Re: The Amarok is here again!

[piorunz]

On 07/06/2024 12:48, Martin Steigerwald wrote:


Can you send pictures how does it look like now?


Would not like to attach an image to mailing list. There should be some
images online already. I'd rather not go through the hassle to scrub an
image for privacy, upload it somewhere and then post a link here.


When you press Print Screen key on your keyboard, you have an option to
upload directly to Imgur (in KDE's Spectacle tool). In Export / Share /
Imgur menu. Like this:

https://i.imgur.com/v68Xl7j.png

Exactly the same option exists in Gwenview, default KDE image viewer.

And of course, when you do a screenshot, use Rectangle Region area
option, Active Window. That way, you only capture what you want, not an
entire desktop.


Does it have smart playlists, like Strawberry Music Player, or old
Winamp?


Pretty similar than before.

Not sure what you refer to with smart playlists. I do not know Strawberry
Music Player and Winamp. Old Amarok had some auto DJ feature where it
would add titles based on what is already in playlist. However I do not
see that in Amarok 3 at the moment.

There may still be some features from the old Amarok missing.


I used Amarok briefly years ago, but I don't remember if it has dynamic
playlists (smart playlists like Strawberry player calls it). I am still
not settled on music player. My simple requirement is that I can create
a playlist, which dynamically loads songs, for example filter based on
name, or song length, or number of stars in the rating, or my play
count. If music player does not have this feature is pretty much useless
to manage a big music collection, because I can't even load my favourite
songs.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: The Amarok is here again!

[piorunz]

On 07/06/2024 08:53, Martin Steigerwald wrote:

Martin Steigerwald - 07.06.24, 09:51:01 CEST:

The legendary Amarok is playing music again!


And it retrieves and scrolls the text of the song currently playing.

I love it!

I have the flexible layout again. Can drag and drop things around and so
on. Awesome.



Can you send pictures how does it look like now?
Does it have smart playlists, like Strawberry Music Player, or old Winamp?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Any possibility the "Restore/Add Double Click Speed setting" bug can be backported to bookworm?

[piorunz]

On 08/11/2023 13:49, local10 wrote:

Hi,

Is there any possibility the "Restore/Add Double Click Speed setting" bug ( 
https://bugs.kde.org/show_bug.cgi?id=413502 ) can be backported to bookworm?
Thanks


I am also affected by this. Sigh. Double click is a bit too fast for me,
I want it to register slower clicks.
Well, I guess we will just have to wait until new version of KDE and/or
Debian.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 13:57, Andrey Rakhmatullin wrote:

On Tue, Oct 24, 2023 at 12:16:18PM +0100, piorunz wrote:

Why there are two ways to obtain debugging symbols?

The -dbgsym packages is the official method since its introduction,
debuginfod is newer and has some downsides, e.g. it's easier to
pre-install all -dbgsym you could need and not worry about downloading
symbols on demand.


I already have export DEBUGINFOD_URLS="https://debuginfod.debian.net;,
and this failed to resolve all problems in debugger, it seems. If
debuginfod works only partially, then it should not be recommended

Sure, but unless someone else knows what is the cause of this problem it
looks like you need to investigate it yourself.



Hi Andrey,
Thanks for your explanation. I will concentrate more on Debian
repository as a source of dbgsym packages then. I was already able to
provide more information to other unrelated crash (rasdaemon), by
sending exact, relevant backtrace to the Debian bug report. That's
thanks to your and other KDE group members help!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 12:41, Diederik de Haas wrote:

On Tuesday, 24 October 2023 10:51:46 CEST Cosmo wrote:

piorunz is so incompetent that he managed to discredit the whole of Debian
in front of one of the prominent kde project managers. Nice job 


Piotr didn't read/apply the whole of the Backtrace wiki page, that's their
only 'mistake'.


Yes, for that I am sorry. I am not a developer, never written a line in
C/C++. But I am driven by the target I want to achieve (getting a crash
resolved), so every one gets better experience from using KDE, not just
me. I am not driven by my personal ego. So, cosmo can bark all day long.


You OTOH, only sent a rude, useless and patronizing reply to this list, while
making assumptions about someone's competence.

If that wasn't bad enough, you also added to the upstream bug report (...)


Wow, things escalated very quickly! His reply to KDE bug is indeed very
rude and totally not in place!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 12:35, Cosmo wrote:

Dear piorunz, what do I have to do with it? You're the one who doesn't know
what he's doing...


What you have to do with it? You are laughing at my incompetence, so I
am asking you, show my your track record, or shut up. Easy to blame
someone, not easy to prove if you are any better.


BTW, next time ask here without going around (unintentionally) spreading
discredit on Debian


I am reporting crashes here on Debian-KDE list very often, check my
previous posts and threads.
Only recently, due to lack of improvement with some crashing packages, I
got interested in debugging and I am achieving something.

I am still waiting for your track record, what you have done to improve
Debian?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 12:03, Grzegorz Szymaszek wrote:

On Tue, Oct 24, 2023 at 11:57:46AM +0100, piorunz wrote:

This KDE guideline should definitely be improved:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian

It doesn't say anything about additional debugging repository available
in Debian! [...]


"See also the Debian document on How to get a Backtrace." links to
https://wiki.debian.org/HowToGetABacktrace


Thanks! This is my fault entirely for missing this.

Question:
Why there are two ways to obtain debugging symbols? I already have
export DEBUGINFOD_URLS="https://debuginfod.debian.net;, and this failed
to resolve all problems in debugger, it seems. If debuginfod works only
partially, then it should not be recommended, I would not fall into this
trap but have added additional Debian repository instead, long time ago.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 23/10/2023 20:15, Andrey Rakhmatullin wrote:

On Mon, Oct 23, 2023 at 08:08:56PM +0100, piorunz wrote:

In general, assuming you use KDE packages from official Debian archives,
you can use either debuginfod, or plain old debug packages. Have a look
at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to
obtain the needed debug package names. Let us know if you'll have
further issues or if there's something to improve in that Wiki text.

   [1]: https://wiki.debian.org/HowToGetABacktrace



Hi Grzegorz,

I already have debuginfod configured,

It doesn't look like it worked then.


It's working because when I first installed it in /etc/profile, it has
downloaded some symbols for various crashing packages I stumbled upon in
the last several months. I also manually launch gdb via:

export DEBUGINFOD_URLS="https://debuginfod.debian.net; && sudo
coredumpctl debug

But it doesn't solve everything, it seems.


"or plain old debug packages"

Where I can find those?

The wiki page linked covers that too, in the "Installing the debugging symbols" 
section.


Thanks, indeed it does. Repo added! This, plus debuginfod, should
improve my ability to debug crashing packages.

This KDE guideline should definitely be improved:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian

It doesn't say anything about additional debugging repository available
in Debian! I relied on this source when I first configured debuginfod,
installed gdb, and decided to have a go at it. I was not aware of any
additional repository.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 09:51, Cosmo wrote:

piorunz is so incompetent that he managed to discredit the whole of Debian in
front of one of the prominent kde project managers. Nice job 



Dear cosmo, I assume you are not a developer, because a developer would
not have a laugh like that from incompetency of a user who tries to
help. So if you are a Debian user, show me please how many packages and
bugs in Debian you debugged and helped to solve?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 24/10/2023 11:36, Diederik de Haas wrote:

On Monday, 23 October 2023 20:19:42 CEST piorunz wrote:

Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank you.


Add the following line to your /etc/apt/sources.list and do `apt update`
deb http://debug.mirrors.debian.org/debian-debug bookworm-debug main 
non-free-firmware

Then you will find the dbgsym packages.


#2  0x7fe7678a8e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 
0x4e9b)


With `apt-file search libKF5Crash.so.5` you'll find it belongs to the
libkf5crash5 package and then do `aptitude search libkf5crash5` and you should
find a package with a `-dbgsym` suffix and you install that package.
Repeat that for all the libraries in your stacktrace and when you then generate
a new stacktrace, it should contain all the info you want/need.


Great, thank you!
I was able to add additional repository as you and Andrey Rakhmatullin
mentioned. And now I will get to work to install all necessary dbgsym
packages.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 23/10/2023 19:46, Grzegorz Szymaszek wrote:

Hi,

On Mon, Oct 23, 2023 at 07:19:42PM +0100, piorunz wrote:

Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank you.


In general, assuming you use KDE packages from official Debian archives,
you can use either debuginfod, or plain old debug packages. Have a look
at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to
obtain the needed debug package names. Let us know if you'll have
further issues or if there's something to improve in that Wiki text.

  [1]: https://wiki.debian.org/HowToGetABacktrace



Hi Grzegorz,

I already have debuginfod configured, please read comments to the bug
report, link in first post. I was not able to generate meaningful
backtrace with what I have.

"or plain old debug packages"

Where I can find those?
Thank you.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Plasmashell crash: debugging symbols

[piorunz]

On 23/10/2023 19:34, Brad Rogers wrote:

On Mon, 23 Oct 2023 19:19:42 +0100
piorunz  wrote:

Hello piorunz,


Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank
you.


Search for packages with -dbgsym at the end.  If unsure which one(s), ask
Nate - I'm sure they won't mind.



No such packages in Debian:

$ aptitude search dbgsym
v   libc6-dbgsym
v   libc6-dbgsym:i386

Nate Graham can't help me, has expressed his dissatisfaction.
Please check the link to the bug where he commented.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Plasmashell crash: debugging symbols

[piorunz]

Hello friends,

I've reported a plasmashell crash to bugs.kde.org. Nate Graham from KDE
has responded.

https://bugs.kde.org/show_bug.cgi?id=475779

I provided gdb reports with backtrace, however, they are not useful,
because I don't have debugging symbols for KArchive and Plasma.

Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank you.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)

[piorunz]

On 20/08/2023 19:26, Patrick Franz wrote:

Hi,

FYI, I've requested plasma-workspace to be updated in Debian Stable and
will upload the fix to bookworm once the request is approved.




That's amazing Patrick, thank you! ❤️

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1037557: plasma-workspace: krunner crash almost everytime when start typing

[piorunz]

On 16/08/2023 21:01, Patrick Franz wrote:

Hej Piotr,

I've backported the fix to Plasma 5.27.5. Can you please be so kind and
test it ? You can find the updated packages at
https://people.debian.org/~deltaone/plasma-workspace/


Hi Patrick,

I installed it and it's working! No more crashes.

I launched it with gdb, each key press is spawning and ending a thread,
but they cannot collide any more like before. I could not crash krunner
so far. That's amazing, thanks for your work!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing))

[piorunz]

On 13/08/2023 18:56, Patrick Franz wrote:

Hi,

I was able to reproduce the bug on bookworm, but it is solved for me in
testing ans unstable. Is it maybe this bug ?
https://bugs.kde.org/show_bug.cgi?id=470219

That is solved in Plasma 5.27.6...


Hi Patrick,
Yes, exactly! I was able to dig this information out finally and came to
same conclusion - it's already fixed upstream two months ago:
https://invent.kde.org/plasma/plasma-workspace/-/commit/e2ef967c5860543c7c4bf3da9129b0c70292e8ed

Is there any chance that this is cherry picked and imported to Debian
Stable? Stable is still running 5.27.5, I don't know when it will be
moved to 5.27.6?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma-workspace: krunner crashes with SIGSEGV

[piorunz]

On 11/08/2023 08:50, piorunz wrote:

Hi friends,

I use Debian Stable and I've reported a bug troubling krunner in June.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037557

However, this problem is still unresolved, and I've noticed it too on my
laptop. Both machines are upgrades from Debian 11, and in both krunner
is crashing.
Has anyone also experienced this problem?
I am hoping that someone will get interested and maybe help me report
this upstream, get a fix, anything. Thank you!


Finally I have some new info!

So this bug was actually fixed two months ago:
https://invent.kde.org/plasma/plasma-workspace/-/commit/e2ef967c5860543c7c4bf3da9129b0c70292e8ed

KDE bug (resolved): https://bugs.kde.org/show_bug.cgi?id=470219

Is there any chance that this is cherry picked and imported to Debian
Stable?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)))))

[piorunz]

Upstream bug report has been opened:

https://bugs.kde.org/show_bug.cgi?id=473339

Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing))))

[piorunz]

Full gbd run with debuginfod symbols:


