[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2022-06-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402848

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.25
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #8 from Nate Graham  ---
A variety of Flatpak crashes should be fixed in 5.25.

If you're still experiencing any, please file a new bug report. Thanks!

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2022-06-01 Thread Madalee
https://bugs.kde.org/show_bug.cgi?id=402848

Madalee  changed:

   What|Removed |Added

 CC||mat...@ohlmeyers.com

--- Comment #7 from Madalee  ---
Created attachment 149382
  --> https://bugs.kde.org/attachment.cgi?id=149382&action=edit
This is how I know its time to open the console and run 'sudo flatpak update'

This has been a very consistent crash across so many versions.

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2022-05-23 Thread Gregory Allen
https://bugs.kde.org/show_bug.cgi?id=402848

Gregory Allen  changed:

   What|Removed |Added

   Platform|Fedora RPMs |Kubuntu Packages
 CC||grego...@mail.com

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2021-11-25 Thread Thomas Pfeiffer
https://bugs.kde.org/show_bug.cgi?id=402848

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #6 from Thomas Pfeiffer  ---
I'm having a similar crash, every time I start Discover if there are any
updates available.

Plasma 5.23.3
KDE Frameworks: 5.88.0
Qt: 5.15.3
Kernel: 5.11.0

I could not produce a useful backtrace because the automatic debug package
installer could not find a debug package for the flatpak-backend.so (with the
below output)

[] RESOLVED
"plasma-discover-backend-flatpak;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
"plasma-discover-dbgsym;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
1
[] FileResolver(0x55d8fe712f40) ++ packages for
"plasma-discover-backend-flatpak;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
"plasma-discover-dbgsym;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
[] RESOLVED
"plasma-discover;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
"plasma-discover-dbgsym;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
2
[] FileResolver(0x55d8fe6adec0) ++ packages for
"plasma-discover;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
"plasma-discover-dbgsym;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
[] candidates ("plasma-discover-backend-flatpak-dbgsym",
"plasma-discover-backend-flatpak-dbg", "plasma-discover-dbg",
"plasma-discover-dbgsym")
[] FileResolver(0x55d8fe712f40) found
"plasma-discover-backend-flatpak;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
[] candidates ("plasma-discover-dbgsym", "plasma-discover-dbg",
"plasma-discover-dbg", "plasma-discover-dbgsym")
[] FileResolver(0x55d8fe6adec0) found
"plasma-discover;5.23.3.1-0xneon+20.04+focal+release+build47;amd64;installed:user_focal-focal-main"
[] ("neon-repositories-ubuntu-ddebs")
[] "[repository::system/package/os/org.kde.neon.com.ubuntu.ddebs/*]> name:
Ubuntu Debug Symbols | summary: Debug Symbols for Ubuntu | package:
neon-repositories-ubuntu-ddebs"
[] ("org.kde.neon.com.ubuntu.ddebs") 1
[] files: ("/usr/bin/plasma-discover",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so")

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2020-11-22 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=402848

Justin Zobel  changed:

   What|Removed |Added

   Severity|normal  |crash
 CC||justin.zo...@gmail.com

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-15 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402848

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-05 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

Matt Fagnani  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com
  Component|discover|Flatpak Backend

--- Comment #5 from Matt Fagnani  ---
I ran gdb plasma-discover. The segmentation fault was shown as

Thread 79 "QNetworkAccessM" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x9c9ffb40 (LWP 2647)]
0xb5c9c23b in QHttpNetworkConnectionChannel::sendRequest (this=0x9ce0b114)
at access/qhttpnetworkconnectionchannel.cpp:251
251 return protocolHandler->sendRequest();

protocolHandler and its component object had null pointers as follows.

(gdb) p protocolHandler
$1 = {d = 0x0}
(gdb) p protocolHandler.d
$2 = (QAbstractProtocolHandler *) 0x0

protocolHandler->sendRequest() seemed to be a null pointer dereference
resulting in the segmentation fault at qhttpnetworkconnectionchannel.cpp:251

I saw two other segmentation faults in gdb which occurred after the one above
involving gpgme, flatpak, and ostree on two different runs.

Thread 13 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa2969b40 (LWP 3076)]
0xa336255f in _gpgme_debug_buffer () from /lib/libgpgme.so.11
(gdb) bt
#0  0xa336255f in _gpgme_debug_buffer () at /lib/libgpgme.so.11
#1  0xa335f7dc in _gpgme_io_read () at /lib/libgpgme.so.11
#2  0xa336586e in _gpgme_get_program_version () at /lib/libgpgme.so.11
#3  0xa3350184 in gpg_get_version () at /lib/libgpgme.so.11
#4  0xa334df9d in _gpgme_set_engine_info () at /lib/libgpgme.so.11
#5  0xa3364b4e in gpgme_ctx_set_engine_info () at /lib/libgpgme.so.11
#6  0xa3215493 in  () at /lib/libostree-1.so.1
#7  0xa3201f53 in  () at /lib/libostree-1.so.1
#8  0xa31a5c46 in  () at /lib/libostree-1.so.1
#9  0xa31ae378 in  () at /lib/libostree-1.so.1
#10 0xa31aec3a in ostree_repo_verify_summary () at /lib/libostree-1.so.1
#11 0xa31d09c1 in ostree_repo_remote_fetch_summary_with_options ()
at /lib/libostree-1.so.1
#12 0xa31a88f2 in ostree_repo_remote_fetch_summary () at /lib/libostree-1.so.1
#13 0xa33f5ae1 in  () at /lib/libflatpak.so.0
#14 0xa33f62e4 in  () at /lib/libflatpak.so.0
#15 0xa343b4ea in flatpak_installation_list_remote_refs_sync ()
at /lib/libflatpak.so.0
#16 0xa343b7ae in flatpak_installation_list_installed_refs_for_update ()
at /lib/libflatpak.so.0
#17 0xa34ac059 in  () at /usr/lib/qt5/plugins/discover/flatpak-backend.so
#18 0xb5704af0 in QThreadPoolThread::run() (this=)
at thread/qthreadpool.cpp:101
#19 0xb570d7e9 in QThreadPrivate::start(void*) (arg=)
at thread/qthread_unix.cpp:367
#20 0xb4f035de in start_thread (arg=) at pthread_create.c:486
#21 0xb531997a in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
(gdb) bt
#0  0xa336255f in _gpgme_debug_buffer () at /lib/libgpgme.so.11
#1  0xa335f7dc in _gpgme_io_read () at /lib/libgpgme.so.11
#2  0xa336586e in _gpgme_get_program_version () at /lib/libgpgme.so.11
#3  0xa3350184 in gpg_get_version () at /lib/libgpgme.so.11
#4  0xa334df9d in _gpgme_set_engine_info () at /lib/libgpgme.so.11
#5  0xa3364b4e in gpgme_ctx_set_engine_info () at /lib/libgpgme.so.11
#6  0xa3215493 in  () at /lib/libostree-1.so.1
#7  0xa3201f53 in  () at /lib/libostree-1.so.1
#8  0xa31a5c46 in  () at /lib/libostree-1.so.1
#9  0xa31ae378 in  () at /lib/libostree-1.so.1
#10 0xa31aec3a in ostree_repo_verify_summary () at /lib/libostree-1.so.1
#11 0xa31d09c1 in ostree_repo_remote_fetch_summary_with_options ()
at /lib/libostree-1.so.1
#12 0xa31a88f2 in ostree_repo_remote_fetch_summary () at /lib/libostree-1.so.1
#13 0xa33f5ae1 in  () at /lib/libflatpak.so.0
#14 0xa33f62e4 in  () at /lib/libflatpak.so.0
#15 0xa343b4ea in flatpak_installation_list_remote_refs_sync ()
at /lib/libflatpak.so.0
#16 0xa343b7ae in flatpak_installation_list_installed_refs_for_update ()
at /lib/libflatpak.so.0
#17 0xa34ac059 in  () at /usr/lib/qt5/plugins/discover/flatpak-backend.so
#18 0xb5704af0 in QThreadPoolThread::run() (this=)
at thread/qthreadpool.cpp:101
#19 0xb570d7e9 in QThreadPrivate::start(void*) (arg=)
at thread/qthread_unix.cpp:367
#20 0xb4f035de in start_thread (arg=) at pthread_create.c:486
--Type  for more, q to quit, c to continue without paging--
#21 0xb531997a in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 13 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa296ab40 (LWP 5956)]
0xa335e55f in _gpgme_debug_buffer (lvl=7, fmt=0xa3365b11 "%s: check: %s", 
func=0xa3367b97 "_gpgme_io_read", buffer=0xa2969afc "", len=4294967295)
at debug.c:393
393   val = buffer[idx++];


