[plasma-systemmonitor] [Bug 439503] systemmonitor crashes

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #4 from David Redondo  ---
>From the linked bug report, looks like libksysguard is out of date

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 439503] systemmonitor crashes

[Iván Ávalos]

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

Iván Ávalos  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|BACKTRACE   |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 439503] systemmonitor crashes

[Iván Ávalos]

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

Iván Ávalos  changed:

   What|Removed |Added

 CC||ava...@disroot.org

--- Comment #3 from Iván Ávalos  ---
I'm having the same problem in Parabola GNU/Linux (Arch-based) using the latest
version (5.22.3). It exits normally, immediately, but plasma-systemmonitor
never starts. Here's a GDB backtrace:

GNU gdb (GDB) 10.2
Copyright (C) 2021 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-pc-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 plasma-systemmonitor...
(No debugging symbols found in plasma-systemmonitor)
(gdb) run
Starting program: /usr/bin/plasma-systemmonitor 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x70f8b640 (LWP 164876)]
[New Thread 0x7fffebf78640 (LWP 164877)]
[Thread 0x7fffebf78640 (LWP 164877) exited]
[Thread 0x714aaa80 (LWP 164872) exited]
[Inferior 1 (process 164872) exited normally]
(gdb) bt
No stack.
(gdb) quit

Here's the related issue on Parabola's bug tracker:
https://labs.parabola.nu/issues/3057

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 439503] systemmonitor crashes

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 439503] systemmonitor crashes

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 CC||k...@david-redondo.de
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David Redondo  ---
Hi could you provide a backtrace, otherwise we are not able to know what's
going wrong 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

-- 
You are receiving this mail because:
You are watching all bug changes.