$ gdb krunner
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krunner...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from
/home/pioruns/.cache/debuginfod_client/703112e8addd504b93c81c1ca3e6bd4bc8152bd3/debuginfo...

(gdb) run


Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]


Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x703ff6c0 (LWP 355717)]


[New Thread 0x7fffed5ff6c0 (LWP 355722)]


[New Thread 0x7fffecdfe6c0 (LWP 355723)]
[New Thread 0x7fffdf5ff6c0 (LWP 355724)]
[New Thread 0x7fffdedfe6c0 (LWP 355725)]
[New Thread 0x7fffde5fd6c0 (LWP 355726)]
[Thread 0x7fffde5fd6c0 (LWP 355726) exited]
[New Thread 0x7fffde5fd6c0 (LWP 355727)]


[New Thread 0x7fffddbfc6c0 (LWP 355728)]
[Thread 0x7fffddbfc6c0 (LWP 355728) exited]
[New Thread 0x7fffddbfc6c0 (LWP 355729)]


[New Thread 0x7fffbedff6c0 (LWP 355730)]


[New Thread 0x7fffbe5fe6c0 (LWP 355731)]
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.


kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
[New Thread 0x7fffb7c226c0 (LWP 355766)]


[New Thread 0x7fffb74216c0 (LWP 355767)]
[New Thread 0x7fffb6b846c0 (LWP 355768)]


Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)


[New Thread 0x7fffb627e6c0 (LWP 355784)]
[New Thread 0x7fffb5a7d6c0 (LWP 355785)]
[New Thread 0x7fffb527c6c0 (LWP 355786)]
[New Thread 0x7fffb4a7b6c0 (LWP 355787)]
[New Thread 0x7fff93fff6c0 (LWP 355788)]
[New Thread 0x7fff8bfff6c0 (LWP 355789)]
[New Thread 0x7fff937fe6c0 (LWP 355790)]
[New Thread 0x7fff92ffd6c0 (LWP 355791)]
[New Thread 0x7fff927fc6c0 (LWP 355792)]
[New Thread 0x7fff91ffb6c0 (LWP 355793)]
[New Thread 0x7fff917fa6c0 (LWP 355794)]
[New Thread 0x7fff90ff96c0 (LWP 355795)]
[New Thread 0x7fff8b7fe6c0 (LWP 355796)]
[New Thread 0x7fff8affd6c0 (LWP 355797)]
[New Thread 0x7fff8a7fc6c0 (LWP 355798)]
[New Thread 0x7fff89ffb6c0 (LWP 355799)]
[New Thread 0x7fff897fa6c0 (LWP 355800)]
[New Thread 0x7fff88ff96c0 (LWP 355801)]
[New Thread 0x7fff53fff6c0 (LWP 355802)]
[New Thread 0x7fff4bfff6c0 (LWP 355803)]
[New Thread 0x7fff537fe6c0 (LWP 355804)]
[New Thread 0x7fff52ffd6c0 (LWP 355805)]
[New Thread 0x7fff527fc6c0 (LWP 355806)]
[New Thread 0x7fff51ffb6c0 (LWP 355807)]
[New Thread 0x7fff517fa6c0 (LWP 355808)]
[New Thread 0x7fff50ff96c0 (LWP 355809)]
[New Thread 0x7fff4b7fe6c0 (LWP 355810)]
[New Thread 0x7fff4affd6c0 (LWP 355811)]
[New Thread 0x7fff4a7fc6c0 (LWP 355812)]
[New Thread 0x7fff49ffb6c0 (LWP 355813)]
[New Thread 0x7fff497fa6c0 (LWP 355814)]
[New Thread 0x7fff48ff96c0 (LWP 355815)]
[Detaching after vfork from child process 355816]


[New Thread 0x7fff13fff6c0 (LWP 355817)]


[Detaching after fork from child process 355818]
[New Thread 0x7fff137fe6c0 (LWP 355819)]
[Thread 0x7fff137fe6c0 (LWP 355819) exited]
[Thread 0x7fff13fff6c0 (LWP 355817) exited]
[New Thread 0x7fff137fe6c0 (LWP 355821)]
[New Thread 0x7fff12ffd6c0 (LWP 355822)]
[New Thread 0x7fff0affd6c0 (LWP 355829)]
[New Thread 0x7fff11ffb6c0 (LWP 355824)]
[New Thread 0x7fff127fc6c0 (LWP 355823)]
[New Thread 0x7fff0bfff6c0 (LWP 355827)]
[New Thread 0x7fff10ff96c0 (LWP 355826)]
[New Thread 0x7fff09ffb6c0 (LWP 355831)]
[New Thread 0x7fff117fa6c0 (LWP 355825)]
[New Thread 0x7fff0a7fc6c0 (LWP 355830)]
[New Thread 0x7fff097fa6c0 (LWP 355832)]
[New Thread 0x7fff08ff96c0 (LWP 355833)]
[New Thread 0x7fff0b7fe6c0 (LWP 355828)]
[Thread 0x7fff12ffd6c0 (LWP 355822) exited]

Thread 50 "GlobalQueue[13]" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff137fe6c0 (LWP 355821)]
0x7fffbca5a1a4 in MathStructure::set
(this=this@entry=0x7fffb5a7c830, o=...,
merge_precision=merge_precision@entry=false) at
./libqalculate/MathStructure.cc:218
Download failed: Invalid argument.  Continuing without source file
./libqalculate/./libqalculate/MathStructure.cc.

218 ./libqalculate/MathStructure.cc: No such file or directory.
(gdb) bt
#0  0x7fffbca5a1a4 in MathStructure::set
(this=this@entry=0x7fffb5a7c830, o=...,

Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)))

[piorunz]

Crashing krunner directly from terminal, with gdb on:

$ gdb krunner
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krunner...
(No debugging symbols found in krunner)
(gdb) run
Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x703ff6c0 (LWP 551440)]
[New Thread 0x7fffed5ff6c0 (LWP 551441)]
[New Thread 0x7fffecdfe6c0 (LWP 551442)]
[New Thread 0x7fffdf5ff6c0 (LWP 551443)]
[New Thread 0x7fffdedfe6c0 (LWP 551444)]
[New Thread 0x7fffde5fd6c0 (LWP 551445)]
[Thread 0x7fffde5fd6c0 (LWP 551445) exited]
[New Thread 0x7fffde5fd6c0 (LWP 551446)]
[New Thread 0x7fffddbfc6c0 (LWP 551447)]
[Thread 0x7fffddbfc6c0 (LWP 551447) exited]
[New Thread 0x7fffddbfc6c0 (LWP 551448)]
[New Thread 0x7fffbedff6c0 (LWP 551449)]
[New Thread 0x7fffbe5fe6c0 (LWP 551450)]
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
[New Thread 0x7fffb7c226c0 (LWP 551488)]
[New Thread 0x7fffb74216c0 (LWP 551489)]
[New Thread 0x7fffb6b846c0 (LWP 551490)]
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[New Thread 0x7fffb627e6c0 (LWP 551506)]
[New Thread 0x7fffb5a7d6c0 (LWP 551507)]
[New Thread 0x7fffb527c6c0 (LWP 551508)]
[New Thread 0x7fffb4a7b6c0 (LWP 551509)]
[New Thread 0x7fff93fff6c0 (LWP 551510)]
[New Thread 0x7fff8b7fe6c0 (LWP 551511)]
[New Thread 0x7fff937fe6c0 (LWP 551512)]
[New Thread 0x7fff92ffd6c0 (LWP 551513)]
[New Thread 0x7fff927fc6c0 (LWP 551514)]
[New Thread 0x7fff91ffb6c0 (LWP 551515)]
[New Thread 0x7fff917fa6c0 (LWP 551516)]
[New Thread 0x7fff90ff96c0 (LWP 551517)]
[New Thread 0x7fff8bfff6c0 (LWP 551518)]
[New Thread 0x7fff8affd6c0 (LWP 551519)]
[New Thread 0x7fff8a7fc6c0 (LWP 551520)]
[New Thread 0x7fff89ffb6c0 (LWP 551521)]
[New Thread 0x7fff897fa6c0 (LWP 551522)]
[New Thread 0x7fff88ff96c0 (LWP 551523)]
[New Thread 0x7fff53fff6c0 (LWP 551524)]
[New Thread 0x7fff4b7fe6c0 (LWP 551525)]
[New Thread 0x7fff537fe6c0 (LWP 551526)]
[New Thread 0x7fff52ffd6c0 (LWP 551527)]
[New Thread 0x7fff527fc6c0 (LWP 551528)]
[New Thread 0x7fff51ffb6c0 (LWP 551529)]
[New Thread 0x7fff517fa6c0 (LWP 551530)]
[New Thread 0x7fff50ff96c0 (LWP 551531)]
[New Thread 0x7fff4bfff6c0 (LWP 551532)]
[New Thread 0x7fff4affd6c0 (LWP 551533)]
[New Thread 0x7fff4a7fc6c0 (LWP 551534)]
[New Thread 0x7fff49ffb6c0 (LWP 551535)]
[New Thread 0x7fff497fa6c0 (LWP 551536)]
[New Thread 0x7fff48ff96c0 (LWP 551537)]
[Detaching after fork from child process 551538]
[Detaching after vfork from child process 551540]
[New Thread 0x7fff127fc6c0 (LWP 551541)]
[New Thread 0x7fff12ffd6c0 (LWP 551545)]
[New Thread 0x7fff10ff96c0 (LWP 551544)]
[New Thread 0x7fff13fff6c0 (LWP 551543)]
[New Thread 0x7fff11ffb6c0 (LWP 551547)]
[New Thread 0x7fff137fe6c0 (LWP 551542)]
[New Thread 0x7fff117fa6c0 (LWP 551546)]

Thread 51 "GlobalQueue[19]" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff13fff6c0 (LWP 551543)]
0x7fffbca5a010 in MathStructure::clear(bool) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
(gdb) bt
#0  0x7fffbca5a010 in MathStructure::clear(bool) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#1  0x7fffbca5b322 in MathStructure::setAborted(bool) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#2  0x7fffbc9d68d7 in CalculateThread::run() () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#3  0x7fffbca6596f in Thread::doRun(void*) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#4  0x75aa8044 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x75b285fc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

All what needs to be done is to type several numbers very fast. 100%
chance of crash.

plasma-workspace: krunner crashes with SIGSEGV

[piorunz]

Hi friends,

I use Debian Stable and I've reported a bug troubling krunner in June.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037557

However, this problem is still unresolved, and I've noticed it too on my
laptop. Both machines are upgrades from Debian 11, and in both krunner
is crashing.
Has anyone also experienced this problem?
I am hoping that someone will get interested and maybe help me report
this upstream, get a fix, anything. Thank you!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)

[piorunz]

Another crash just now, this one has subtly different stack trace.$ debug 2804705
   PID: 2804705 (krunner)
   UID: 1000 (pioruns)
   GID: 1000 (pioruns)
Signal: 11 (SEGV)
 Timestamp: Wed 2023-06-14 11:02:17 BST (1h 37min ago)
  Command Line: /usr/bin/krunner
Executable: /usr/bin/krunner
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-krunner.service
  Unit: user@1000.service
 User Unit: plasma-krunner.service
 Slice: user-1000.slice
 Owner UID: 1000 (pioruns)
   Boot ID: 194ee41541104cefbfe91ddd5cf10473
Machine ID: 01568f2c8e7d4695b16a1f32deab7e38
  Hostname: ryzen
   Storage: 
/var/lib/systemd/coredump/core.krunner.1000.194ee41541104cefbfe91ddd5cf10473.2804705.168673693700.zst
 (present)
  Size on Disk: 21.0M
   Message: Process 2804705 (krunner) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.6-1.amd64