I noticed discover output various errors for firefox, kde, gnome flatpak
remotes I had added months ago using the flatpak cli. I removed the firefox,
kde, gnome flatpak remotes in groups one at a time using flatpak remo

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-04 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

--- Comment #4 from Matt Fagnani  ---
Created attachment 117280
  --> https://bugs.kde.org/attachment.cgi?id=117280&action=edit
error messages in konsole when valgrind was run on discover

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-04 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

--- Comment #3 from Matt Fagnani  ---
Created attachment 117279
  --> https://bugs.kde.org/attachment.cgi?id=117279&action=edit
valgrind output when run on discover

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-04 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

--- Comment #2 from Matt Fagnani  ---
I ran valgrind --leak-check=no --log-file=valgrind-discover-5.14.5-1.txt
plasma-discover & The valgrind output following the crash showed an invalid
read of size 4 in QHttpNetworkConnectionChannel::sendRequest() at
qhttpnetworkconnectionchannel.cpp:251 like in the trace of the crashing thread.
The line "Address 0x0 is not stack'd, malloc'd or (recently) free'd" likely
means a null pointer is involved and might be dereferenced leading to the
segmentation fault.

==5133== Thread 9 QNetworkAccessMa:
==5133== Invalid read of size 4
==5133==at 0x6AA623B: QHttpNetworkConnectionChannel::sendRequest()
(qhttpnetworkconnectionchannel.cpp:251)
==5133==by 0x6AA4A5A: QHttpNetworkConnectionPrivate::_q_startNextRequest()
(qhttpnetworkconnection.cpp:1044)
==5133==by 0x6F18FC5: placeMetaCall (qobject.cpp:506)
==5133==by 0x6F18FC5: QMetaCallEvent::placeMetaCall(QObject*)
(qobject.cpp:501)
==5133==by 0x6F1C4B2: QObject::event(QEvent*) (qobject.cpp:1251)
==5133==by 0x59ADD89: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(qapplication.cpp:3726)
==5133==by 0x59B5E38: QApplication::notify(QObject*, QEvent*)
(qapplication.cpp:3485)
==5133==by 0x6EF0BB5: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1047)
==5133==by 0x6EF4067: sendEvent (qcoreapplication.h:234)
==5133==by 0x6EF4067: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1744)
==5133==by 0x6EF447A: QCoreApplication::sendPostedEvents(QObject*, int)
(qcoreapplication.cpp:1598)
==5133==by 0x6F48166: postEventSourceDispatch(_GSource*, int (*)(void*),
void*) (qeventdispatcher_glib.cpp:276)
==5133==by 0x9FED3F4: g_main_dispatch (gmain.c:3182)
==5133==by 0x9FED3F4: g_main_context_dispatch (gmain.c:3847)
==5133==by 0x9FED7D8: g_main_context_iterate.isra.20 (gmain.c:3920)
==5133==  Address 0x0 is not stack'd, malloc'd or (recently) free'd


