<https://wiki.trinitydesktop.org/Fedora_Trinity_Repository_Installation_Inst…> provides
great instructions for installing TDE on a working Fedora 37 system. But the last section provides
no help for starting TDE from a "run-level 3" system (multi-user, not graphical). The built-in
startx command does not detect TDE. Or, more specifically, the /etc/sysconfig/desktop script. Of
course, I can modify that script but I have no idea what to add to it. It would be nice if the TDE
installation provided an updated version.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
dave(a)compata.com dhclose(a)alumni.caltech.edu
"Thoughts, like fleas, jump from man to man,
but they don't bite everybody." -- Stanislaw Jerzy Lec
Hello,
On my second computer,
I created an icon Konqueror to open it in root.
When I want to open a file I receive this message :
"Impossible to dialogue with TDE Launcher"
and the file does not open.
Quid ?
I don't have this message on my two others computers.
Thanks, cheers.
André
Wolfgang Pfeiffer composed on 2023-03-06 18:38 (UTC+0100): # on fedora user mailing list.
> On Mar 06, 2023 at 03:34:38 -0500, Felix Miata wrote:
>>I'm not against change, but this is a result of several years of system-upgrades,
>>and I've never seen anything explaining how to make a switch:
...
> In your messages wireplumber does not appear. It seems this software
> is managing sound since F34. On this page
> https://fedoraproject.org/wiki/Common_F35_bugs#No_sound_after_upgrade_(wire…
> you find
> "Wireplumber ... "needs to be running for sound to work"."
>
> The page above provides excellent documentation to find what went
> wrong, and how to fix it.
It doesn't seem to cover this:
# dnf search systemd | grep -iE 'wire|puls|audio|sound'
Last metadata expiration check: 0:20:21 ago on Mon 06 Mar 2023 06:11:55 PM EST.
[root@gx62b ~]# rpm -qa | grep -iE 'wire|pulse|alsa|audio|sound' |sort
alsa-firmware-1.2.4-7.fc37.noarch
alsa-lib-1.2.8-2.fc37.x86_64
alsa-tools-firmware-1.2.5-5.fc37.x86_64
alsa-ucm-1.2.8-2.fc37.noarch
alsa-utils-1.2.8-1.fc37.x86_64
audiofile-0.3.6-31.fc37.x86_64
esound-libs-0.2.41-28.fc37.x86_64
jack-audio-connection-kit-1.9.21-3.fc37.x86_64
pipewire-libs-0.3.66-1.fc37.x86_64
pipewire-pulseaudio-0.3.66-1.fc37.x86_64
pulseaudio-libs-16.1-4.fc37.x86_64
pulseaudio-utils-16.1-4.fc37.x86_64
python3-alsa-1.2.7-3.fc37.x86_64
sound-theme-freedesktop-0.8-18.fc37.noarch
soundtouch-2.3.1-3.fc37.x86_64
webrtc-audio-processing-0.3.1-9.fc37.x86_64
wireplumber-libs-0.4.13-1.fc37.x86_64
zita-alsa-pcmi-0.6.1-1.fc37.x86_64
#
$ systemctl --user status wireplumber.service
Unit wireplumber.service could not be found.
$
This is after rebooting following running
dnf swap --allowerasing pulseaudio pipewire-pulseaudio
dnf install wireplumber-libs
dnf remove pulseaudio-libs-glib2 # removed phonon* too
Afterward:
dnf install wireplumber
And reboot. Now logging in TDE produces an endless stream of soundserver popups
that prevents focus from staying anywhere else long enough to do anything but
log out, but logging in on vtty allows:
$ systemctl --user status wireplumber.service
# wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service: enabled; preset: enabled)
Active: inactive (dead)
What's required to end the popups and continue lack of sound diagnosis?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
On 2023-03-05 17:29:04 deloptes via tde-users wrote:
> J Leslie Turriff via tde-users wrote:
> > Is there a way for one account to fetch information from another
> > account's DCOP service? If I open a Konsole session that logs into
> > another account's shell, can that shell fetch the SessionName from the
> > DCOP of the Konsole account?
Attached is a snapshot of the Konsole sessions in question. The three sessions with red
terminal icons are root sessions. I want their .bashrc to be able to obtain the tab
titles (SessionName) for self-identification.
Leslie
--
Platform: GNU/Linux
Hardware: x86_64
Distribution: openSUSE Leap 15.4
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0
Trinity 14.0.6 preliminary.
Don't know if it is a feature of ksnapshot or a misconfiguration
somewhere from me, but it is getting absolutely annoying what happens.
I have a website, a document or whatsoever on my screen in full
A4-papersize. Now I want a printout of a small part of it. Call
ksnapshot, choose "region" "new snapshot" and then draw a border around
the desired part. Press "print" and then print it. Bull... I get a
print in landscape, useless and even worse not even the original layout
reappears.
Stop ksnapshot, restart it and same procedure with again the same
miserable result.
Stop, restart, same procedure but no actual printing, instead I look
into the printer properties. And there, big surprise, landscape was
marked as to be printed BUT all 4 orientations were grayed out, so I
couldn't change that.
Checked in tdeprint the printersettings, nothing wrong, in "instances"
"settings" all 4 orientations were available and portrait was marked as
to be applied in the default printer.
Checked kprinter and of course the settings of tdeprint were there also
valid.
But then I had an idea. If I selected in ksnapshot a larger part of the
screen, say more than half A4, what would happen?
Yes, some ugly words from me and there it was: portrait was marked but
still all 4 possibilities grayed out.
So ksnapshot decides how it wants to print and doesn't leave the user a
chance to get a result, that he wants. Utterly bull....
Any suggestion, where I could look to alter this behaviour?
Phiebie.
I found a Stretch installation I forgot to upgrade at the time support
ended, and tried to do it now. It won't let me complete the operation
without removing Konq:
# dpkg-query -l | grep 14.0.6
ii kcontrol-trinity 4:14.0.6-0debian9.0.0+0 amd64 control center for TDE
ii kdesktop-trinity 4:14.0.6-0debian9.0.0+0 amd64 miscellaneous binaries and files for the Trinity desktop
ii kfind-trinity 4:14.0.6-0debian9.0.0+0 amd64 file-find utility for TDE
ii kicker-trinity 4:14.0.6-0debian9.0.0+0 amd64 desktop panel for TDE
ii konq-plugins-trinity 4:14.0.6-0debian9.0.0+0 amd64 plugins for Konqueror, the Trinity file/web/doc browser
ii konqueror-trinity 4:14.0.6-0debian9.0.0+0 amd64 TDE's advanced file manager, web browser and document viewer
ii kpersonalizer-trinity 4:14.0.6-0debian9.0.0+0 amd64 installation personalizer for TDE
ii ksplash-trinity 4:14.0.6-0debian9.0.0+0 amd64 the TDE splash screen
ii smb4k-trinity 4:14.0.6-0debian9.0.0+0 amd64 A Samba (SMB) share advanced browser for Trinity
ii tdebase-data-trinity 4:14.0.6-0debian9.0.0+0 all shared data files for the TDE base module
ii tdebase-tdeio-plugins-trinity 4:14.0.6-0debian9.0.0+0 amd64 core I/O slaves for TDE
ii tdebase-trinity-bin 4:14.0.6-0debian9.0.0+0 amd64 core binaries for the TDE base module
ii tdm-trinity 4:14.0.6-0debian9.0.0+0 amd64 X display manager for TDE
# apt-get full-upgrade
...
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
konq-plugins-trinity konqueror-nsplugins-trinity konqueror-trinity smb4k-trinity
The following packages will be upgraded:
kcontrol-trinity kdesktop-trinity kfind-trinity kicker-trinity kpersonalizer-trinity ksplash-trinity tdebase-data-trinity tdebase-trinity-bin
tdm-trinity
9 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Need to get 24.0 MB of archives.
After this operation, 12.9 MB disk space will be freed.
Do you want to continue? [Y/n] n
What's the right way to proceed while keeping all of konq installed?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
I am trying to configure special window rules for some VirtualBox machines.
I want the virtual machines to always open in virtual desktop/workspace 2.
I have many virtual machines but a few I use almost daily. Many years
ago I created *.desktop files to launch these few systems without
needing to launch the VirtualBox Manager. I have used devilspie to force
launching in desktop 2.
While devilspie works well in TDE, I want to do this natively with TDE
special window rules.
I have been unable to configure special rules in TDE to ensure the
virtual machines open in desktop 2.
Everything I try in TDE special rules results in the virtual machines
opening in the current desktop.
Other special window rules are working as expected.
Selecting the special rules "Detect" button does not help.
I suspect something different about VirtualBox that is not obvious.
Help is appreciated with respect to creating TDE special rules.
Thank you!
P.S.
To simulate the *.desktop files, launch the mini cli (Alt+F2) and launch
a virtual machine like this:
vboxmanage startvm "name_of_virtual_machine"
DA