Module libudev.so.1 from deb systemd-252.6-1.amd64
Stack trace of thread 2804705:
#0  0x7f27900a9ccc n/a (libc.so.6 + 0x8accc)
#1  0x7f279005aef2 raise (libc.so.6 + 0x3bef2)
#2  0x7f2792402b46 _ZN6KCrash19defaultCrashHandlerEi 
(libKF5Crash.so.5 + 0x5b46)
#3  0x7f279005af90 n/a (libc.so.6 + 0x3bf90)
#4  0x7f27900a9ccc n/a (libc.so.6 + 0x8accc)
#5  0x7f279005aef2 raise (libc.so.6 + 0x3bef2)
#6  0x7f279005af90 n/a (libc.so.6 + 0x3bf90)
#7  0x7f27900a4ef4 __lll_lock_wait_private (libc.so.6 + 
0x85ef4)
#8  0x7f27900b79c8 malloc (libc.so.6 + 0x989c8)
#9  0x7f278fea958c _Znwm (libstdc++.so.6 + 0xa958c)
#10 0x7f27904e76b4 _ZN7QObjectC2EPS_ (libQt5Core.so.5 + 
0x2e76b4)
#11 0x7f277b12e272 
_ZN6Plasma13RunnerContextC1ERS0_P7QObject (libKF5Runner.so.5 + 0x25272)
#12 0x7f277b131b6c n/a (libKF5Runner.so.5 + 0x28b6c)
#13 0x7f277b13b2f0 n/a (libKF5Runner.so.5 + 0x322f0)
#14 0x7f277b138163 
_ZN6Plasma13RunnerManager11launchQueryERK7QStringS3_ (libKF5Runner.so.5 + 
0x2f163)
#15 0x7f2783e624e4 n/a (libmilou.so.5 + 0x114e4)
#16 0x7f2783e5fd4d 
_ZN5Milou12ResultsModel14setQueryStringERK7QString (libmilou.so.5 + 0xed4d)
#17 0x7f2791aeb13b n/a (libQt5Qml.so.5 + 0x2eb13b)
#18 0x7f2791aeb93e n/a (libQt5Qml.so.5 + 0x2eb93e)
#19 0x7f2791ae9354 
_ZN11QQmlBinding6updateE6QFlagsIN16QQmlPropertyData9WriteFlagEE (libQt5Qml.so.5 
+ 0x2e9354)
#20 0x7f2791ac677f 
_ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 
0x2c677f)
#21 0x7f27904e8a8d n/a (libQt5Core.so.5 + 0x2e8a8d)
#22 0x7f2791a6ea35 
_ZN17QQmlVMEMetaObject8metaCallEP7QObjectN11QMetaObject4CallEiPPv 
(libQt5Qml.so.5 + 0x26ea35)
#23 0x7f27919a6b62 
_ZN3QV414QObjectWrapper11setPropertyEPNS_15ExecutionEngineEP7QObjectP16QQmlPropertyDataRKNS_5ValueE
 (libQt5Qml.so.5 + 0x1a6b62)
#24 0x7f27919a6ffb 
_ZN3QV414QObjectWrapper14setQmlPropertyEPNS_15ExecutionEngineEP15QQmlContextDataP7QObjectPNS_6StringENS0_12RevisionModeERKNS_5ValueE
 (libQt5Qml.so.5 + 0x1a6ffb)
#25 0x7f27919a715b 
_ZN3QV414QObjectWrapper10virtualPutEPNS_7ManagedENS_11PropertyKeyERKNS_5ValueEPS4_
 (libQt5Qml.so.5 + 0x1a715b)
#26 0x7f279192f333 
_ZN3QV46Lookup14setterFallbackEPS0_PNS_15ExecutionEngineERNS_5ValueERKS4_ 
(libQt5Qml.so.5 + 0x12f333)
#27 0x7f275a6190cc n/a (n/a + 0x0)
#28 0x7f27919c5300 n/a (libQt5Qml.so.5 + 0x1c5300)
#29 0x7f2791957c2e 
_ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5 
+ 0x157c2e)
#30 0x7f2791ae144d 
_ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 + 
0x2e144d)
#31 0x7f2791a92baf 
_ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt5Qml.so.5 + 0x292baf)
#32 0x7f2791a942f8 n/a (libQt5Qml.so.5 + 0x2942f8)
#33 0x7f2791ac677f 
_ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 
0x2c677f)
#34 0x7f27904e8a8d n/a (libQt5Core.so.5 + 0x2e8a8d)
#35 0x7f2792097f48 
_ZN22QQuickTextInputPrivate12finishChangeEibb (libQt5Quick.so.5 + 0x297f48)
#36 0x7f279209c4c0 
_ZN22QQuickTextInputPrivate15processKeyEventEP9QKeyEvent (libQt5Quick.so.5 + 
0x29c4c0)
#37 0x7f279209c58c 
_ZN15QQuickTextInput13keyPressEventEP9QKeyEvent (libQt5Quick.so.5 + 0x29c58c)
#38 0x7f2792054f2b 
_ZN17QQuickItemPrivate15deliverKeyEventEP9QKeyEvent 

Bug#1037557: plasma-workspace: krunner crash almost everytime when start typing

[piorunz]

Package: plasma-workspace
Version: 4:5.27.5-2
Severity: important
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

I am experiencing krunner crash almost every time I start type something.
For example I start typing 20491+20 and krunner dissapears, with notification
from KDE Crash Handler, offering me to report the bug, but then it goes on to
say that "The generated crash information is not useful", so I cannot submit my
error report through that tool.
Anyway, I have debugging enabled in my system so I am able to generate some
reports.

$ sudo coredumpctl list --no-pager | grep krunner
Fri 2023-06-02 15:36:18 BST 2714641 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Fri 2023-06-02 15:36:28 BST 2714775 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Mon 2023-06-05 15:59:49 BST 2826851 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Tue 2023-06-06 17:31:24 BST 3173741 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Tue 2023-06-06 17:33:25 BST 3361955 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Tue 2023-06-06 18:09:28 BST 3362192 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Tue 2023-06-06 18:12:46 BST 3364551 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Wed 2023-06-07 00:25:49 BST 3364850 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Wed 2023-06-07 15:56:39 BST 3393665 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Wed 2023-06-07 16:07:30 BST 3407464 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Fri 2023-06-09 18:44:53 BST  639019 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Fri 2023-06-09 19:49:34 BST 4080355 1000 1000 SIGSEGV missing  /usr/bin/krunner
-
Sat 2023-06-10 04:00:53 BST 4083426 1000 1000 SIGSEGV present  /usr/bin/krunner
15.1M
Sat 2023-06-10 22:46:21 BST   38104 1000 1000 SIGSEGV present  /usr/bin/krunner
20.4M
Mon 2023-06-12 19:26:13 BST   99001 1000 1000 SIGSEGV present  /usr/bin/krunner
15.9M
Mon 2023-06-12 20:02:41 BST  382477 1000 1000 SIGSEGV present  /usr/bin/krunner
14.5M
Wed 2023-06-14 00:48:38 BST 3408294 1000 1000 SIGSEGV present  /usr/bin/krunner
17.6M
Wed 2023-06-14 08:41:58 BST 1608509 1000 1000 SIGSEGV present  /usr/bin/krunner
15.3M

gbd backtrace from last crash just now, pid 1608509, has been attached.

Let me know if you need anything else, I will be happy to test. I use Debian
Stable on AMD64 system.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]1.14.6-1
ii  drkonqi 5.27.5-2
ii  frameworkintegration5.103.0-1
ii  gdb-minimal [gdb]   13.1-3
ii  init-system-helpers 1.65.2
ii  iso-codes   4.15.0-1
ii  kactivitymanagerd   5.27.5-2
ii  kded5   5.103.0-1
ii  kinit   5.103.0-1
ii  kio 5.103.0-1
ii  kpackagetool5   5.103.0-1
ii  kwin-common 4:5.27.5-3
ii  libappstreamqt2 0.16.1-2
ii  libc6   2.36-9
ii  libcolorcorrect54:5.27.5-2
ii  libcrypt1   1:4.4.33-2
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   12.2.0-14
ii  libgps283.22-4.1+b1
ii  libice6 2:1.0.10-1
ii  libicu7272.1-3
ii  libkf5activities5   5.103.0-1
ii  libkf5activitiesstats1  5.103.0-1
ii  libkf5archive5  5.103.0-1
ii  libkf5authcore5 5.103.0-1
ii  libkf5baloo55.103.0-2
ii  libkf5bookmarks55.103.0-1
ii  libkf5calendarevents5   5.103.0-1
ii  libkf5completion5   5.103.0-1
ii  libkf5config-bin5.103.0-2
ii  libkf5configcore5   5.103.0-2
ii  libkf5configgui55.103.0-2
ii  libkf5configwidgets5

Re: Bookworm upgrade to 5.26.90 resulted in a huge App Launcher icon size

[piorunz]

On 01/02/2023 09:17, local10 wrote:


Filed a bug ( https://bugs.kde.org/show_bug.cgi?id=465107 ) in case if someone 
wants to follow it.

My solution was to replace the Application Launcher widget with the Application 
Menu, where the icon still has a resonable size.


I also been affected by this, launcher icon ridiculous size, I use 
vertical panel with size of 256 and that icon was stretched fully to 
that size. Switched to Application Menu like you, thanks.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1029810: dolphin / ark: Error when unpacking RAR archive while unrar is not installed

[piorunz]

Package: dolphin
Version: 4:22.12.1-1
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

How to reproduce:
Make sure unrar and unrar-free packages are NOT installed.
Right click on some RAR file, Extract -> Extract archive here

* What was the outcome of this action?
Dolphin will produce error:
"There was an error while extracting ‘path to file.rar’:
Extraction failed. Make sure that enough space is available."

* What outcome did you expect instead?
Dolphin should produce message:
"Extraction failed.
unrar-free is not installed. Please install unrar-free or unrar to decompress
this archive."

Explanation:
This error message "Make sure that enough space is available" is very
confusing, I thought something is wrong with my system. Dolphin / Ark should
let user know it's not space available problem, but lack of decompress addon to
open the archive.

Note: I am reporting this against Dolphin, because all messages are with title
"Dolphin", and error itself also is in red as a warning inside opened folder
window where this error occured. Looks like Dolphin have handling of errors
like this build-in. So I feel Dolphin could handle it better here. If
inappropriate, please move this bug report to Ark.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dolphin depends on:
ii  baloo-kf5 5.101.0-1
ii  kinit 5.101.0-1
ii  kio   5.101.0-2
ii  libc6 2.36-8
ii  libdolphinvcs54:22.12.1-1
ii  libkf5activities5 5.101.0-1
ii  libkf5baloo5  5.101.0-1
ii  libkf5baloowidgets5   4:22.12.1-1
ii  libkf5bookmarks5  5.101.0-1
ii  libkf5codecs5 5.101.0-1
ii  libkf5completion5 5.101.0-1
ii  libkf5configcore5 5.101.0-1
ii  libkf5configgui5  5.101.0-1
ii  libkf5configwidgets5  5.101.0-1
ii  libkf5coreaddons5 5.101.0-1
ii  libkf5crash5  5.101.0-1
ii  libkf5dbusaddons5 5.101.0-1
ii  libkf5filemetadata3   5.101.0-3
ii  libkf5i18n5   5.101.0-1+b2
ii  libkf5iconthemes5 5.101.0-1+b2
ii  libkf5itemviews5  5.101.0-1
ii  libkf5jobwidgets5 5.101.0-1
ii  libkf5kcmutils5   5.101.0-1
ii  libkf5kiocore55.101.0-2
ii  libkf5kiofilewidgets5 5.101.0-2
ii  libkf5kiogui5 5.101.0-2
ii  libkf5kiowidgets5 5.101.0-2
ii  libkf5newstuff5   5.101.0-1
ii  libkf5newstuffwidgets55.101.0-1
ii  libkf5notifications5  5.101.0-1
ii  libkf5parts5  5.101.0-1
ii  libkf5service-bin 5.101.0-1
ii  libkf5service55.101.0-1
ii  libkf5solid5  5.101.0-1
ii  libkf5textwidgets55.101.0-1
ii  libkf5widgetsaddons5  5.101.0-1
ii  libkf5windowsystem5   5.101.0-2
ii  libkf5xmlgui5 5.101.0-1+b2
ii  libkuserfeedbackcore1 1.2.0-2
ii  libkuserfeedbackwidgets1  1.2.0-2
ii  libpackagekitqt5-11.1.0-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.8+dfsg-2
ii  libqt5dbus5   5.15.8+dfsg-2
ii  libqt5gui55.15.8+dfsg-2
ii  libqt5widgets55.15.8+dfsg-2
ii  libqt5xml55.15.8+dfsg-2
ii  libstdc++612.2.0-14
ii  phonon4qt54:4.11.1-4

Versions of packages dolphin recommends:
ii  ffmpegthumbs  4:22.12.1-1
ii  kdegraphics-thumbnailers  4:22.12.1-1
ii  kimageformat-plugins  5.101.0-2
ii  kio-extras4:22.12.1-1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information

Re: Coloured character borders in kterm

[piorunz]

On 27/01/2023 21:06, Miguel A. Vallejo wrote:

The only bug somewhat related I found is this one

https://bugs.kde.org/show_bug.cgi?id=463024

But I'm not sure if we are talking about the same issue.


So I am reading this bug report. Sub-pixel rendering turned off is 
better visually?


My result is:
$ grep Xft ~/.config/kdeglobals
XftAntialias=true
XftHintStyle=hintslight
XftSubPixel=rgb

And everything is fine, my image on two 4K monitors is crispy sharp, no 
blurry RGB rainbow or whatever, it always has been like that. Is it any 
better if I turn off XftSubPixel?


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Coloured character borders in kterm

[piorunz]

On 27/01/2023 21:06, Miguel A. Vallejo wrote:


The main problem for me is I'm suffering eye strain because of all the
rainbow colors around texts, and because this does not seem to be
resolved anytime soon so I'm seriously thinking of migrating to stable
or any other distribution with more up to date packages. I can't take
this much longer.


Just downgrade to Bookworm repo (current Testing). You should be able to 
do it in your system without reinstalling, just make sure you on top of 
apt and its manual, apt-pinning, when manipulating all packages. From 
Sid to Testing is not very far, and everything works - at least on my 
machine.
I use Testing on only one machine, everything else is on Stable. Stable 
has its name for a good reason.



--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1029774: kdepim-runtime: akonadi_imap_resource crashed with SIGSEGV

[piorunz]

Package: kdepim-runtime
Version: 4:22.12.0-2
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

Today I've noticed akonadi_imap_resource from kdepim-runtime has registered a
SIGSEGV crash in my logs.
Sending all details including backtrace below.

System is Debian Testing AMD64, with redundant storage and ECC RAM, all
packages up to date.

   PID: 13239 (akonadi_imap_re)
   UID: 1000 (pioruns)
   GID: 1000 (pioruns)
Signal: 11 (SEGV)
 Timestamp: Wed 2023-01-25 23:03:16 GMT (1 day 15h ago)
  Command Line: /usr/bin/akonadi_imap_resource --identifier
akonadi_imap_resource_0
Executable: /usr/bin/akonadi_imap_resource
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-
org.kde.kalendarac@autostart.service
  Unit: user@1000.service
 User Unit: app-org.kde.kalendarac@autostart.service
 Slice: user-1000.slice
 Owner UID: 1000 (pioruns)
   Boot ID: 3f0211eb7e694aceafbb8916452990c1
Machine ID: 01568f2c8e7d4695b16a1f32deab7e38
  Hostname: ryzen
   Storage:
/var/lib/systemd/coredump/core.akonadi_imap_re.1000.3f0211eb7e694aceafbb8916452990c1.13239.167468779600.zst
(present)
  Size on Disk: 37.8M
   Message: Process 13239 (akonadi_imap_re) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.4-1.amd64
Module libudev.so.1 from deb systemd-252.4-1.amd64
Stack trace of thread 1814164:
#0  0x7fe82c2a9ccc n/a (libc.so.6 + 0x8accc)
#1  0x7fe82c25aef2 raise (libc.so.6 + 0x3bef2)
#2  0x7fe82af49be1 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5be1)
#3  0x7fe82c25af90 n/a (libc.so.6 + 0x3bf90)
#4  0x7fe82c2a9ccc n/a (libc.so.6 + 0x8accc)
#5  0x7fe82c25aef2 raise (libc.so.6 + 0x3bef2)
#6  0x7fe82c25af90 n/a (libc.so.6 + 0x3bf90)
#7  0x7fe82c2a4d36 n/a (libc.so.6 + 0x85d36)
#8  0x7fe82c2a76dc pthread_cond_timedwait (libc.so.6 +
0x886dc)
#9  0x7fe82c4d19bc
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd19bc)
#10 0x7fe82c4cf0a5 n/a (libQt5Core.so.5 + 0xcf0a5)
#11 0x7fe82c4cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#12 0x7fe82c2a7fd4 n/a (libc.so.6 + 0x88fd4)
#13 0x7fe82c32866c n/a (libc.so.6 + 0x10966c)

Stack trace of thread 13252:
#0  0x7fe82c31b0af __poll (libc.so.6 + 0xfc0af)
#1  0x7fe82b401d12 n/a (libxcb.so.1 + 0xcd12)
#2  0x7fe82b40407a xcb_wait_for_event (libxcb.so.1 +
0xf07a)
#3  0x7fe826afaef0 n/a (libQt5XcbQpa.so.5 + 0x6cef0)
#4  0x7fe82c4cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#5  0x7fe82c2a7fd4 n/a (libc.so.6 + 0x88fd4)
#6  0x7fe82c32866c n/a (libc.so.6 + 0x10966c)

Stack trace of thread 13239:
#0  0x7fe82c31b0af __poll (libc.so.6 + 0xfc0af)
#1  0x7fe82af49160 n/a (libKF5Crash.so.5 + 0x5160)
#2  0x7fe82af49b67 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b67)
#3  0x7fe82c25af90 n/a (libc.so.6 + 0x3bf90)
#4  0x7fe82c62d03a
_ZN9QSettings8setValueERK7QStringRK8QVariant (libQt5Core.so.5 + 0x22d03a)
#5  0x7fe82e1eef05 _ZN7Akonadi9AgentBase9setOnlineEb
(libKF5AkonadiAgentBase.so.5 + 0x1ef05)
#6  0x55f30a6465c4 n/a (akonadi_imap_resource + 0x5a5c4)
#7  0x7fe82c6e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f)
#8  0x55f30a62c756 n/a (akonadi_imap_resource + 0x40756)
#9  0x55f30a6706c9 n/a (akonadi_imap_resource + 0x846c9)
#10 0x7fe82c6e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f)
#11 0x7fe82dda17a5 _ZN4KJob6resultEPS_NS_14QPrivateSignalE
(libKF5CoreAddons.so.5 + 0x6a7a5)
#12 0x7fe82dda2c8b _ZN4KJob9finishJobEb
(libKF5CoreAddons.so.5 + 0x6bc8b)
#13 0x7fe82e4c504a
_ZN5KIMAP3Job18handleErrorRepliesERKNS_8ResponseE (libKF5IMAP.so.5 + 0x5404a)
#14 0x7fe82e4df4f6
_ZN5KIMAP14SessionPrivate16responseReceivedERKNS_8ResponseE (libKF5IMAP.so.5 +
0x6e4f6)
#15 0x7fe82c6dd6f0 _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x2dd6f0)
#16 0x7fe82d362fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#17 0x7fe82c6b16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#18 0x7fe82c6b4681
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5 + 0x2b4681)
#19 0x7fe82c70a153 n/a 

Re: Coloured character borders in kterm

[piorunz]

On 25/01/2023 21:58, Miguel A. Vallejo wrote:

Nobody else noticed this problem?


Debian Testing, after all updates in last 10 days, did not brought this 
issue to my machine. Fonts are still perfect in Konsole. Maybe boot up 
from USB stick with various versions, see if issue is there in Stable, 
Testing, Sid, maybe it's GPU driver, or something else to do with hardware?


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1028197: plasmashell: Program terminated with signal SIGSEGV

[piorunz]

On 24/01/2023 00:05, Bernhard Übelacker wrote:

Am 24.01.23 um 00:30 schrieb piorunz:

On 23/01/2023 22:46, Bernhard Übelacker wrote:

https://bugs.debian.org/1028197

On Mon, 23 Jan 2023 21:48:23 + piorunz  wrote:

On 23/01/2023 13:35, Bernhard Übelacker wrote:
  journalctl --user --since="2023-01-08 12:10" --until="2023-01-08 
12:12"

-- No entries --


Then please try something like this:

   journalctl --user --since="2023-01-08 11:08" --until="2023-01-08 
11:12"


That worked! Attached.




Jan 08 11:11:06 ryzen systemd-coredump[1987371]: Process 1341349 (kded5) 
of user 1000 dumped core.

...
  #3  0x7faafb991f90 
n/a (libc.so.6 + 0x3bf90)
  #4  0x7faa7b2e8ba4 
_ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x1aba4)
  #5  0x7faa7b3a4aae 
n/a (kded_apperd.so + 0xeaae)
  #6  0x7faa7b3a4b99 
n/a (kded_apperd.so + 0xeb99)
  #7  0x7faafb6e8fcf 
n/a (libQt5Core.so.5 + 0x2e8fcf)
  #8  0x7faa7b2dc095 
_ZN10PackageKit6Daemon22transactionListChangedERK11QStringList 
(libpackagekitqt5.so.1 + 0xe095)
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: 
XRandR::setConfig
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: 
Requested screen size is QSize(7680, 2160)
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: 
Needed CRTCs:  2
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: 
Actions to perform:
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]:  Primary 
Output: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: 
kscreen.xrandr: Change Screen Size: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: 
kscreen.xrandr: Disable outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: 
kscreen.xrandr: Change outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: 
kscreen.xrandr: Enable outputs: false
Jan 08 11:11:07 ryzen kscreen_backend_launcher[5795]: kscreen.xrandr: 
XRandR::setConfig done!
Jan 08 11:11:07 ryzen plasmashell[5575]: QFont::setPointSizeF: Point 
size <= 0 (0.00), must be greater than 0

Jan 08 11:11:07 ryzen plasmashell[5575]: 25 -- exe=/usr/bin/plasmashell
Jan 08 11:11:07 ryzen plasmashell[5575]: KCrash: crashing... 
crashRecursionCounter = 2



Here was also just before such a kded5 crash right before.
Either this or the startup of the new kded5 might trigger this,
as it looks like setting up some screen parameters (xrandr).
And while doing this plasmashell wrote
this "QFont::setPointSizeF" message.

Those two upstream bugs appear, but both got closed,
because upstream could not reproduce them:
   https://bugs.kde.org/show_bug.cgi?id=453712
   https://bugs.kde.org/show_bug.cgi?id=462098

I don't know which package management you use,
but until there is a fix for Debian #1026062,
you could experiment with another package manager
like synaptic and uninstall apper for now, as a workaround.

Kind regards,
Bernhard



I use apt + nala to upgrade my system, install and uninstall packages.
Very rarely I ever launch KDE's Discover program. Discover has came with 
Debian's KDE, I did not asked for it to be installed.
apper, about which I didn't know anything until this issue, also came 
with KDE uninvited. Just found this in apt logs:


Start-Date: 2023-01-08  15:03:28
Commandline: apt purge apper
Requested-By: pioruns (1000)
Purge: apper:amd64 (1.0.0-3)
End-Date: 2023-01-08  15:03:30

I uninstalled apper after I reported this bug it seems, thanks to advice 
from Debian KDE mailing list. This particular bug has not returned since 
then. Today I had another desktop crash, but that's probably unrelated. 
I can install apper again if you want me to try and reproduce some more 
of it.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1028197: Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV

[piorunz]

On 23/01/2023 13:35, Bernhard Übelacker wrote:

(gdb) bt
#0  0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fbffe79dbe1 in KCrash::defaultCrashHandler(int) () from 
/lib/x86_64-linux-gnu/libKF5Crash.so.5

#3  
#4  0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#6  
#7  0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x7fbffad3c3b0 in g_closure_invoke () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x7fbffad4f1a5 in ?? () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0



Hello Piotr,
this raise might indicate that libgobject wanted
to stop the process for some reason.
This reason it might have written to stdout/stderr.

Therefore probably you can still retrieve this logging.
 From the "Sun 2023-01-08 13:36:08 GMT" I assume it happend at 14:36
your local time? Then following might possibly show related output.
If there is some could you provide the related parts?

journalctl --user --since="2023-01-08 14:34" --until="2023-01-08 14:38"

Unfortunately there might also be some programs writing to 
~/.xsession-errors,

there the lines are not prefixed with the date and time ...
So it might be difficult to find them there.

Was this just a "one-time" crash, or do you get that regularly?

Kind regards,
Bernhard


Hello Bernhard,

Thanks for your reply. I am not sure what bug you want me to reply to so 
I reply to both.


