Bug 342201 - Crash on Konsole exit when using proprietary nvidia drivers
Summary: Crash on Konsole exit when using proprietary nvidia drivers
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 3.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
: 345712 346833 347129 348466 348828 349535 350924 351288 351908 353906 354028 354435 354914 356710 357473 357737 358255 358280 358326 361260 365351 371011 373350 378512 378562 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-25 00:46 UTC by Javier
Modified: 2021-01-01 04:39 UTC (History)
31 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-31932-0.html (1.94 KB, text/html)
2020-12-02 00:30 UTC, djcole187
Details
attachment-32743-0.html (5.38 KB, text/html)
2020-12-02 00:45 UTC, djcole187
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Javier 2014-12-25 00:46:06 UTC
Application: konsole (3.0.0)

Qt Version: 5.3.2
Operating System: Linux 3.16.0-28-generic x86_64
Distribution: Ubuntu Vivid Vervet (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Exited the konsole after installing a package, command secuence:
su <user>
<pass>
sudo apt-get install ....
exit
exit
<crash>

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7187b95800 (LWP 8926))]

Thread 3 (Thread 0x7f717182c700 (LWP 8927)):
[KCrash Handler]
#6  malloc_consolidate (av=av@entry=0x7f716c000020) at malloc.c:4151
#7  0x00007f71874500e8 in _int_malloc (av=av@entry=0x7f716c000020, bytes=bytes@entry=2032) at malloc.c:3423
#8  0x00007f7187452e0c in __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3219
#9  0x00007f717a30c1ae in ?? () from /usr/lib/nvidia-331-updates/tls/libnvidia-tls.so.331.113
#10 0x00007f717df4ba82 in g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f717df6318c in g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f717e67bea2 in __nptl_deallocate_tsd () at pthread_create.c:157
#13 0x00007f717e67c0b8 in start_thread (arg=0x7f717182c700) at pthread_create.c:322
#14 0x00007f71874c990d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f716a96e700 (LWP 8929)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x00007f71874546eb in _L_lock_4702 () at malloc.c:5206
#2  0x00007f718744ee7b in _int_free (av=0x7f716c000020, p=0x7f716c0012f0, have_lock=0) at malloc.c:3943
#3  0x00007f717df61ac6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f717df61c88 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f717e67bea2 in __nptl_deallocate_tsd () at pthread_create.c:157
#6  0x00007f717e67c0b8 in start_thread (arg=0x7f716a96e700) at pthread_create.c:322
#7  0x00007f71874c990d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f7187b95800 (LWP 8926)):
#0  0x00007f71874bf45d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f71808f6b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f71808f83ff in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f71808f8512 in xcb_wait_for_reply () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x00007f7180d4e69f in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x00007f7180d4a28d in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x00007f7180d2c5be in XCloseDisplay () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x00007f7173f92494 in QXcbConnection::~QXcbConnection (this=0x1939a60, __in_chrg=<optimized out>) at qxcbconnection.cpp:424
#8  0x00007f7173f928b9 in QXcbConnection::~QXcbConnection (this=0x1939a60, __in_chrg=<optimized out>) at qxcbconnection.cpp:430
#9  0x00007f7173f9764e in qDeleteAll<QList<QXcbConnection*>::const_iterator> (end=..., begin=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:323
#10 qDeleteAll<QList<QXcbConnection*> > (c=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:331
#11 QXcbIntegration::~QXcbIntegration (this=0x1919a90, __in_chrg=<optimized out>) at qxcbintegration.cpp:177
#12 0x00007f7173f97729 in QXcbIntegration::~QXcbIntegration (this=0x1919a90, __in_chrg=<optimized out>) at qxcbintegration.cpp:178
#13 0x00007f7183fd1b73 in QGuiApplicationPrivate::~QGuiApplicationPrivate (this=0x1917770, __in_chrg=<optimized out>) at kernel/qguiapplication.cpp:1364
#14 0x00007f718476b489 in QApplicationPrivate::~QApplicationPrivate (this=0x1917770, __in_chrg=<optimized out>) at kernel/qapplication.cpp:185
#15 0x00007f7183aca917 in cleanup (pointer=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#16 ~QScopedPointer (this=0x7fffc3f2aca8, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:109
#17 QObject::~QObject (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:880
#18 0x00007f718476cda6 in QApplication::~QApplication (this=0x7fffc3f2aca0, __in_chrg=<optimized out>) at kernel/qapplication.cpp:688
#19 0x00007f71877b5a09 in kdemain (argc=1, argv=0x7fffc3f2ade8) at ../../src/main.cpp:87
#20 0x00007f71873f0ec5 in __libc_start_main (main=0x400720 <main(int, char**)>, argc=1, argv=0x7fffc3f2ade8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc3f2add8) at libc-start.c:287
#21 0x000000000040074e in _start ()

