Any idea why it may fail? log attached
from log:
[ 60%] Building CXX object
kttsd/kttsd/CMakeFiles/kttsd.dir/threadedplugin.cpp.o
[ 60%] Generating KSayItView.h, KSayItView.cpp
In file included from
/tmp/build/tmp-tdeaccessibility/tdeaccessibility-trinity-14.0.13/build-tdeaccessibility/kttsd/kcmkttsmgr/kcmkttsmgrwidget.cpp:12:
/tmp/build/tmp-tdeaccessibility/tdeaccessibility-trinity-14.0.13/build-tdeaccessibility/kttsd/kcmkttsmgr/kcmkttsmgrwidget.h:37:1:
error: expected class-name before '{' token
37 | {
| ^
note, I upgrade from tde 14.0.12 via Ray-V's slackbuilds
other packages upgrade themselves ok so far ....
I thought I reported this a year ago. I can't find one on
<https://bugs.pearsoncomputing.net/buglist.cgi?cmdtype=runnamed&list_id=7199…>
and <https://mirror.git.trinitydesktop.org/gitea/issues> says I never filed any
reports at all, which I find hard to believe. :(
Fedora 36, only my second upgrade to 14.0.13 following one on Devuan, where the
instant problem did not occur. This was not a true "upgrade" from a user
perspective. I deleted ~/.trinity so to get a fresh start, then logged into what I
thought would be a virgin TDE session. First click on menu starter produced a
"Malformed URL system:/" Kicker popup that must be dismissed before the menu
starter can be successfully opened. That first click followed configuring clock
and panel. It's repeatable across sessions. :(
First attempt to log out, after typing the above, took probably about 30 seconds
from mouse click to login manager re-appearance, with most of time spent
"notifying applications", of which the only one I opened was Konsole.
On next login, soundserver crash handler appears, same as was happening on all my
Fedora 14.0.12 installations IIRC. An accompanying popup reports KNotify crashed
while instantiating itself, and also asks if I want to try again or disable ARTS.
The really aggravating part is my xrandr startup script in
/etc/X11/xinit/xinitrc.d/ that works fine in openSUSE and Mageia is totally
ignored, so primary status is errantly assigned to the smaller display, and I
can't find any way to get TDE to run the script itself on startup. If I run it
after starting the session, Kicker doesn't land on the bottom of the larger
screen, instead falling above by a distance defined by the difference in height of
the two displays. :(
Attached is example of what happens when selecting and copying Konsole content
into a plain text file opened with MCedit (F4 in MC). This instance is from
trinity-sb in Bullseye, with window size 132x43, but it's been happening in
various distros and various TDE versions 14.0.12 & up. This has been going on for
months in more and more installations as time goes on.
More and more I find myself needing to redirect output to a file, but it's often
not possible to regenerate the same output needed for sharing in a bug, forum post
or email.
A quick and easy way to strip all white space from start of a line would be
appreciated as a workaround until this is fixed. Blocks of many lines increase
whitespace so much that it's very hard to manually remove.
--
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
# rpm -qa | grep lasma5-de
plasma5-desktop-5.24.4-bp154.2.3.2.x86_64
# rpm -qa | grep ty-kde
trinity-kdesktop-14.0.12-1.oss154.x86_64
Trying to run a Plasma session from TDM never completely starts:
We are sorry, klauncher closed unexpectedly.
You cannot report this error, because klauncher does not provide a bug reporting
address.
We are sorry, kdepowerdevil, closed unexpectedly.
You cannot report...
We are sorry, ksplashqml, closed unexpectedly.
You cannot report...
Trying to run a TDE session there are similar continuously repeating popups from
the KDE Crash Handler about segfaulting /usr/bin/kglobalaccel5 that steal focus
from anything needed or wanted to do in TDE session. Making it non-executable
stops the popups, but making executable again makes the popups return instantly.
Removing all KDE settings from ~/.local/share/ and ~/.config/ also fails to
prevent this interference in a TDE session unless TDM is also restarted before
logging into TDE.
--
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
Hi all!
I compiled tde 14.0.12 on 32 bit slackware (mostly 15.0, but actually
upgraded from much earlier versions) via Ray-V Slackbuilds and desktop
works ok.
But today I tried to copy 4.3 gb file from my home dir open in one
konqueror tab into media/sdc1 (newly inserted usb flash drive) open in
another tab, by selecting two files, and then selecting 'copy' from their
context menu, and then switching tab and pasting files there.
I was surprized to see error on bigger file, one with 4.3 GB in size, while
smaller file (2GB) copied ok. I copied bigger file with mc ok.
I wonder if this behaviour just comes from miscompilation (missing
LARGEFILE_SOURCE ? ) or issue might be deeper ?
# rpm -e plymouth plymouth-scripts plymouth-system-theme mageia-theme bootsplash
error: Failed dependencies:
mageia-theme-Default is needed by (installed) trinity-tdebase-14.0.12-1.mga8.x86_64
#
Why does TDE demand plymouth be installed on Mageia installations? I've seen no
equivalent on Debian & derivatives or other rpm distros. :(
--
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
Hi,
I hope someone can assist here. I couldn't come with better title, sorry.
I write a test application and I want to run the compiled code without
installing. So I build using make -f debian/rules build and then run
LD_LIBRARY_PATH=obj-x86_64-linux-gnu/src/testapp
obj-x86_64-linux-gnu/src/testapp/testapp
but I do not get any debugging symbols and no debugging output with kdDebug.
tqDebug works, but this is not what I want.
How can I compile so that I can have the debugging with kdDebug without
building dbgsym packages.
Does someone have an advise.
thanks
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Steam does occasional random hardware surveys. When it sees TDE
it records the window manager as KWin (see screenshot attached).
I don't know whether the TDE devels think it better to be recorded
as KWin or whether you'd prefer to make some change to be recorded
instead as TWin. Indeed I don't know how Steam guesses which window
manager is running.
Anyway this just FWIW.
--Mike
Hi all,
as developers, you are probably more involved, so you probably keep in mind
that there is a plan for release R14.0.13 at the end of October. Therefore,
only a small reminder, if you are not subscribed to the tde-announcements
list:
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/announcements@trin…
Cheers
--
Slávek