Plasma, or kwin, or entire desktop crashes all the time. There most 
likely are multiple bugs. This is one of them. Sometimes desktop crashes 
and there is no SIGSEV. Usually I launch Konsole from shortcut, restart 
kwin and plasmashell with --replace option, but this not always helps.

I have modern Radeon GPU, it probably adds fuel to the fire.
Can't wait for more updates regarding kwin/plasmashell/multi monitor 
handling/sleeping and waking up the monitor. There is a lot of bugs in 
these areas, when Radeon GPU is involved at least. I will be happy to 
debug as much as I can, you can tell me what else to do.


$ journalctl --user --since="2023-01-08 14:34" --until="2023-01-08 14:38"
-- No entries --

 journalctl --user --since="2023-01-08 12:10" --until="2023-01-08 12:12"
-- No entries --

.xsession-errors:

Xsession: X session started for pioruns at Sat  7 Jan 08:04:38 GMT 2023
dbus-update-activation-environment: setting 
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting 
XAUTHORITY=/home/pioruns/.Xauthority

localuser:pioruns being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89: 
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:88: 
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89: 
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89: 
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:88: 
ReferenceError: bottomRect is not defined
file:///home/pioruns/.local/share/plasma/look-and-feel/com.github.vinceliuice.Qogir-light/contents/splash/Splash.qml:89: 
ReferenceError: bottomRect is not defined

Xsession: X session started for pioruns at Mon  9 Jan 10:52:01 GMT 2023

This seems to be a session between 7th and 9th January.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Coloured character borders in kterm

[piorunz]

On 16/01/2023 15:37, Miguel A. Vallejo wrote:


Here is the apt log for january 13 and 14

Plenty of packages with something to do with fonts and rendering.
libfreetype6
libfontembed1
fonts-wine
libtiff6
and so on.

And now these packages landed in Testing, packages due to upgrade in my 
system, among others:

  libfreetype-dev
  libfreetype6
  libfreetype6-dev
  libfreetype6:i386
  libgcc-11-dev
  libgl-dev
  libgl1
  libgl1:i386
  libgles-dev
  libgles1
  libgles2

I think I will hold fire upgrading these packages, see what happens.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Coloured character borders in kterm

[piorunz]

On 16/01/2023 00:31, piorunz wrote:


Looks like inverted sub-pixel rendering to me.


Scratch that. Even with inverted RGB, it should NOT have colors.. :| 
Like you have. Shades of blue and brown. That's weird one!


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Coloured character borders in kterm

[piorunz]

On 16/01/2023 00:11, Miguel A. Vallejo wrote:

Hi. What system are you running? Is it even Debian? What versions of
KDE, packages, system? Can't help without info.


Sorry, I forgot the details because I always assume here everyone uses Sid.

Debian Sid, fully updated, as today no packages were kept back.

Konsole version 22.12.1
Plasma version 5.26.5
KDE frameworks version 5.101
QT version 5.15.8
Kernel 6.1.0-1 amd64 running under X11

The problem is also observed in desktop icons, Dolphin, etc (less
noticeable because of the colored background) and in some GTK
applications, like Chrome. It seems to be more noticeable with smaller
font sizes


No, I use Testing. Saves me hassle with broken deps or early bugs.
For me, fonts are perfect:
https://i.imgur.com/UQ5qyIW.png

See if you can configure fonts in this place:
https://i.imgur.com/yjrvQl4.png

Looks like inverted sub-pixel rendering to me. Experiment with settings 
on that page see if you have any results.
Fun fact, some monitors are not RGB but inverted BGR or some other 
combination. They need careful adjustment of sub-pixel rendering for 
best results.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Coloured character borders in kterm

[piorunz]

On 14/01/2023 21:05, Miguel A. Vallejo wrote:


After today's apt-upgrade I noticed all letters in kterm have a
coloured border as you can see in the attached image.

But I also noticed 78 packages have been kept back


Hi. What system are you running? Is it even Debian? What versions of 
KDE, packages, system? Can't help without info.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV

[piorunz]

Package: plasma-discover
Version: 5.26.4-1+b1
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

I just noticed crash of plasma-discover on my Debian Testing machine.

I am using Debian Testing, fully updated, on AMD64 machine with ECC RAM and
RAID1 storage.

Full gdb backtrace attached.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-discover depends on:
ii  appstream0.15.6-1
ii  apt-config-icons 0.15.6-1
ii  kio  5.101.0-2
ii  libappstreamqt2  0.15.6-1
ii  libc62.36-7
ii  libkf5attica55.101.0-1
ii  libkf5configcore55.101.0-1
ii  libkf5configgui5 5.101.0-1
ii  libkf5coreaddons55.101.0-1
ii  libkf5crash5 5.101.0-1
ii  libkf5dbusaddons55.101.0-1
ii  libkf5i18n5  5.101.0-1+b1
ii  libkf5idletime5  5.101.0-2
ii  libkf5jobwidgets55.101.0-1
ii  libkf5kiocore5   5.101.0-2
ii  libkf5kiogui55.101.0-2
ii  libkf5newstuffcore5  5.101.0-1
ii  libkf5notifications5 5.101.0-1
ii  libkf5service-bin5.101.0-1
ii  libkf5service5   5.101.0-1
ii  libkf5widgetsaddons5 5.101.0-1
ii  libkf5windowsystem5  5.101.0-2
ii  libmarkdown2 2.2.7-2
ii  libpackagekitqt5-1   1.1.0-1
ii  libqt5core5a 5.15.7+dfsg-2
ii  libqt5dbus5  5.15.7+dfsg-2
ii  libqt5gui5   5.15.7+dfsg-2
ii  libqt5network5   5.15.7+dfsg-2
ii  libqt5qml5   5.15.7+dfsg-2
ii  libqt5quick5 5.15.7+dfsg-2
ii  libqt5webview5   5.15.7-2
ii  libqt5widgets5   5.15.7+dfsg-2
ii  libqt5xml5   5.15.7+dfsg-2
ii  libstdc++6   12.2.0-13
ii  packagekit   1.2.6-1
ii  plasma-discover-common   5.26.4-1
ii  qml-module-org-kde-kcoreaddons   5.101.0-1
ii  qml-module-org-kde-kirigami2 5.101.0-1+b1
ii  qml-module-org-kde-kquickcontrols5.101.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.101.0-1
ii  qml-module-org-kde-qqc2desktopstyle  5.101.0-1
ii  qml-module-qtquick-dialogs   5.15.7-2

Versions of packages plasma-discover recommends:
ii  apt-config-icons-hidpi 0.15.6-1
ii  apt-config-icons-large 0.15.6-1
ii  apt-config-icons-large-hidpi   0.15.6-1
ii  kde-config-updates 5.26.4-1+b1
ii  plasma-discover-backend-fwupd  5.26.4-1+b1
ii  software-properties-kde0.96.20.2-2.1

Versions of packages plasma-discover suggests:
pn  plasma-discover-backend-flatpak  

-- no debconf information
   PID: 2832872 (plasma-discover)
   UID: 1000 (pioruns)
   GID: 1000 (pioruns)
Signal: 11 (SEGV)
 Timestamp: Sun 2023-01-08 13:36:08 GMT (1h 29min ago)
  Command Line: /usr/bin/plasma-discover appstream://sgt-map.desktop
Executable: /usr/bin/plasma-discover
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.urlhandler-8fcfc6530e104bb7a31ca8d2ddcae0dc.scope
  Unit: user@1000.service
 User Unit: 
app-org.kde.discover.urlhandler-8fcfc6530e104bb7a31ca8d2ddcae0dc.scope
 Slice: user-1000.slice
 Owner UID: 1000 (pioruns)
   Boot ID: d4d94006660c4c26903fb792a9dd31e4
Machine ID: 01568f2c8e7d4695b16a1f32deab7e38
  Hostname: ryzen
   Storage: 
/var/lib/systemd/coredump/core.plasma-discover.1000.d4d94006660c4c26903fb792a9dd31e4.2832872.167318496800.zst
 (present)
  Size on Disk: 28.2M
   Message: Process 2832872 (plasma-discover) of user 1000 dumped core.

Module libudev.so.1 from deb systemd-252.4-1.amd64
Module libsystemd.so.0 from deb systemd-252.4-1.amd64
Stack trace of thread 2832899:
#0  0x7fbffc2a9ccc n/a (libc.so.6 + 0x8accc)
#1  0x7fbffc25aef2 raise (libc.so.6 + 0x3bef2)
#2  0x7fbffe79dbe1 _ZN6KCrash19defaultCrashHandlerEi 
(libKF5Crash.so.5 + 0x5be1)
#3  0x7fbffc25af90 

Re: plasmashell crashes

[piorunz]

On 08/01/2023 11:43, Martin Steigerwald wrote:

piorunz - 08.01.23, 12:33:06 CET:

Debian Testing is experiencing high volume of plasmashell and kded5
crashes. Just caught clean crash of plasmashell with full backtrace, I
was clicking nothing on the desktop with focus on another program,
and plasmashell just crashed. But this time it restarted itself and
desktop was usable again immediately, so I didn't wasted my work.
X11, Radeon card, AMD64 machine with ECC RAM and RAID1 storage.
Bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028197


No crashes here on Unstable.

ThinkPad T14 AMD Gen 1 with integrated AMD Renoir Vega 7 graphics.

Don't have Apper installed.

Ciao,


Hi.
I have apper installed. "KDE package management tool using PackageKit".
What is it for, can I uninstall it without consequence? I don't use 
Discover or other KDE tools too much to install software, and can live 
without it, if it comes to that.



--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

plasmashell crashes

[piorunz]

Hi all,

Debian Testing is experiencing high volume of plasmashell and kded5 
crashes. Just caught clean crash of plasmashell with full backtrace, I 
was clicking nothing on the desktop with focus on another program, and 
plasmashell just crashed. But this time it restarted itself and desktop 
was usable again immediately, so I didn't wasted my work.

X11, Radeon card, AMD64 machine with ECC RAM and RAID1 storage.
Bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028197


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1028197: plasmashell: Program terminated with signal SIGSEGV

[piorunz]

Package: plasma-workspace
Version: 4:5.26.4.1-1+b1
Severity: important
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

plasmashell is crashing very often on Debian Testing.
Latest crash happened just now, segmentation fault. Plasmashell, along with all
icons and panels disappeared completely and launched again.

I am using Debian Testing, fully updated, on AMD64 machine with ECC RAM and
RAID1 storage.

Full gdb backtrace attached.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]1.14.4-1
ii  drkonqi 5.26.4-1
ii  frameworkintegration5.101.0-1
ii  gdb-minimal [gdb]   12.1-4+b1
ii  init-system-helpers 1.65.2
ii  iso-codes   4.12.0-1
ii  kactivitymanagerd   5.26.4-1
ii  kded5   5.101.0-1
ii  kinit   5.101.0-1
ii  kio 5.101.0-2
ii  kpackagetool5   5.101.0-1
ii  kwin-common 4:5.26.4-1+b1
ii  libappstreamqt2 0.15.6-1
ii  libc6   2.36-7
ii  libcolorcorrect54:5.26.4.1-1+b1
ii  libcrypt1   1:4.4.33-1
ii  libfontconfig1  2.13.1-4.5
ii  libfreetype62.12.1+dfsg-3
ii  libgcc-s1   12.2.0-13
ii  libgps283.22-4.1+b1
ii  libice6 2:1.0.10-1
ii  libicu7272.1-3
ii  libkf5activities5   5.101.0-1
ii  libkf5activitiesstats1  5.101.0-1
ii  libkf5archive5  5.101.0-1
ii  libkf5authcore5 5.101.0-1
ii  libkf5baloo55.101.0-1
ii  libkf5bookmarks55.101.0-1
ii  libkf5calendarevents5   5.101.0-1
ii  libkf5completion5   5.101.0-1
ii  libkf5config-bin5.101.0-1
ii  libkf5configcore5   5.101.0-1
ii  libkf5configgui55.101.0-1
ii  libkf5configwidgets55.101.0-1
ii  libkf5coreaddons5   5.101.0-1
ii  libkf5crash55.101.0-1
ii  libkf5dbusaddons5   5.101.0-1
ii  libkf5declarative5  5.101.0-1
ii  libkf5globalaccel-bin   5.101.0-1
ii  libkf5globalaccel5  5.101.0-1
ii  libkf5guiaddons55.101.0-1
ii  libkf5holidays5 1:5.101.0-1
ii  libkf5i18n5 5.101.0-1+b1
ii  libkf5iconthemes5   5.101.0-1+b1
ii  libkf5idletime5 5.101.0-2
ii  libkf5jobwidgets5   5.101.0-1
ii  libkf5kcmutils5 5.101.0-1
ii  libkf5kexiv2-15.0.0 22.12.0-2
ii  libkf5kiocore5  5.101.0-2
ii  libkf5kiofilewidgets5   5.101.0-2
ii  libkf5kiogui5   5.101.0-2
ii  libkf5kiowidgets5   5.101.0-2
ii  libkf5networkmanagerqt6 5.101.0-1
ii  libkf5newstuff5 5.101.0-1
ii  libkf5newstuffcore5 5.101.0-1
ii  libkf5newstuffwidgets5  5.101.0-1
ii  libkf5notifications55.101.0-1
ii  libkf5notifyconfig5 5.101.0-1
ii  libkf5package5  5.101.0-1
ii  libkf5parts55.101.0-1
ii  libkf5people5   5.101.0-1
ii  libkf5peoplewidgets5