Reported using DrKonqi
Comment 1 Martin Sandsmark 2016-08-13 17:25:12 UTC
*** Bug 345712 has been marked as a duplicate of this bug. ***
Comment 2 Martin Sandsmark 2016-08-13 17:25:50 UTC
*** Bug 346833 has been marked as a duplicate of this bug. ***
Comment 3 Martin Sandsmark 2016-08-13 17:26:02 UTC
*** Bug 354028 has been marked as a duplicate of this bug. ***
Comment 4 Martin Sandsmark 2016-08-13 17:27:29 UTC
*** Bug 351288 has been marked as a duplicate of this bug. ***
Comment 5 Martin Sandsmark 2016-08-13 17:28:09 UTC
*** Bug 353906 has been marked as a duplicate of this bug. ***
Comment 6 Martin Sandsmark 2016-08-13 17:30:03 UTC
*** Bug 348466 has been marked as a duplicate of this bug. ***
Comment 7 Martin Sandsmark 2016-08-13 17:31:23 UTC
*** Bug 347129 has been marked as a duplicate of this bug. ***
Comment 8 Martin Sandsmark 2016-08-13 17:31:44 UTC
*** Bug 348828 has been marked as a duplicate of this bug. ***
Comment 9 Martin Sandsmark 2016-08-13 17:32:18 UTC
*** Bug 349535 has been marked as a duplicate of this bug. ***
Comment 10 Martin Sandsmark 2016-08-13 17:32:41 UTC
*** Bug 351908 has been marked as a duplicate of this bug. ***
Comment 11 Martin Sandsmark 2016-08-13 17:33:10 UTC
*** Bug 354914 has been marked as a duplicate of this bug. ***
Comment 12 Martin Sandsmark 2016-08-13 17:33:38 UTC
*** Bug 357473 has been marked as a duplicate of this bug. ***
Comment 13 Martin Sandsmark 2016-08-13 17:34:01 UTC
*** Bug 357737 has been marked as a duplicate of this bug. ***
Comment 14 Martin Sandsmark 2016-08-13 17:34:38 UTC
*** Bug 358280 has been marked as a duplicate of this bug. ***
Comment 15 Martin Sandsmark 2016-08-13 17:34:51 UTC
*** Bug 358326 has been marked as a duplicate of this bug. ***
Comment 16 Martin Sandsmark 2016-08-13 17:36:37 UTC
*** Bug 354435 has been marked as a duplicate of this bug. ***
Comment 17 Martin Sandsmark 2016-08-13 17:36:53 UTC
*** Bug 356710 has been marked as a duplicate of this bug. ***
Comment 18 Martin Sandsmark 2016-08-13 17:37:44 UTC
*** Bug 361260 has been marked as a duplicate of this bug. ***
Comment 19 Martin Sandsmark 2016-08-13 17:37:55 UTC
*** Bug 365351 has been marked as a duplicate of this bug. ***
Comment 20 Christoph Feck 2016-12-08 13:24:40 UTC
*** Bug 373350 has been marked as a duplicate of this bug. ***
Comment 21 Christoph Feck 2017-02-03 21:44:14 UTC
*** Bug 358255 has been marked as a duplicate of this bug. ***
Comment 22 Christoph Feck 2017-02-03 21:45:32 UTC
*** Bug 371011 has been marked as a duplicate of this bug. ***
Comment 23 Kurt Hindenburg 2017-02-18 23:22:24 UTC
*** Bug 350924 has been marked as a duplicate of this bug. ***
Comment 24 Christoph Feck 2018-01-10 17:07:25 UTC
*** Bug 378512 has been marked as a duplicate of this bug. ***
Comment 25 Christoph Feck 2018-01-10 17:10:40 UTC
*** Bug 378562 has been marked as a duplicate of this bug. ***
Comment 26 Justin Zobel 2020-12-02 00:13:16 UTC
Thanks for the report. The duplicates on this seemed to have stopped around 2018.

