Bug 375052 - discover crashes upon start
Summary: discover crashes upon start
Status: RESOLVED DUPLICATE of bug 345563
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.7.5
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: drkonqi
: 375284 376782 377872 377986 377996 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-01-14 18:05 UTC by mike marotta
Modified: 2017-03-24 21:05 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-15761-0.html (807 bytes, text/html)
2017-01-19 21:49 UTC, mike marotta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mike marotta 2017-01-14 18:05:57 UTC
Application: plasma-discover (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-22-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
- Unusual behavior I noticed:  screen flickers on and off like a strobe.   149 updates not installing

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8caab7e00 (LWP 16789))]

Thread 5 (Thread 0x7ff8a7ce6700 (LWP 16793)):
#0  0x00007ff8c73390bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff8c45ba9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff8c45baaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff8c7f704ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007ff8c7f180fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ff8c7d3dd43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007ff8c7d42c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ff8c4add6ca in start_thread (arg=0x7ff8a7ce6700) at pthread_create.c:333
#8  0x00007ff8c73450af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7ff8adbd1700 (LWP 16792)):
#0  0x00007ff8caaa4dc3 in __GI___tls_get_addr (ti=0x7ff8c8167798) at dl-tls.c:831
#1  0x00007ff8c7d41b06 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007ff8c7f6fc91 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007ff8c45ba3c9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ff8c45ba974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ff8c45baaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ff8c7f704ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ff8c7f180fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ff8c7d3dd43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ff8c9f02c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x00007ff8c7d42c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ff8c4add6ca in start_thread (arg=0x7ff8adbd1700) at pthread_create.c:333
#12 0x00007ff8c73450af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7ff8aede2700 (LWP 16791)):
#0  0x00007ff8c73390bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff8c45ba9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff8c45baaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff8c7f704ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007ff8c7f180fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ff8c7d3dd43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007ff8c5375575 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007ff8c7d42c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ff8c4add6ca in start_thread (arg=0x7ff8aede2700) at pthread_create.c:333
#9  0x00007ff8c73450af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7ff8b7749700 (LWP 16790)):
#0  0x00007ff8c73390bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff8c2688c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007ff8c268a8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007ff8ba2d3299 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007ff8c7d42c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ff8c4add6ca in start_thread (arg=0x7ff8b7749700) at pthread_create.c:333
#6  0x00007ff8c73450af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7ff8caab7e00 (LWP 16789)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x00007ff8c72743ea in __GI_abort () at abort.c:89
#8  0x00007ff8c7d29cc1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ff8ca3f9a13 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007ff8ca401b82 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007ff8ca401f63 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007ff8c850bf65 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007ff8ca435a13 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x00007ff8c8ae88ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ff8c8aedd4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007ff8c7f1a3b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ff8c850129d in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007ff8c8501e7d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007ff8c84dfb2b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x00007ff8ba309660 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007ff8c45ba7d7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007ff8c45baa40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ff8c45baaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007ff8c7f7048f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007ff8c7f180fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007ff8c7f2090c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00005639c7d87699 in ?? ()
#28 0x00007ff8c725d3f1 in __libc_start_main (main=0x5639c7d86f90, argc=3, argv=0x7ffd5257eb38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd5257eb28) at ../csu/libc-start.c:291
#29 0x00005639c7d877ba in _start ()

Possible duplicates by query: bug 364721, bug 364342, bug 362635, bug 362228.

Reported using DrKonqi
Comment 1 Aleix Pol 2017-01-17 14:42:24 UTC
I've seen this issue on Neon. It's a crash in Qt, I cannot get a proper backtrace with debug symbols though. It would be helpful to come up with a fix or a test case at least.

Clearly the same issue as #364342.
Comment 2 Christoph Feck 2017-01-19 20:01:24 UTC
*** Bug 375284 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2017-01-19 20:08:46 UTC
This is bug 345563, probably caused by a broken nvidia driver setup.
Comment 4 mike marotta 2017-01-19 21:49:07 UTC
Created attachment 103545 [details]
attachment-15761-0.html

Am new to Linux.  How do I fix the driver?

On Jan 19, 2017 14:08, "Christoph Feck" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=375052
>
> --- Comment #3 from Christoph Feck <cfeck@kde.org> ---
> This is bug 345563, probably caused by a broken nvidia driver setup.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 Aleix Pol 2017-01-21 23:01:04 UTC

*** This bug has been marked as a duplicate of bug 375083 ***
Comment 6 Marco Martin 2017-02-22 17:17:18 UTC
*** Bug 376782 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2017-03-21 13:24:56 UTC

*** This bug has been marked as a duplicate of bug 345563 ***
Comment 8 Christoph Feck 2017-03-21 13:26:44 UTC
*** Bug 377872 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Feck 2017-03-24 21:05:25 UTC
*** Bug 377986 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Feck 2017-03-24 21:05:48 UTC
*** Bug 377996 has been marked as a duplicate of this bug. ***