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

2023-03-11 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 libpackagekitqt5-1 1.1.0-1
Bug #1028208 [plasma-discover] plasma-discover: Program terminated with signal 
SIGSEGV
Bug reassigned from package 'plasma-discover' to 'libpackagekitqt5-1'.
No longer marked as found in versions plasma-discover/5.26.4-1.
Ignoring request to alter fixed versions of bug #1028208 to the same values 
previously set
Bug #1028208 [libpackagekitqt5-1] plasma-discover: Program terminated with 
signal SIGSEGV
Marked as found in versions packagekit-qt/1.1.0-1.

-- 
1028208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

2023-03-11 Thread Aurélien COUDERC 
control: reassign -1 libpackagekitqt5-1 1.1.0-1

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

2023-01-23 Thread Bernhard Übelacker 

Am 23.01.23 um 23:07 schrieb piorunz:

On 23/01/2023 21:59, Bernhard Übelacker wrote:


Hello Piotr,
if it is not clear it would be possible to take
the bug number from the email addresses and open
the bug page e.g. https://bugs.debian.org/1028208.
This was just about the plasma-discover crash part.

However, you can also iterate through past logs by
showing the different boots like this:

$ journalctl --user --list-boots
IDX BOOT ID  FIRST ENTRY LAST 
ENTRY

...
-14  Thu 2022-12-29 16:49:33 CET Mon 
2023-01-09 12:05:55 CET

...


And then show the logging for your user at that boot and
scroll to the wanted time frame:

$ journalctl --user -b -14


Kind regards,
Bernhard



Thank you Bernhard,

I've extracted logs from that time, please see attached.




Hello Piotr,
ok, then I got distracted by this from coredumpctl, showing "GMT",
while it might be really localtime ... at least it is the same as in journalctl 
...
 Timestamp: Sun 2023-01-08 13:36:08 GMT (1h 29min ago)


Your log shows four times a crashing kded5 before, then the plasma-discover:
  Jan 08 13:35:03 ryzen systemd-coredump[2835427]: Process 1997855 (kded5) of 
user 1000 dumped core.
  Jan 08 13:35:04 ryzen systemd-coredump[2835810]: Process 2835418 (kded5) of 
user 1000 dumped core.
  Jan 08 13:35:06 ryzen systemd-coredump[2836051]: Process 2835806 (kded5) of 
user 1000 dumped core.
  Jan 08 13:35:08 ryzen systemd-coredump[2836163]: Process 2836048 (kded5) of 
user 1000 dumped core.
  Jan 08 13:36:09 ryzen systemd-coredump[2842084]: Process 2832872 
(plasma-discover) of user 1000 dumped core.


And before the plasma-discover PID 2832872 shows:
  Jan 08 13:35:00 ryzen plasmashell[2832872]: adding empty sources model 
QStandardItemModel(0x55cb965ccf70)
  Jan 08 13:35:00 ryzen plasmashell[2832872]: 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/TextFieldContextMenu.qml:159:5:
 QML MenuItem: Binding loop detected for property "implicitWidth"
  Jan 08 13:35:00 ryzen plasmashell[2832872]: 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:76:5:
 QML Binding: Binding loop detected for property "value"
  Jan 08 13:35:00 ryzen plasmashell[2832872]: packagekitqt.transaction: Unknown Transaction 
property: "Sender" QVariant(QString, ":1.577")
  Jan 08 13:35:01 ryzen plasmashell[2832872]: packagekitqt.transaction: Unknown Transaction 
property: "Sender" QVariant(QString, ":1.577")
  Jan 08 13:35:01 ryzen plasmashell[2832872]: packagekitqt.transaction: Unknown Transaction 
property: "Sender" QVariant(QString, ":1.577")
  Jan 08 13:35:03 ryzen plasmashell[2832872]: took really long to fetch 
PackageKitBackend(0x55cb964b2e50)
  Jan 08 13:35:03 ryzen plasmashell[2832872]: 29 -- exe=/usr/bin/plasma-discover
  Jan 08 13:35:03 ryzen plasmashell[2832872]: KCrash: crashing... 
crashRecursionCounter = 2


So I assume this plasma-discover crash is a result
of the crash of kded5 with PID 1997855 in the same second before:
 #2  
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x586d)
 #3  n/a (libc.so.6 + 0x3bf90)
 #4  
_ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x1aba4)
 #5  n/a (kded_apperd.so + 
0xeaae)
 #6  n/a (kded_apperd.so + 
0xeb99)
 #7  n/a (libQt5Core.so.5 + 
0x2e8fcf)
 #8  
_ZN10PackageKit6Daemon22transactionListChangedERK11QStringList 
(libpackagekitqt5.so.1 + 0xe095)

Which looks like that from Debian bug #1026062.


The 60 seconds between the crashes might be the timeout
of KCrash to give the user the chance to click the icon
in the systray, after that time it "forwards" the crash
to get collected by systemd-coredump.


So in the end it looks like plasma-discover is not prepared
for kded5 crashing, not ideal, but if kded5 gets fixed this
plasma-discover crash might disappear too.

Kind regards,
Bernhard

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

2023-01-23 Thread Bernhard Übelacker 

Am 23.01.23 um 22:48 schrieb 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.




Hello Piotr,
if it is not clear it would be possible to take
the bug number from the email addresses and open
the bug page e.g. https://bugs.debian.org/1028208.
This was just about the plasma-discover crash part.

However, you can also iterate through past logs by
showing the different boots like this:

$ journalctl --user --list-boots
IDX BOOT ID  FIRST ENTRY LAST ENTRY
...
-14  Thu 2022-12-29 16:49:33 CET Mon 2023-01-09 
12:05:55 CET
...


And then show the logging for your user at that boot and
scroll to the wanted time frame:

$ journalctl --user -b -14


Kind regards,
Bernhard

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

2023-01-23 Thread 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/
⠈⠳⣄

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

2023-01-23 Thread Bernhard Übelacker 

(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

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

2023-01-08 Thread 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