Re: kded5 crashes

[piorunz]

On 07/12/2022 14:47, tv.debian wrote:

Is there a bug report opened somewhere?


Bug report opened on 13th December. I added backtrace from crashes in my 
machine too.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1026062: kded5: kded crashes with signal 11

[piorunz]

Package: kded5
Version: 5.101.0-1
Followup-For: Bug #1026062
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

I can also observe this problem. Just booted my computer, first I see in "sudo
coredumpctl list", is freshly crashed kded5:

$ sudo coredumpctl list
Sat 2023-01-07 08:09:54 GMT5500 1000 1000 SIGSEGV present  /usr/bin/kded5
4.2M

service status confirm this:
 systemctl --user status plasma-kded
× plasma-kded.service - KDE Daemon
 Loaded: loaded (/usr/lib/systemd/user/plasma-kded.service; static)
 Active: failed (Result: core-dump) since Sat 2023-01-07 08:09:54 GMT; 6min
ago
   Duration: 5min 13.302s
Process: 5500 ExecStart=/usr/bin/kded5 (code=dumped, signal=SEGV)
   Main PID: 5500 (code=dumped, signal=SEGV)
CPU: 1.637s

Jan 07 08:09:52 ryzen kded5[5500]: KCrash: Attempting to start
/usr/lib/x86_64-linux-gnu/libexec/drkonqi
Jan 07 08:09:52 ryzen kded5[5500]: QSocketNotifier: Invalid socket 11 and type
'Read', disabling...
Jan 07 08:09:52 ryzen kded5[5500]: QSocketNotifier: Invalid socket 17 and type
'Read', disabling...
Jan 07 08:09:52 ryzen kded5[5500]: QSocketNotifier: Invalid socket 47 and type
'Read', disabling...
Jan 07 08:09:53 ryzen kded5[5500]: Unable to start Dr. Konqi
Jan 07 08:09:53 ryzen kded5[5500]: Re-raising signal for core dump handling.
Jan 07 08:09:54 ryzen systemd-coredump[47140]: [] Process 5500 (kded5) of user
1000 dumped core.

   Module libudev.so.1 from deb
systemd-252.4-1.amd64
   Module libsystemd.so.0 from deb
systemd-252.4-1.amd64
   Stack trace of thread 5500:
   #0  0x7f292a9e5bb4
pthread_sigmask (libc.so.6 + 0x8fbb4)
   #1  0x7f292a992179
sigprocmask (libc.so.6 + 0x3c179)
   #2  0x7f292bb09eab
_ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4eab)
   #3  0x7f292bb0abd9
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5bd9)
   #4  0x7f292a991f90 n/a
(libc.so.6 + 0x3bf90)
   #5  0x7f28b2308ba4
_ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x1aba4)
   #6  0x7f28b23c4aae n/a
(kded_apperd.so + 0xeaae)
   #7  0x7f28b23c4b99 n/a
(kded_apperd.so + 0xeb99)
   #8  0x7f292a6e8fcf n/a
(libQt5Core.so.5 + 0x2e8fcf)
   #9  0x7f28b22fc095
_ZN10PackageKit6Daemon22transactionListChangedERK11QStringList
(libpackagekitqt5.so.1 + 0xe095)
   #10 0x7f292a6e8ffc n/a
(libQt5Core.so.5 + 0x2e8ffc)
   #11 0x7f28b2314b38 n/a
(libpackagekitqt5.so.1 + 0x26b38)
   #12 0x7f28b2315d73 n/a
(libpackagekitqt5.so.1 + 0x27d73)
   #13 0x7f292b32661b n/a
(libQt5DBus.so.5 + 0x2361b)
   #14 0x7f292a6dd770
_ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd770)
   #15 0x7f292b562f5e
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162f5e)
   #16 0x7f292a6b17c8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b17c8)
   #17 0x7f292a6b4761
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5 + 0x2b4761)
   #18 0x7f292a70a1d3 n/a
(libQt5Core.so.5 + 0x30a1d3)
   #19 0x7f292951e7a9
g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9)


Full gdb coredump and backtrace included in the attachment.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kded5 depends on:
ii  libc6  2.36-7
ii  libkf5configcore5  5.101.0-1
ii  libkf5coreaddons5  5.101.0-1
ii  libkf5crash5   5.101.0-1
ii  libkf5dbusaddons5  5.101.0-1
ii  libkf5service-bin  5.101.0-1
ii  libkf5service5 5.101.0-1
ii  libqt5core5a   5.15.7+dfsg-2
ii  libqt5dbus55.15.7+dfsg-2
ii  libqt5gui5 5.15.7+dfsg-2
ii  libqt5widgets5 

Re: kded5 crashes

[piorunz]

On 07/12/2022 00:46, Diederik de Haas wrote:

It looks like I'm not having those issues, but your report did prompt me
to look in syslog ... and that looks like KDE's debug log?!?


2023-01-04T20:50:31.002430+00:00 ryzen kglobalaccel5[433966]: Invalid 
return type in method "addAction"
2023-01-04T20:50:31.002448+00:00 ryzen kglobalaccel5[433966]: Skipped 
method "setDefaultShortcuts" : Pointers are not supported: QAction*
2023-01-04T20:50:31.012326+00:00 ryzen kglobalaccel5[2669877]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.012357+00:00 ryzen kglobalaccel5[2669877]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.012718+00:00 ryzen kglobalaccel5[2669877]: Invalid 
return type in method "addAction"
2023-01-04T20:50:31.012747+00:00 ryzen kglobalaccel5[2669877]: Skipped 
method "setDefaultShortcuts" : Pointers are not supported: QAction*
2023-01-04T20:50:31.025360+00:00 ryzen kglobalaccel5[3565037]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.025400+00:00 ryzen kglobalaccel5[3565037]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.025653+00:00 ryzen kglobalaccel5[3565037]: Invalid 
return type in method "addAction"
2023-01-04T20:50:31.025668+00:00 ryzen kglobalaccel5[3565037]: Skipped 
method "setDefaultShortcuts" : Pointers are not supported: QAction*
2023-01-04T20:50:31.038086+00:00 ryzen kglobalaccel5[3663985]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.038110+00:00 ryzen kglobalaccel5[3663985]: 
Unsupported return type 65 QPixmap in method "grab"
2023-01-04T20:50:31.038402+00:00 ryzen kglobalaccel5[3663985]: Invalid 
return type in method "addAction"
2023-01-04T20:50:31.038429+00:00 ryzen kglobalaccel5[3663985]: Skipped 
method "setDefaultShortcuts" : Pointers are not supported: QAction*
2023-01-04T20:56:34.498590+00:00 ryzen kglobalaccel5[3702650]: Omitting 
both --window and --windowclass arguments is not recommended
2023-01-04T20:56:34.631005+00:00 ryzen kglobalaccel5[3702659]: 
kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.
2023-01-04T20:56:34.631096+00:00 ryzen kglobalaccel5[3702659]: 
kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.
2023-01-04T21:04:34.087617+00:00 ryzen kglobalaccel5[3752214]: Omitting 
both --window and --windowclass arguments is not recommended
2023-01-04T21:04:34.221507+00:00 ryzen kglobalaccel5[3752838]: 
kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.
2023-01-04T21:04:34.221593+00:00 ryzen kglobalaccel5[3752838]: 
kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.
2023-01-04T21:08:36.695088+00:00 ryzen kglobalaccel5[3777855]: Omitting 
both --window and --windowclass arguments is not recommended
2023-01-04T21:08:36.829862+00:00 ryzen kglobalaccel5[3777864]: 
kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.
2023-01-04T21:08:36.829961+00:00 ryzen kglobalaccel5[3777864]: 
kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with 
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) 
instead.


That's only last 18 minutes of the log ;)

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

[backtrace] kded5 crashes

[piorunz]

On 06/12/2022 12:45, Miguel A. Vallejo wrote:

Since a few days ago I've been experiencing problems with KDE in a
fully upgraded Sid.

The symptoms are always the same: kded5 crashes a few minutes after
boot and then icons from no KDE programs (like Telegram) disappears
from the system tray.

A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself.
Any ideas?


Confirming, dozens of kwin, plasmashell, kded5 crashes, very often. I 
run "kwin --replace" and "plasmashell --replace" commands in Konsole 
terminal, as I can quickly kill and restore them when things glitch.
I don't know any better solution which allows me to continue using 
desktop without full restart or killing X by Ctrl+Alt+Backspace 
combination, which I really would like to avoid.

KDE desktop freezes or glitch every 24h of active desktop use, on average.
I use fully updated Debian Testing, on AMD64, with Radeon 6800 XT card, 
X11 display, two monitors. kded5 shows Version: 5.101.0-1.


Crashes today:
Wed 2023-01-04 11:19:06 GMT 3813232 1000 1000 SIGSEGV present 
/usr/bin/kded5   6.5M
Wed 2023-01-04 11:20:26 GMT 1197737 1000 1000 SIGSEGV present 
/usr/bin/kded5   6.3M
Wed 2023-01-04 11:20:29 GMT 1209714 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.5M
Wed 2023-01-04 11:20:35 GMT 1210113 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.5M
Wed 2023-01-04 11:20:38 GMT 1211582 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.5M
Wed 2023-01-04 11:20:48 GMT 1212583 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.5M
Wed 2023-01-04 11:20:53 GMT 1217289 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.5M
Wed 2023-01-04 11:20:56 GMT 1218407 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.2M
Wed 2023-01-04 14:17:53 GMT 1219170 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.3M
Wed 2023-01-04 14:17:55 GMT 2269708 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.2M
Wed 2023-01-04 14:17:57 GMT 2269821 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.2M
Wed 2023-01-04 14:17:58 GMT 2269927 1000 1000 SIGSEGV present 
/usr/bin/kded5   4.2M


Closer look at last four: four consecutive crashes in a few seconds. 
They are different, crashing on something else.


Full gdb backtrace of first crash Wed 2023-01-04 14:17:53 GMT
https://paste.debian.net/1266164/

And the last one:
https://paste.debian.net/1266163/

Has anyone opened bug report yet? If not, against which package we can 
open it? kded5?


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

[piorunz]

On 09/09/2022 00:24, Lisandro Damián Nicanor Pérez Meyer wrote:


To be honest that could be a gazillion things. This is clearly related
to rendering, thus it can easily be an issue on the graphics driver...
I am also figuring that it's complicated to replicate, right? Or you
can easily replicate it every time you suspend/resume your machine?

Regards, Lisandro.


Yes I think this is related to GPU driver (AMD Radeon card).
Because its glitching sometimes and sometimes I have to kill X session.

I will be happy to provide more logs and maybe move this bug to other
relevant package, but how to catch and identify this bug in more detail?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

[piorunz]

Package: libqt5core5a
Version: 5.15.4+dfsg-5
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

I Did suspend/resume cycle of my computer.
Later I found in dmesg:

[96111.865203] QSGRenderThread[569483]: segfault at 0 ip 7fe450b2bcfb sp
7fe411703950 error 4 in libQt5Core.so.5.15.4[7fe450ae9000+301000]
[96111.865213] Code: 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 e8 c9
a4 ff ff 48 85 c0 0f 84 4a 11 fc ff 48 89 c3 4c 8d 68 50 48 8b 40 50 <49> 63 2c
24 3b 68 04 7d 6c 8b 10 83 fa 01 76 25 8b 70 08 81 e6 ff

   * What outcome did you expect instead?
No error at all


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5core5a depends on:
ii  libc6  2.34-7
ii  libdouble-conversion3  3.2.1-1
ii  libgcc-s1  12.2.0-1
ii  libglib2.0-0   2.73.3-3
ii  libicu71   71.1-3
ii  libpcre2-16-0  10.40-1
ii  libstdc++6 12.2.0-1
ii  libzstd1   1.5.2+dfsg-1
ii  shared-mime-info   2.2-1
ii  zlib1g 1:1.2.11.dfsg-4.1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.4-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.29-1

-- no debconf information

Re: plasma 25.4

[piorunz]

On 11/08/2022 00:02, local10 wrote:

Aug 10, 2022, 22:21 by pior...@gmx.com:


Unfortunately, changing this from 1 to 2 has no effect.
Icons are still too small for 4K screen. Before, I could adjust panel
size and icons were scaling. Now, they are fixed in (too small) size.




Perhaps you may want to add your feedback to this bug: 
https://bugs.kde.org/show_bug.cgi?id=457379


Regards,


Thanks, comment added.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma 25.4

[piorunz]

On 10/08/2022 21:31, local10 wrote:

Aug 10, 2022, 16:29 by pior...@gmx.com:


Where is this iconSpacing setting? I can't find it in KDE Icons
settings, or in Task Manager settings.




See the bottom of the 
"/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/config/main.xml


Unfortunately, changing this from 1 to 2 has no effect.
Icons are still too small for 4K screen. Before, I could adjust panel
size and icons were scaling. Now, they are fixed in (too small) size.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma 25.4

[piorunz]

On 10/08/2022 01:28, local10 wrote:

IIRC, there used to be a way to change the icon size on the Task Manager's Appearance 
tab, but now it's gone. See if changing the "iconSpacing" setting helps, for me 
it didn't. Logging  out of KDE is needed for the change to take effect.

Regards,


Where is this iconSpacing setting? I can't find it in KDE Icons
settings, or in Task Manager settings.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma 25.4

[piorunz]

On 10/08/2022 00:28, piorunz wrote:

In KDE settings, under Appearance/Icons, I can set icon sizes for 
Toolbar, Main Toolbar, Small Icons, Panel, Dialogues. But not for Task 
Manager. Task Manager icons are fixed.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma 25.4

[piorunz]

On 09/08/2022 23:21, local10 wrote:

Aug 9, 2022, 14:19 by pior...@gmx.com:


Yes, KDE 5.25.4 is up and running. Everything fine, so far!




Can't really say the same. 25.4.3 had created some issues for me[1][2] that 
continued in 25.4.4, the devs say some are resolved in 25.4.5. So what are the 
plans for 25.4.5? Also, any plans for elisa 22.04.3 [3]?

Thanks


1. https://bugs.kde.org/show_bug.cgi?id=457357
2. https://bugs.kde.org/show_bug.cgi?id=457379
3. https://bugs.kde.org/show_bug.cgi?id=457510


I've read your bug reports. I also have been affected by Task Manager
issue. Now I realized, recent changes were not so positive after all :)

For me, Task Manager icons have become too small on 4K screen. I also
use vertical panel on which Task Manager is located. Panel has 256
pixels width.
Before update, changing size of the panel was scaling icons in Task
Manager as well. Now, they are fixed in size.

https://i.imgur.com/Mqd4ZrC.png

Icons used to be much bigger before. Now, they are a bit too small and I
have no way to change their size.
Any solution for this?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: plasma 25.4

[piorunz]

On 08/08/2022 07:21, Luc Castermans wrote:

Dear

Just saw many Plasma 25.4 packages being installed. Thank you very much!


Yes, KDE 5.25.4 is up and running. Everything fine, so far!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 19/04/2022 08:03, Andrey Rahmatullin wrote:

On Mon, Apr 18, 2022 at 08:41:13PM +0100, piorunz wrote:

Thank you all,

I was able to uninstall many akonadi packages, including akonadi server,
and installed back (marked as installed manually) LibreOffice, system
printing and few other things. Unfortunately akregator which I use
(sporadically) still requires a few akonadi packages:
$ dpkg -l | grep akona | awk {print'$2'}
akonadi-contacts-data
akonadi-mime-data
libkf5akonadi-data
libkf5akonadicontact5:amd64
libkf5akonadicore5abi2:amd64
libkf5akonadimime5:amd64
libkf5akonadiprivate5abi2:amd64
libkf5akonadiwidgets5abi1:amd64
libkf5mailtransportakonadi5:amd64

None of these include the actual service. When in doubt you should read
package descriptions, though often package names are enough.


Yep, I thought so. Actual service is akonadi-server and other things.
Anyway, all of it has been nuked.
You seen my previous post with imgur link? 16 cores saturated and
cranked to 4.4 GHz that's quite a lot of electricity burned in vain, I
don't need any more heating up of my living room haha.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 18/04/2022 23:21, Xavier Brochard wrote:

Le 18.04.2022 21:41, piorunz a écrit :

Unfortunately akregator which I use
(sporadically)


Thunderbird can read RSS/Atom feeds


Yes, and I use it too... Don't know why I didn't merged them before. I
just moved them all to TB, full success. Akregator is gone, so is
akonadi :) dpkg is clean, no more akonadi found. This group is
invaluable as always - thank you Xavier!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

Thank you all,

I was able to uninstall many akonadi packages, including akonadi server,
and installed back (marked as installed manually) LibreOffice, system
printing and few other things. Unfortunately akregator which I use
(sporadically) still requires a few akonadi packages:
$ dpkg -l | grep akona | awk {print'$2'}
akonadi-contacts-data
akonadi-mime-data
libkf5akonadi-data
libkf5akonadicontact5:amd64
libkf5akonadicore5abi2:amd64
libkf5akonadimime5:amd64
libkf5akonadiprivate5abi2:amd64
libkf5akonadiwidgets5abi1:amd64
libkf5mailtransportakonadi5:amd64

I will keep them for now so akregator can work. I hope I will not
encounter any problem with akonadi again, now when almost all of it is
uninstalled.

Thanks all for your help!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 15/04/2022 11:07, Andrey Rahmatullin wrote:

On Fri, Apr 15, 2022 at 11:05:03AM +0100, piorunz wrote:

Yes, totally. Why this abomination cannot be uninstalled without pulling
half of KDE out?

This is definitely not true.


$ sudo apt purge akonadi-server

[...]

The following packages will be REMOVED:
   akonadi-server* kaddressbook* kde-standard* kdepim-runtime* kmail*
knotes* korganizer* task-kde-desktop*
0 upgraded, 0 newly installed, 8 to remove and 1 not upgraded.

Correct.


Printing gone. Libreoffice gone. Speech gone. That's what I can see here.

No, you should learn to read the apt output before drawing conclusions.


I probably know what you mean. Thanks. You mean I can install them
manually, and they will stay as manually installed?
So only akonadi-server* kaddressbook* kde-standard* kdepim-runtime*
kmail* knotes* korganizer* task-kde-desktop* will be gone effectively?

Shouldn't I have task-kde-desktop installed to track all packages
required by entire KDE? So my Testing system evolves with changing deps?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 15/04/2022 11:03, Andrey Rahmatullin wrote:

On Fri, Apr 15, 2022 at 10:56:28AM +0100, piorunz wrote:

Yes, totally. Why this abomination cannot be uninstalled without pulling
half of KDE out?

This is definitely not true.


$ sudo apt purge akonadi-server
[sudo] password for pioruns:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer
required:
  accountwizard akonadi-backend-mysql apper apper-data coinor-libcbc3
coinor-libcgl1 coinor-libclp1 coinor-libcoinmp1v5 coinor-libcoinutils3v5
coinor-libosi1v5 cups-pk-helper default-mysql-client-core
  default-mysql-server-core espeak-ng-data gir1.2-atspi-2.0
gir1.2-wnck-3.0 hyphen-en-us kaddressbook-data kdeaccessibility
kdepim-addons kdepim-themeeditors kio-ldap kmag kmailtransport-akonadi
  kmousetool kmouth kontrast libatk-adaptor libbox2d2 libcdr-0.1-1
libdotconf0 libespeak-ng1 libfreehand-0.1-1 libkf5akonadiagentbase5
libkf5akonadicalendar-data libkf5akonadicalendar5abi1
  libkf5akonadinotes5 libkf5akonadisearch-bin libkf5akonadisearch-data
libkf5akonadisearch-plugins libkf5akonadisearchcore5
libkf5akonadisearchdebug5 libkf5akonadisearchpim5 libkf5akonadisearchxapian5
  libkf5alarmcalendar-data libkf5alarmcalendar5abi1
libkf5calendarcore5abi2 libkf5calendarsupport-data
libkf5calendarsupport5abi1 libkf5calendarutils5 libkf5dav-data
libkf5dav5 libkf5eventviews-data
  libkf5eventviews5abi1 libkf5imap-data libkf5imap5
libkf5incidenceeditor-data libkf5incidenceeditor5abi1
libkf5kmanagesieve5 libkf5ksieve-data libkf5ksieve5 libkf5ksieveui5
libkf5ldap-data
  libkf5ldap5abi1 libkf5mailcommon-data libkf5mailcommon5abi2
libkf5mailimporter5 libkf5mailimporterakonadi5
libkf5messagecomposer5abi1 libkf5messagelist5abi1 libkf5pimcommon-data
  libkf5pimcommonakonadi5abi1 libkf5templateparser5 libkf5tnef5
libkgantt2 libkgantt2-l10n libkolabxml1v5
libkpimaddressbookimportexport5 libkpimgapicalendar5
libkpimgapicontacts5 libkpimgapitasks5
  libkpimimportwizard5 libkpimitinerary-data libkpimitinerary5
libkpimpkpass5 libmspub-0.1-1 libpagemaker-0.0-0 libpcaudio0
libphonenumber8 libqaccessibilityclient-qt5-0 libqt5networkauth5
libqxp-0.0-0
  libreoffice-calc libreoffice-draw libreoffice-help-en-us
libreoffice-impress libreoffice-kf5 libreoffice-plasma libreoffice-qt5
libsasl2-modules-kdexoauth2 libsonic0 libstartup-notification0
  libvisio-0.1-1 libwnck-3-0 libwnck-3-common libxerces-c3.2
libzmf-0.0-0 lp-solve mbox-importer mythes-en-us orca perl-tk
pim-data-exporter pim-sieve-editor print-manager python3-brlapi
  python3-cupshelpers python3-louis python3-pyatspi python3-smbc
python3-speechd qtgstreamer-plugins-qt5 sound-icons speech-dispatcher
speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng
  system-config-printer-common system-config-printer-udev xbrlapi xkbset
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  akonadi-server* kaddressbook* kde-standard* kdepim-runtime* kmail*
knotes* korganizer* task-kde-desktop*
0 upgraded, 0 newly installed, 8 to remove and 1 not upgraded.
After this operation, 63.3 MB disk space will be freed.
Do you want to continue? [Y/n]


Printing gone. Libreoffice gone. Speech gone. That's what I can see here.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 15/04/2022 09:37, Martin Steigerwald wrote:


Well on those systems where I do not use Akonadi and switch to SQLite3.

Please do not do this without having a good reason to do it, in case you
actually use Akonadi.

There is potential data loss – i.e. loosing mails, appointments,
contacts – in there, since Akonadi is unfortunately not just a read
cache, but a time-limited – or unlimited in case of a certain
conditation – write cache where things may end to be stored just in the
database for a limited or even an unlimited time ("item without RID"
message in akonadictl fsck).


I never ever used Akonadi database AFAIK. I don't use KDE contacts,
KMail, or any of that.
I use "Plasma Search" in KRunner, is that in Akonadi, or something separate?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Akonadi using 100% CPU resources

[piorunz]

On 15/04/2022 09:31, Martin Steigerwald wrote:


Which processes of Akonadi are using up the CPU? In case it is just a
certain process like "akonadi_indexing_agent", well what I did with this
one is:

chmod 000 /usr/bin/akonadi_indexing_agent

It works.


All of them.
Screenshot:
https://imgur.com/vJFrPPR

Thank you, I will try to block all executables so they never run again.


Do you really not use it? Look at

du -sch ~/.local/share/akonadi/* | sort -rh

If you really do you use it, this should be almost empty beside some
MariaDB journal files.


I nuked that directory yesterday without checking what's inside. Today,
with akonadi stopped, my system works perfectly fine as expected. That
shows how badly (not) my system needs akonadi.


Note: In case you store contacts in KAdressbook or use a calender with
KOrganizer, you actually *use* Akonadi. Akonadi is not just about
storing mails for KMail.


I don't use any of that. I use Thunderbird with its contacts.


What I do on systems where I do not use Akonadi – it may even work well
on systems where it is used – is to replace "akonadi-backend-mysql" by
"akonadi-backend-sqlite". That way I get rid of an additional full blown
database process.

I usually also stop Akonadi with

akonadictl stop

And then do

rm -r ~/.local/share/akonadi

rm -r ~/.config/akonadi


Yes, that's what I did. I killed all processes (had to resort to signal
9) and nuked both directories.



I still believe the end user should not have to do with any of this.


Indeed. Akonadi should never use all of my machine 16 cores in the first
place.


Akonadi is something that drags down the overall good Plasma / KDE
experience unfortunately since more than a decade. I defended it earlier
on. Meanwhile I think it is better to completely replace it.


Yes, totally. Why this abomination cannot be uninstalled without pulling
half of KDE out? Shouldn't that be reported as a bug?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Akonadi using 100% CPU resources

[piorunz]

Hi all,

I noticed that akonadi services are using 100% of 16-core CPU resources
on my machine. I don't even use Kmail, I use Thunderbird. I'm not even
sure what akonadi is for. I have following packages installed:

$ dpkg -l | grep akonadi | awk {'print $2'}
akonadi-backend-mysql
akonadi-contacts-data
akonadi-mime-data
akonadi-server
kmailtransport-akonadi:amd64
libkf5akonadi-data
libkf5akonadiagentbase5:amd64
libkf5akonadicalendar-data
libkf5akonadicalendar5abi1:amd64
libkf5akonadicontact5:amd64
libkf5akonadicore5abi2:amd64
libkf5akonadimime5:amd64
libkf5akonadinotes5:amd64
libkf5akonadiprivate5abi2:amd64
libkf5akonadisearch-bin
libkf5akonadisearch-data
libkf5akonadisearch-plugins:amd64
libkf5akonadisearchcore5:amd64
libkf5akonadisearchdebug5:amd64
libkf5akonadisearchpim5:amd64
libkf5akonadisearchxapian5:amd64
libkf5akonadiwidgets5abi1:amd64
libkf5mailimporterakonadi5:amd64
libkf5mailtransportakonadi5:amd64
libkf5pimcommonakonadi5abi1:amd64

System is Debian Testing.

How can I get rid of that akonadi, or disable it?

I can't uninstall akonadi-server, because it wants to uninstall with it:
akonadi-server* kaddressbook* kde-standard* kdepim-runtime* kmail*
knotes* korganizer* task-kde-desktop*

And dozens of libraries.

Any help appreciated.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Dolphin problems with NFS file transfer cancellation

[piorunz]

Hi all,

I experience Dolphin problems when moving files from local folder to NFS
share.

How to reproduce:
Mount NFS share in some folder.
Select big files from your local computer and start moving them to NFS
share.
Transfer starts (LAN + Gigabit Ethernet, basically two computers next to
each other)
ALL Dolphin windows become unresponsive at this point. Very very slow
reaction. Basically I can't do nothing, window responds after 30 seconds
or a minute. But transfer progresses nicely in the background.
At some point 10 minutes later I cancel the transfer, because I need to
go away and sleep the computer.
I click Cancel in Dolpin Moving Files notification window
Notification dissapears, but I see that network transfers still going in
bpytop.
5 minutes later, network transfers are still going.
I try to sleep computer. Nothing happens, sleep is prevented.
I look info dmesg. kernel critical error - INFO: task dolphin:1775617
blocked for more than 120 seconds. and Call Trace (log file attached)
Somehow I figure that umount -f /home/user/myNFSshare will help. I issue
the command.
Computer immediately goes to sleep as intended.
Upon waking up next day, everything is as usual, all normal.

This problem only happens when I want to cancel transfer. Dolphin don't
know how to CANCEL the tranfer. If I don't cancel and let it run,
everything is fine.

Is this KDE issue or Linux kernel issue? Where to report a bug?
I use clean Debian Testing, untainted kernel. No weird stuff, almost
everything from Debian repos.

$ inxi -F
System:
  Host: ryzen Kernel: 5.15.0-3-amd64 x86_64 bits: 64
Desktop: KDE Plasma 5.23.5 Distro: Debian GNU/Linux bookworm/sid

dmesg says:
[399243.523138] nfs: server 192.168.1.zz not responding, still trying

Why is Linux still trying to keep connection to NFS open, preventing
sleep? Why is dolphin hanging hard in this situation, throwing critical
timeout errors in dmesg? How to fix it?

This is my fstab line (some fields replaced with x y z)
192.168.1.zz:/home/xxx/Share   /home/yyy/Share
   nfs4noatime,user,noauto,x-systemd.mount-timeout-30,_netdev 0 2

Any help appreciated!

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄
[399064.214375] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[399064.215781] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[399064.349670] r8169 :06:00.0 ethernet: Link is Down
[399064.641462] PM: suspend entry (deep)
[399065.451014] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[399065.45] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[399065.452337] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[399235.335288] INFO: task dolphin:1775617 blocked for more than 120 seconds.
[399235.335293]   Not tainted 5.15.0-3-amd64 #1 Debian 5.15.15-2
[399235.335295] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[399235.335296] task:dolphin state:D stack:0 pid:1775617 ppid:  
3567 flags:0x4000
[399235.335299] Call Trace:
[399235.335300]  
[399235.335302]  __schedule+0x2f3/0x940
[399235.335307]  schedule+0x44/0xa0
[399235.335308]  io_schedule+0x42/0x70
[399235.335309]  wait_on_page_bit_common+0x100/0x390
[399235.335312]  ? dio_warn_stale_pagecache.part.0+0x50/0x50
[399235.335314]  wait_on_page_writeback+0x22/0x70
[399235.335315]  __filemap_fdatawait_range+0x81/0xf0
[399235.335317]  ? mls_compute_context_len+0x1f/0x200
[399235.335319]  filemap_write_and_wait_range+0x85/0xf0
[399235.335323]  nfs_getattr+0x3d3/0x3f0 [nfs]
[399235.335336]  vfs_statx+0xa0/0x130
[399235.335338]  do_statx+0x40/0x80
[399235.335340]  __x64_sys_statx+0x1b/0x20
[399235.335342]  do_syscall_64+0x3b/0xc0
[399235.335343]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[399235.335346] RIP: 0033:0x7fd2f7b0850a
[399235.335347] RSP: 002b:7ffe6d6977e8 EFLAGS: 0202 ORIG_RAX: 
014c
[399235.335349] RAX: ffda RBX: 556fbea8edd0 RCX: 
7fd2f7b0850a
[399235.335350] RDX:  RSI: 556fbf2e7e68 RDI: 
ff9c
[399235.335351] RBP:  R08: 7ffe6d697840 R09: 

[399235.335351] R10: 0fff R11: 0202 R12: 
556fbea8edb8
[399235.335352] R13: 72a67077 R14: 7ffe6d697820 R15: 
7ffe6d697818
[399235.335354]  
[399235.335391] INFO: task dolphin:1877801 blocked for more than 120 seconds.
[399235.335392]   Not tainted 5.15.0-3-amd64 #1 Debian 5.15.15-2
[399235.335393] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[399235.335394] task:dolphin state:D stack:0 pid:1877801 ppid:  
3567 flags:0x4000
[399235.335395] Call Trace:
[399235.335396]  
[399235.335397]  __schedule+0x2f3/0x940
[399235.335398]  schedule+0x44/0xa0
[399235.335399]  

Re: Future of "his" packages in Debian

[piorunz]

On 21/01/2022 06:47, Aurélien COUDERC wrote:



Le 20 janvier 2022 23:09:30 GMT+01:00, piorunz  a écrit :

On 20/01/2022 18:17, Marco Valli wrote:

by Norbert Preining · 2022/01/14


Admittedly, this guy doesn't have much faith in the the Debian/Kde team. 
Regards


Who is this clown again? 


The Debian KDE team is a (small) handful of people maintaining both the Qt 
stack and the ~500 frameworks/plasma/apps packages on their free time.

Lately Norbert was doing most of the later.

More contributors are really welcome ! If you've always wanted to become a 
Debian contributor and are interested in the KDE stack, now is a perfect time.

Join us on IRC, the handful is a friendly bunch of people.


Best,
--
Aurélien



I didn't wanted to angry anyone. Apologies. But he kinda asked for it:

"I guess that  with me not taking action, frameworks, gears, and plasma
will fall back over time "

Really?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: Future of "his" packages in Debian

[piorunz]

On 20/01/2022 18:17, Marco Valli wrote:

by Norbert Preining · 2022/01/14



After having been (again) demoted (blah)
based on flimsy arguments, I have been forced to rethink the level
of contribution I want to do for Debian. Blah blah blah blah
After about 20 years in Debian, blah blah blah
blah
KDE/Plasma, frameworks, Gears, and related packages:
blah
All these packages are group maintained, so there is not much to
worry about.
Furthermore, a few new faces have joined the team and
are actively working on the packages, although mostly on Qt6. I guess
that  with me not taking action, frameworks, gears, and plasma
will fall back over time


Admittedly, this guy doesn't have much faith in the the Debian/Kde team. 
Regards


Who is this clown again? 

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

KDE: Default to HDMI sound output when available

[piorunz]

Hi all,

Every day I connect TV with speakers to my laptop via HDMI cable. When
connected, it doesn't change to new output. I have to manually change to
HDMI audio. When disconnected, sound output default to laptop speakers.

Audio Volume Settings panel, on Advanced tab, has "Automatically switch
all running streams when a new output becomes available" but this
doesn't work, when I plug in HDMI, nothing changes, my default audio
sink stays the same (laptop speakers).

How to change audio settings, so it does one new thing as below:
* when HDMI Audio output is available, switch to it

Nothing else is needed really.
I use Debian 11.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Broken KDE in Sid/Unstable

[piorunz]

On 20/09/2021 12:19, Norbert Preining wrote:

Hi,


The main drawback I see every time KDE gets updated is that everything
changes. Few weeks ago the main menu changed to a ugly one with too
big icons... and no way to get back the old one. Today the taskbar


I somehow disagree. Since I started packaging KDE/plasma with 5.18 or
so, I have been tracking every single minor and major release within a
few days, and I never have seen any considerable change in
layout/design.

So I am really surprised about your experience.


So you are maintainer and you package KDE for Debian, I understand
correctly? If, yes thanks for your work :)

Unfortunately, OP author got this because he clicks YES when apt
full-upgrade wants to many delete packages due to unmet dependencies.
That ends up with more or less broken system, and in this example,
broken KDE.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Broken KDE in Sid/Unstable

[piorunz]

On 19/09/2021 17:16, Miguel A. Vallejo wrote:

The main drawback I see every time KDE gets updated is that everything
changes. Few weeks ago the main menu changed to a ugly one with too
big icons... and no way to get back the old one. Today the taskbar
reappeared with an "only icons" version. Once I changed the widget to
the traditional one I just have too much text in taskbar items...

KDE is a constant fight between the user keeping things like he wants
and the developers changing everything to a worse / uglier version.


Problems you are describing are happening because you using are Sid.
This is not KDE's fault. Packages in Sid are landing when they are
ready, without checking for dependences, that's how Sid is designed to
be. You are doing full upgrades, which are breaking your system. This is
very often accuring after new stable release, which happened last month.
You don't know how to use Sid properly - you should be using Testing,
not Sid. Next time Sid can pull out half of your system, not just some
KDE packages, because you are full-upgrading without reading.

If you want to stay with Sid, I recommend at least start using backups
and do safe upgrades, not full upgrades, and *read*.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