Two invalid reads of size 2 in socketNotifierSourceCheck at
qeventdispatcher_glib.cpp:88 and socketNotifierSourceCheck at
qeventdispatcher_glib.cpp:79 appear to be use-after-free errors since they have
lines like "Address 0xcbdff66 is 6 bytes inside a block of size 12 free'd"
Invalid data from those errors might lead to the crash.

==5133== Thread 3 QDBusConnectionM:
==5133== Invalid read of size 2
==5133==at 0x6F47CCC: socketNotifierSourceCheck(_GSource*)
(qeventdispatcher_glib.cpp:88)
==5133==by 0x9FED0F1: g_main_context_check (gmain.c:3753)
==5133==by 0x9FED6E4: g_main_context_iterate.isra.20 (gmain.c:3917)
==5133==by 0x9FED88A: g_main_context_iteration (gmain.c:3981)
==5133==by 0x6F47E2C:
QEventDispatcherGlib::processEvents(QFlags)
(qeventdispatcher_glib.cpp:422)
==5133==by 0x6EEF8BE:
QEventLoop::exec(QFlags) (qeventloop.cpp:214)
==5133==by 0x6D58CB0: QThread::exec() (qthread.cpp:525)
==5133==by 0x580C0CF: QDBusConnectionManager::run()
(qdbusconnection.cpp:178)
==5133==by 0x6D637E8: QThreadPrivate::start(void*) (qthread_unix.cpp:367)
==5133==by 0x78FD5DD: start_thread (pthread_create.c:486)
==5133==by 0x7527979: clone (clone.S:108)
==5133==  Address 0xcbdff66 is 6 bytes inside a block of size 12 free'd
==5133==at 0x4836D85: operator delete(void*, unsigned int)
(vg_replace_malloc.c:591)
==5133==by 0x6F485DF:
QEventDispatcherGlib::unregisterSocketNotifier(QSocketNotifier*)
(qeventdispatcher_glib.cpp:503)
==5133==by 0x6F27AF1: QSocketNotifier::setEnabled(bool)
(qsocketnotifier.cpp:246)
==5133==by 0x6F47CC4: socketNotifierSourceCheck(_GSource*)
(qeventdispatcher_glib.cpp:88)
==5133==by 0x9FED0F1: g_main_context_check (gmain.c:3753)
==5133==by 0x9FED6E4: g_main_context_iterate.isra.20 (gmain.c:3917)
==5133==by 0x9FED88A: g_main_context_iteration (gmain.c:3981)
==5133==by 0x6F47E2C:
QEventDispatcherGlib::processEvents(QFlags)
(qeventdispatcher_glib.cpp:422)
==5133==by 0x6EEF8BE:
QEventLoop::exec(QFlags) (qeventloop.cpp:214)
==5133==by 0x6D58CB0: QThread::exec() (qthread.cpp:525)
==5133==by 0x580C0CF: QDBusConnectionManager::run()
(qdbusconnection.cpp:178)
==5133==by 0x6D637E8: QThreadPrivate::start(void*) (qthread_unix.cpp:367)
==5133==  Block was alloc'd at
==5133==at 0x4835C89: operator new(unsigned int) (vg_replace_malloc.c:338)
==5133==by 0x6F484AC:
QEventDispatcherGlib::registerSocketNotifier(QSocketNotifier*)
(qeventdispatcher_glib.cpp:459)
==5133==by 0x6F279E5: QSocketNotifier::QSocketNotifier(int,
QSocketNotifier::Type, QObject*) (qsocketnotifier.cpp:155)
==5133==by 0x58174F8: qDBusAddWatch (qdbusintegrator.cpp:213)
==5133==by 0x7B41688: _dbus_watch_list_set_functions (in
/usr/lib/libdbus-1.so.3.19.8)
==5133==by 0x7B25219: dbus_connection_set_watch_functions (in
/usr/lib/libdbus-1.so.3.19.8)
==5133==by 0x581A00A: q_dbus_connection_set_watch_functions
(qdbus_symbols_p.h:229)
==5133==by 0x581A00A:

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-04 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

Matt Fagnani  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared

2019-01-04 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=402848

--- Comment #1 from Matt Fagnani  ---
Created attachment 117277
  --> https://bugs.kde.org/attachment.cgi?id=117277&action=edit
full trace of all threads for discover crash

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