[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 Tim Steinberger changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #45 from Tim Steinberger --- Sorry about that, I've done more experimenting with it and my crash is happening for a different reason. Packagekit was crashing because it depended on a binary I did not have installed. This is a problem on the package maintainer's end, so the only issue I see with discover here is that it crashes when packagekit exits rather than continuing and just printing an error which is a different issue in itself. I set this back to Fixed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #44 from Tim Steinberger --- Actually, I apologize, this might be a different bug. I was able to build flatpak without systemd support and install it. I found it crashes with both installed (though takes longer than if just packagekit-qt5 is installed). Bug number is 396069. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496
--- Comment #42 from Tim Steinberger ---
I found this bug after googling what seemed to be the error message most likely
to cause the crash. As this gave the exact same behavior I assumed this was
what was causing it. Here is the log from the command line if I start discover
from there, maybe I missed something obvious.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
QQmlComponent: Created graphical object was not placed in the graphics scene.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
error loading "flatpak-backend" "Cannot load library
/usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open
shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":330497})
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x564cc1ec2850)
could not find "org.kde.krita.desktop" "krita.desktop"
could not find "org.kde.krita.desktop" "krita.desktop"
Error when fetching the last update time
QDBusError("org.freedesktop.DBus.Error.Spawn.ChildExited", "Launch helper
exited with unknown return code 127")
Transaction error: PackageKit::Transaction::Error(ErrorInternalError) "Launch
helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1ea51d0)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f8c040)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f8c040)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f81d80)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f81d80)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f87ba0)
qml: message: Launch helper exited with unknown return code 127
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 2889
KCrash: Arguments: /usr/bin/plasma-discover
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Write', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Write', disabling...
QSocketNotifier: Invalid socket 32 and type 'Write', disabling...
QSocketNotifier: Invalid socket 26 and type 'Write', disabling...
QSocketNotifier: Invalid socket 28 and type 'Write', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496
--- Comment #43 from Tim Steinberger ---
I found this bug after googling what seemed to be the error message most likely
to cause the crash. As this gave the exact same behavior I assumed this was
what was causing it. Here is the log from the command line if I start discover
from there, maybe I missed something obvious.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
QQmlComponent: Created graphical object was not placed in the graphics scene.
Icon theme "ubuntu-mono-dark" not found.
Icon theme "Mint-X" not found.
Icon theme "elementary" not found.
Icon theme "gnome" not found.
error loading "flatpak-backend" "Cannot load library
/usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open
shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":330497})
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x564cc1ec2850)
could not find "org.kde.krita.desktop" "krita.desktop"
could not find "org.kde.krita.desktop" "krita.desktop"
Error when fetching the last update time
QDBusError("org.freedesktop.DBus.Error.Spawn.ChildExited", "Launch helper
exited with unknown return code 127")
Transaction error: PackageKit::Transaction::Error(ErrorInternalError) "Launch
helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1ea51d0)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f8c040)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f8c040)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f81d80)
qml: message: Launch helper exited with unknown return code 127
failed PackageKit::Transaction::Exit(ExitFailed)
PackageKit::Transaction(0x564cc1f81d80)
Transaction error: "Launch helper exited with unknown return code 127"
PackageKit::Transaction(0x564cc1f87ba0)
qml: message: Launch helper exited with unknown return code 127
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 2889
KCrash: Arguments: /usr/bin/plasma-discover
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Write', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Write', disabling...
QSocketNotifier: Invalid socket 32 and type 'Write', disabling...
QSocketNotifier: Invalid socket 26 and type 'Write', disabling...
QSocketNotifier: Invalid socket 28 and type 'Write', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #41 from Aleix Pol --- Tim Steinberger, how do you know this is the bug you're hitting? FWIW, I just tried here removing flatpak, it works just fine. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 tste...@protonmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||tste...@protonmail.com --- Comment #40 from tste...@protonmail.com --- Application: plasma-discover (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: This crash is still occurring for me on Obarun Linux (which is based on Arch). The version is 5.13 so it is up to date. So long as packagekit-qt5 is installed, but flatpak is not the application crashes. This is particularly problematic for me as I cannot install flatpak on here due to a dependency on systemd. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd65f72780 (LWP 1921))] Thread 11 (Thread 0x7fdd1e940700 (LWP 1940)): #0 0x7fdd614d4ea9 in poll () at /usr/lib/libc.so.6 #1 0x7fdd5bc0f523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdd5bc0f63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fdd61df0f84 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fdd61d9c87c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdd61be59c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdd61befa75 in () at /usr/lib/libQt5Core.so.5 #7 0x7fdd5dbbe075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fdd614df53f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fdd1f141700 (LWP 1931)): #0 0x7fdd614d4ea9 in poll () at /usr/lib/libc.so.6 #1 0x7fdd5bc0f523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdd5bc0f8e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7fdd30d15348 in () at /usr/lib/libgio-2.0.so.0 #4 0x7fdd5bc37a2a in () at /usr/lib/libglib-2.0.so.0 #5 0x7fdd5dbbe075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdd614df53f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fdd1f942700 (LWP 1930)): #0 0x7fdd5bc0f3ac in () at /usr/lib/libglib-2.0.so.0 #1 0x7fdd5bc0f63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7fdd5bc0f692 in () at /usr/lib/libglib-2.0.so.0 #3 0x7fdd5bc37a2a in () at /usr/lib/libglib-2.0.so.0 #4 0x7fdd5dbbe075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fdd614df53f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fdd32d49700 (LWP 1928)): #0 0x7fdd614da0f9 in syscall () at /usr/lib/libc.so.6 #1 0x7fdd61be45a5 in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #2 0x7fdd61dc7cca in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #3 0x7fdd5f39941f in () at /usr/lib/libQt5Network.so.5 #4 0x7fdd5f43b366 in () at /usr/lib/libQt5Network.so.5 #5 0x7fdd61dc7a2c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #6 0x7fdd5f38ee15 in () at /usr/lib/libQt5Network.so.5 #7 0x7fdd5f38f7ed in () at /usr/lib/libQt5Network.so.5 #8 0x7fdd61dc7a2c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x7fdd5f434d06 in () at /usr/lib/libQt5Network.so.5 #10 0x7fdd5f42fb56 in () at /usr/lib/libQt5Network.so.5 #11 0x7fdd5f430008 in () at /usr/lib/libQt5Network.so.5 #12 0x7fdd5f41a131 in () at /usr/lib/libQt5Network.so.5 #13 0x7fdd61dc7a2c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #14 0x7fdd5f3da514 in () at /usr/lib/libQt5Network.so.5 #15 0x7fdd5f3da5a0 in () at /usr/lib/libQt5Network.so.5 #16 0x7fdd5f3ed202 in () at /usr/lib/libQt5Network.so.5 #17 0x7fdd633a9a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7fdd633b1341 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fdd61d9dbe9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7fdd61df1bdb in () at /usr/lib/libQt5Core.so.5 #21 0x7fdd5bc0f368 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #22 0x7fdd5bc0f5b1 in () at /usr/lib/libglib-2.0.so.0 #23 0x7fdd5bc0f63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #24 0x7fdd61df0f84 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7fdd61d9c87c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7fdd61be59c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #27 0x7fdd61befa75 in () at /usr/lib/libQt5
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #39 from Aleix Pol --- Seems to be fixed, please reopen if it's not the case. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening when the flatpak backend is present but flatpak not installed
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added Summary|Discover crashes upon |Discover crashes upon |opening |opening when the flatpak ||backend is present but ||flatpak not installed -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Kiko Unfla changed: What|Removed |Added CC||viticl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #38 from Kiko Unfla --- Created attachment 108628 --> https://bugs.kde.org/attachment.cgi?id=108628&action=edit New crash information added by DrKonqi plasma-discover (5.10.5) using Qt 5.9.1 - What I was doing when the application crashed: trying to update de system with octopi Linux viticleri 4.4.90-1-MANJARO #1 SMP PREEMPT Thu Oct 5 14:53:38 UTC 2017 x86_64 GNU/Linux -- Backtrace (Reduced): #5 0x7fc234d91ae8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #6 0x7fc234d99a33 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #7 0x7fc23069beb4 in _dl_catch_error () at /usr/lib/libc.so.6 #8 0x7fc234d9937a in _dl_open () at /lib64/ld-linux-x86-64.so.2 #9 0x7fc22af4ae86 in () at /usr/lib/libdl.so.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 vagabonda...@gmail.com changed: What|Removed |Added CC||vagabonda...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 trevor.la...@gmail.com changed: What|Removed |Added CC||trevor.la...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #37 from trevor.la...@gmail.com --- Created attachment 107918 --> https://bugs.kde.org/attachment.cgi?id=107918&action=edit New crash information added by DrKonqi plasma-discover (5.10.5) using Qt 5.9.1 - What I was doing when the application crashed: Just trying to update my system ended up using pacman as usual - Unusual behavior I noticed: there are two volume controls (little speaker thingies) on my taskbar -- Backtrace (Reduced): #5 0x7f07b107aae8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #6 0x7f07b1082a33 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #7 0x7f07ac96eeb4 in _dl_catch_error () at /usr/lib/libc.so.6 #8 0x7f07b108237a in _dl_open () at /lib64/ld-linux-x86-64.so.2 #9 0x7f07a7218e86 in () at /usr/lib/libdl.so.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #36 from keitalbame --- Created attachment 107898 --> https://bugs.kde.org/attachment.cgi?id=107898&action=edit Pacman log from previous system update. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #35 from keitalbame --- Created attachment 107897 --> https://bugs.kde.org/attachment.cgi?id=107897&action=edit Crash report -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #34 from keitalbame --- (In reply to Antonio Rojas from comment #33) > (In reply to keitalbame from comment #32) > > Started to have this core dumps after last update, on Friday, 15th (usually > > I update once a week). > > > > I'm on Arch. > > Please confirm that it is indeed the same crash (same backtrace, and fixed > by installing flatpak). If it is, please post the pacman log of your last > update. I can confirm the issue seems the same. Attached the crash report. Did a full system update (due to the security updates available) and the issue persisted after reboot. Installed flatpak as mentioned and after that, Discover opened sucessfully, even without reboot. Also attached the previous system update log, where I detected the issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #33 from Antonio Rojas --- (In reply to keitalbame from comment #32) > Started to have this core dumps after last update, on Friday, 15th (usually > I update once a week). > > I'm on Arch. Please confirm that it is indeed the same crash (same backtrace, and fixed by installing flatpak). If it is, please post the pacman log of your last update. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #32 from keitalbame --- Started to have this core dumps after last update, on Friday, 15th (usually I update once a week). I'm on Arch. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #31 from Sebastian Cramer --- Created attachment 107809 --> https://bugs.kde.org/attachment.cgi?id=107809&action=edit New crash information added by DrKonqi plasma-discover (5.10.5) using Qt 5.9.1 Just my two cents: This seems also to be happening on a fully updated Arch Linux 64bit. -- Backtrace (Reduced): #5 0x7f9164e1948d in do_lookup_x () at /lib64/ld-linux-x86-64.so.2 #6 0x7f9164e1a03f in _dl_lookup_symbol_x () at /lib64/ld-linux-x86-64.so.2 #7 0x7f9164e1bb19 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #8 0x7f9164e23a33 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #9 0x7f916070feb4 in _dl_catch_error () at /usr/lib/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Sebastian Cramer changed: What|Removed |Added CC||scra...@jioni.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||check...@gmail.com --- Comment #30 from Antonio Rojas --- *** Bug 384318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||safa1996alful...@gmail.com --- Comment #29 from Antonio Rojas --- *** Bug 384278 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||elfimov8...@gmail.com --- Comment #28 from Antonio Rojas --- *** Bug 384263 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #27 from kts --- (In reply to Aleix Pol from comment #26) > @kts an easy way to fix it is by installing flatpak as mentioned in the > comments. We both know it's not a rational solution. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #26 from Aleix Pol --- @kts an easy way to fix it is by installing flatpak as mentioned in the comments. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #25 from kts --- I hope it get resolved soon. I have a laptop and a desktop. The problem cannot be reproduced in laptop. It can be on desktop, freshly installed Arch Linux. I got confused because laptop is good and desktop is not. I reinstalled Arch on desktop in case I made some installation mistakes. It's not. I still love KDE. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||jeckfer...@gmail.com --- Comment #24 from Aleix Pol --- *** Bug 383014 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #23 from evanshrubsole+...@gmail.com --- Created attachment 106684 --> https://bugs.kde.org/attachment.cgi?id=106684&action=edit New crash information added by DrKonqi plasma-discover (5.10.3) using Qt 5.9.1 - What I was doing when the application crashed: After installing kde it just crashes, always with the same error in that library. -- Backtrace (Reduced): #5 0x7fbbb77368e8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #6 0x7fbbb773e813 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #7 0x7fbbb302ee44 in _dl_catch_error () at /usr/lib/libc.so.6 #8 0x7fbbb773e15a in _dl_open () at /lib64/ld-linux-x86-64.so.2 #9 0x7fbbadb9bea6 in () at /usr/lib/libdl.so.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 evanshrubsole+...@gmail.com changed: What|Removed |Added CC||evanshrubsole+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #22 from Kevin Harper --- Discover does NOT continue to crash for me after installing FLATPAK ID | Command line | Date and time| Action(s) | Altered --- 36 | install flatpak-0.9.7-1. | 2017-07-14 08:45 | Install|3 35 | remove flatpack-4.0.1-4. | 2017-07-14 08:44 | Erase |1 >< Thank Aleix -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #21 from Aleix Pol --- @Kevin it's "flatpak", not "flatpack". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Kevin Harper changed: What|Removed |Added CC||kevinharp...@gmail.com --- Comment #20 from Kevin Harper --- Discover continues to crash for me even after installing flatpack [lex@localhost ~]$ sudo dnf history ID | Command line | Date and time| Action(s) | Altered --- 6 | install flatpack | 2017-07-12 15:51 | Install| 13 5 | install chromium | 2017-07-12 14:43 | Install|6 4 | install google-chrome-st | 2017-07-12 14:23 | Install| 123 EE 3 | update | 2017-07-12 13:49 | Update |1 2 | install gparted | 2017-07-12 11:01 | Install|1 < 1 | | 2017-07-05 15:00 | Install| 1655 >E This is a fresh install of Fedora 26 KDE and, as noted by 'dnf history', have only 3 packages (forced to do so via Konsole). [lex@localhost ~]$ uname -a Linux localhost.localdomain 4.11.9-300.fc26.x86_64 #1 SMP Wed Jul 5 16:21:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Software: KDE Plasma Version: 5.10.1 KDE Frameworks Version: 5.35.0 Qt Version: 5.7.1 Kernel Version: 4.11.9-300.fc26x86_64 OS Type: 64-bit Hardware: Processor: 8 x Intel Core i7-6700HQ CPU @ 2.60 GHz Memory: 15.5 GiB of RAM Please let me know if you need any more info from me. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||mustafa10...@gmail.com --- Comment #19 from Aleix Pol --- *** Bug 381188 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||xhokaxhiujul...@gmail.com --- Comment #18 from Aleix Pol --- *** Bug 382166 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Nicola Hinssen changed: What|Removed |Added CC||nicola.hins...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #17 from Nicola Hinssen --- Created attachment 106385 --> https://bugs.kde.org/attachment.cgi?id=106385&action=edit New crash information added by DrKonqi plasma-discover (5.10.3) using Qt 5.9.0 Always crashes when trying to open Discover. -- Backtrace (Reduced): #5 0x7fec4a4ae8d8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2 #6 0x7fec4a4b6783 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #7 0x7fec45d91c24 in _dl_catch_error () at /usr/lib/libc.so.6 #8 0x7fec4a4b60c9 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #9 0x7fec4069bf26 in () at /usr/lib/libdl.so.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=381188 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #16 from Stormrider --- I can confirm that installing flatpak resolves this -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||st0r...@gmail.com --- Comment #15 from Antonio Rojas --- *** Bug 381601 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||ram.premn...@gmail.com --- Comment #14 from Aleix Pol --- *** Bug 381497 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Christoph Feck changed: What|Removed |Added CC||mrbrettst...@gmail.com --- Comment #13 from Christoph Feck --- *** Bug 381059 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||guilbaud.jeremie@tutanota.c ||om --- Comment #12 from Aleix Pol --- *** Bug 380987 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||redredempt...@protonmail.co ||m --- Comment #11 from Aleix Pol --- *** Bug 381039 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||jerry.wayne.we...@gmail.com --- Comment #10 from Antonio Rojas --- *** Bug 381019 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #9 from Mayeul Cantan --- I can confirm as well, I had discover crash on me today when launching it on vanilla Arch (I usually don't since I want to see the detailed update logs, but I wanted to check it out). It crashed on launch; and Dr Konqui suggested this bug report. Installing packagekit-qt5 and packagekit seems to solve the issue. The issue doesn't remain after fatpak is installed. Here is my backtrace, just in case: Application: Découvrir (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6d7328a7c0 (LWP 6018))] Thread 67 (Thread 0x7f6cacfe1700 (LWP 6271)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 66 (Thread 0x7f6cad7e2700 (LWP 6270)): #0 0x7f6d6ea6c3b9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6d6edb9087 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*) (g=0x7f6d6da2cc08) at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/guard.cc:302 #2 0x7f6d6d78255c in () at /usr/lib/libQt5Network.so.5 #3 0x7f6d6d775ca3 in () at /usr/lib/libQt5Network.so.5 #4 0x7f6d6f15b371 in () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 65 (Thread 0x7f6cadfe3700 (LWP 6269)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 64 (Thread 0x7f6cae7e4700 (LWP 6268)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 63 (Thread 0x7f6caefe5700 (LWP 6267)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 62 (Thread 0x7f6caf7e6700 (LWP 6266)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 61 (Thread 0x7f6ca
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #8 from Antonio Rojas --- I could split the flatpak backend or make flatpak a hard dependency as a last resort, but I feel like that would be sweeping the actual issue under the rug. I would at least like to understand why this is 100% reproducible for some users but not for others (like me). There must be something (some specific setting or the presence of some package) triggering this. The only difference I can see from the linked report is that in his case the flatpak plugin is being loaded before the packagekit one. In my case it's the other way around. What determines the loading order of the plugins? Could packagekit be forced to always be loaded before flatpak? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Aleix Pol --- (In reply to Antonio Rojas from comment #4) > @Aleix I've gotten a few reports of this one, though I can't reproduce it > myself. It happens when flatpak is not installed but packagekit is, not when > both are installed or both aren't. See > https://bbs.archlinux.org/viewtopic.php?id=226752 for more details including > a BT with debug symbols This is certainly a weird bug report. So, it looks like what's happening is ld loading flatpak-backend.so which uses libappstream.so and libflatpak.so. libappstream is loaded but libflatpak isn't because it isn't there. It's libappstream when is loaded again by the flatpak backend that it explodes. I use ArchLinux but Qt5/KF5 compiled locally in debug mode and it does work for some reason. :( I have never seen anything like this and I can't think of something I can do fix it on Discover side. What other distros do is to split the flatpak-backend package and make it depend on flatpak. One thing we could do is maybe to look for flatpak (as in `which flatpak`) before actually loading it, but I'd prefer we didn't have to get to that. What do you think Antonio? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Aleix Pol changed: What|Removed |Added CC||monzo...@hotmail.com --- Comment #6 from Aleix Pol --- *** Bug 380458 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #5 from CDK --- Yep. Problem went away after installing flatpack. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #4 from Antonio Rojas --- @Aleix I've gotten a few reports of this one, though I can't reproduce it myself. It happens when flatpak is not installed but packagekit is, not when both are installed or both aren't. See https://bbs.archlinux.org/viewtopic.php?id=226752 for more details including a BT with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 --- Comment #3 from Llaurator --- (In reply to Antonio Rojas from comment #1) > does it work if you install flatpak? Yes, it works when installing flatpak, Thanks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||llaura...@gmail.com --- Comment #2 from Antonio Rojas --- *** Bug 380498 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- does it work if you install flatpak? -- You are receiving this mail because: You are watching all bug changes.
