https://bugs.kde.org/show_bug.cgi?id=400386
Harald Sitter changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #20 from Patrick Silva ---
I have renamed /lib/x86_64-linux-gnu/libsnapd-glib.so.1 file, rebooted and this
file was not created again. But then Snap support in Discover stopped working.
I have reverted to original file name and Snap support
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #19 from Harald Sitter ---
I'm sure there is but I wouldn't know how exactly to set that up. auditd
technically should allow you to watch which process is writing to the path. The
tool inotifywatch might as well. Both would only help if it
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #18 from Patrick Silva ---
(In reply to Harald Sitter from comment #17)
> Perhaps something copied the file to /lib?
I don't know. Is there any way to find this out?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #17 from Harald Sitter ---
(In reply to Patrick Silva from comment #16)
> Thanks for your detailed explanation Harald.
>
> libsnapd-glib1 package owns /lib/x86_64-linux-gnu/libsnapd-glib.so.1.
>
> $ sudo apt-file search
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #16 from Patrick Silva ---
Thanks for your detailed explanation Harald.
libsnapd-glib1 package owns /lib/x86_64-linux-gnu/libsnapd-glib.so.1.
$ sudo apt-file search /lib/x86_64-linux-gnu/libsnapd-glib.so.1
libsnapd-glib1:
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #15 from Harald Sitter ---
Right. So. What's going on there is that you somehow have foreign stuff
installed in the form of /lib/x86_64-linux-gnu/libsnapd-glib.so.1 and
snapd-glib.so.1, but they aren't coming from a deb, much less from a
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #14 from Patrick Silva ---
output of "dpkg -S /lib/x86_64-linux-gnu/libsnapd-glib.so.1":
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libsnapd-glib.so.1
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #13 from Patrick Silva ---
output of your first command:
plasma-discover:
Installed: 5.21.2+p20.04+git20210308.0223-0
Candidate: 5.21.2+p20.04+git20210308.0223-0
Version table:
*** 5.21.2+p20.04+git20210308.0223-0 500
500
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #12 from Harald Sitter ---
And please also the output of `dpkg -S
/lib/x86_64-linux-gnu/libsnapd-glib.so.1`
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #11 from Harald Sitter ---
What's the output of `apt-cache policy plasma-discover plasma-discover-dbgsym`
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #10 from Patrick Silva ---
Humm, drkonqi asks for more debug packages but apparently the generated
backtrace is good.
Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #9 from Patrick Silva ---
Created attachment 136485
--> https://bugs.kde.org/attachment.cgi?id=136485=edit
degug symbols of Discover
drkonqi failed to install debug symbols of Discover again.
Operating System: KDE neon Unstable Edition
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #8 from Harald Sitter ---
Mhh. I guess I forgot to actually enable the correct debug output :S
I'll push an improvement to the installer in a bit
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #7 from Patrick Silva ---
Created attachment 134901
--> https://bugs.kde.org/attachment.cgi?id=134901=edit
screenshot
As we can see in the attached screenshot, drkonqi have just failed to install
debug packages for Discover on my neon
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #6 from Harald Sitter ---
I've revised the installer a whole lot so it should be more reliably able to
install debug symbols and make context available for when it isn't able to. Let
me know how that goes.
On a general note: the crashing
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #5 from Patrick Silva ---
Created attachment 133561
--> https://bugs.kde.org/attachment.cgi?id=133561=edit
drkonqi failed to install debug packages after System Settings crash
drkonqi have just failed to install debug packages after
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #4 from Harald Sitter ---
Since we are now using journald to capture qdebugs. Maybe there's some useful
output in
`journalctl _EXE=/usr/bin/drkonqi-pk-debug-installer`
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=400386
Patrick Silva changed:
What|Removed |Added
CC||u.a...@zoho.com
--- Comment #3 from Patrick
https://bugs.kde.org/show_bug.cgi?id=400386
--- Comment #2 from Patrick Silva ---
It happened again on neon unstable.
Kmail crashed, I clicked on "Install debug symbols" button,
drkonqi asked for my password but it was unable to install the needed debug
packages. Drkonqi was still saying "The
https://bugs.kde.org/show_bug.cgi?id=400386
Patrick Silva changed:
What|Removed |Added
Summary|Sometimes Drkonqi does not |Sometimes Drkonqi does not
21 matches
Mail list logo