As it's been a while since the last duplicate, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 27 djcole187 2020-12-02 00:30:43 UTC
Created attachment 133794 [details]
attachment-31932-0.html

When did i report this bug? It's been over 4years since I've turned on my
pc? Is someone else using my email? Weird...

On Wed., 2 Dec. 2020, 11:13 Justin Zobel, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=342201
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>                  CC|                            |justin.zobel@gmail.com
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #26 from Justin Zobel <justin.zobel@gmail.com> ---
> Thanks for the report. The duplicates on this seemed to have stopped around
> 2018.
>
> As it's been a while since the last duplicate, can you please test and
> confirm
> if this issue is still occurring or if this bug report can be marked as
> resolved.
>
> I've set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved" when you respond, thanks.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 28 Justin Zobel 2020-12-02 00:39:00 UTC
(In reply to djcole187 from comment #27)
> Created attachment 133794 [details]
> attachment-31932-0.html
> 
> When did i report this bug? It's been over 4years since I've turned on my
> pc? Is someone else using my email? Weird...
> 
> On Wed., 2 Dec. 2020, 11:13 Justin Zobel, <bugzilla_noreply@kde.org> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=342201
> >
> > Justin Zobel <justin.zobel@gmail.com> changed:
> >
> >            What    |Removed                     |Added
> >
> > ----------------------------------------------------------------------------
> >              Status|REPORTED                    |NEEDSINFO
> >                  CC|                            |justin.zobel@gmail.com
> >          Resolution|---                         |WAITINGFORINFO
> >
> > --- Comment #26 from Justin Zobel <justin.zobel@gmail.com> ---
> > Thanks for the report. The duplicates on this seemed to have stopped around
> > 2018.
> >
> > As it's been a while since the last duplicate, can you please test and
> > confirm
> > if this issue is still occurring or if this bug report can be marked as
> > resolved.
> >
> > I've set the bug status to "needsinfo" pending your response, please change
> > back to "reported" or "resolved" when you respond, thanks.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

You reported 2016-08-14(In reply to djcole187 from comment #27)
> Created attachment 133794 [details]
> attachment-31932-0.html
> 
> When did i report this bug? It's been over 4years since I've turned on my
> pc? Is someone else using my email? Weird...
> 
> On Wed., 2 Dec. 2020, 11:13 Justin Zobel, <bugzilla_noreply@kde.org> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=342201
> >
> > Justin Zobel <justin.zobel@gmail.com> changed:
> >
> >            What    |Removed                     |Added
> >
> > ----------------------------------------------------------------------------
> >              Status|REPORTED                    |NEEDSINFO
> >                  CC|                            |justin.zobel@gmail.com
> >          Resolution|---                         |WAITINGFORINFO
> >
> > --- Comment #26 from Justin Zobel <justin.zobel@gmail.com> ---
> > Thanks for the report. The duplicates on this seemed to have stopped around
> > 2018.
> >
> > As it's been a while since the last duplicate, can you please test and
> > confirm
> > if this issue is still occurring or if this bug report can be marked as
> > resolved.
> >
> > I've set the bug status to "needsinfo" pending your response, please change
> > back to "reported" or "resolved" when you respond, thanks.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

On the 14th of August 2016 you reported bug 353906 which was marked as a duplicate of this bug so you were added to the CC on it.
Comment 29 djcole187 2020-12-02 00:45:26 UTC
Created attachment 133795 [details]
attachment-32743-0.html

Well, I can't test to confirm. I'm sure it's resolved.

On Wed., 2 Dec. 2020, 11:39 Justin Zobel, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=342201
>
> --- Comment #28 from Justin Zobel <justin.zobel@gmail.com> ---
> (In reply to djcole187 from comment #27)
> > Created attachment 133794 [details]
> > attachment-31932-0.html
> >
> > When did i report this bug? It's been over 4years since I've turned on my
> > pc? Is someone else using my email? Weird...
> >
> > On Wed., 2 Dec. 2020, 11:13 Justin Zobel, <bugzilla_noreply@kde.org>
> wrote:
> >
> > > https://bugs.kde.org/show_bug.cgi?id=342201
> > >
> > > Justin Zobel <justin.zobel@gmail.com> changed:
> > >
> > >            What    |Removed                     |Added
> > >
> > >
> ----------------------------------------------------------------------------
> > >              Status|REPORTED                    |NEEDSINFO
> > >                  CC|                            |
> justin.zobel@gmail.com
> > >          Resolution|---                         |WAITINGFORINFO
> > >
> > > --- Comment #26 from Justin Zobel <justin.zobel@gmail.com> ---
> > > Thanks for the report. The duplicates on this seemed to have stopped
> around
> > > 2018.
> > >
> > > As it's been a while since the last duplicate, can you please test and
> > > confirm
> > > if this issue is still occurring or if this bug report can be marked as
> > > resolved.
> > >
> > > I've set the bug status to "needsinfo" pending your response, please
> change
> > > back to "reported" or "resolved" when you respond, thanks.
> > >
> > > --
> > > You are receiving this mail because:
> > > You are on the CC list for the bug.
>
> You reported 2016-08-14(In reply to djcole187 from comment #27)
> > Created attachment 133794 [details]
> > attachment-31932-0.html
> >
> > When did i report this bug? It's been over 4years since I've turned on my
> > pc? Is someone else using my email? Weird...
> >
> > On Wed., 2 Dec. 2020, 11:13 Justin Zobel, <bugzilla_noreply@kde.org>
> wrote:
> >
> > > https://bugs.kde.org/show_bug.cgi?id=342201
> > >
> > > Justin Zobel <justin.zobel@gmail.com> changed:
> > >
> > >            What    |Removed                     |Added
> > >
> > >
> ----------------------------------------------------------------------------
> > >              Status|REPORTED                    |NEEDSINFO
> > >                  CC|                            |
> justin.zobel@gmail.com
> > >          Resolution|---                         |WAITINGFORINFO
> > >
> > > --- Comment #26 from Justin Zobel <justin.zobel@gmail.com> ---
> > > Thanks for the report. The duplicates on this seemed to have stopped
> around
> > > 2018.
> > >
> > > As it's been a while since the last duplicate, can you please test and
> > > confirm
> > > if this issue is still occurring or if this bug report can be marked as
> > > resolved.
> > >
> > > I've set the bug status to "needsinfo" pending your response, please
> change
> > > back to "reported" or "resolved" when you respond, thanks.
> > >
> > > --
> > > You are receiving this mail because:
> > > You are on the CC list for the bug.
>
> On the 14th of August 2016 you reported bug 353906 which was marked as a
> duplicate of this bug so you were added to the CC on it.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 30 Bug Janitor Service 2020-12-17 04:33:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 31 Bug Janitor Service 2021-01-01 04:39:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!