Bug 313520 - changed to xrender by mistake
Summary: changed to xrender by mistake
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.8.5
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-19 20:32 UTC by perezomail
Modified: 2013-01-20 18:58 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description perezomail 2013-01-19 20:32:13 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.2
Operating System: Linux 3.2.29 x86_64

-- Information about the crash:
- What I was doing when the application crashed:

- Custom settings of the application:
changed to xrender by mistake cannot get back to opengl after restartin g both program and system. I was closing down after playing supertuxkart

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fcdb1cb2f00 in xcb_glx_query_server_string_string_length () from /usr/lib64/libxcb-glx.so.0
#6  0x00007fcdb293bdd4 in ?? () from /usr/lib64/libGL.so.1
#7  0x00007fcdb29196c2 in ?? () from /usr/lib64/libGL.so.1
#8  0x00007fcdb29155d9 in glXQueryVersion () from /usr/lib64/libGL.so.1
#9  0x00007fcdb2da84e7 in ?? () from /usr/lib64/kde4/kcm_kwincompositing.so
#10 0x00007fcdb2d9fff7 in ?? () from /usr/lib64/kde4/kcm_kwincompositing.so
#11 0x00007fcdb2d9d2d7 in ?? () from /usr/lib64/kde4/kcm_kwincompositing.so
#12 0x00007fcdc4976ebf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt/lib/libQtCore.so.4
#13 0x00007fcdc5c75772 in QAbstractButton::clicked(bool) () from /usr/lib64/qt/lib/libQtGui.so.4
#14 0x00007fcdc59c995e in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#15 0x00007fcdc59ca190 in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#16 0x00007fcdc566129a in QWidget::event(QEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#17 0x00007fcdc5611f5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#18 0x00007fcdc5616f54 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#19 0x00007fcdc6598136 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#20 0x00007fcdc4961abe in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt/lib/libQtCore.so.4
#21 0x00007fcdc56ae2fa in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#22 0x00007fcdc56ae701 in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#23 0x00007fcdc568c588 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt/lib/libQtGui.so.4
#24 0x00007fcdc56b23e2 in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#25 0x00007fcdbf915c35 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007fcdbf915f68 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x00007fcdbf916024 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007fcdc498fc36 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#29 0x00007fcdc56b206e in ?? () from /usr/lib64/qt/lib/libQtGui.so.4
#30 0x00007fcdc496080f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#31 0x00007fcdc4960a98 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib/libQtCore.so.4
#32 0x00007fcdc4965738 in QCoreApplication::exec() () from /usr/lib64/qt/lib/libQtCore.so.4
#33 0x000000000040ae44 in ?? ()
#34 0x00007fcdc3a0fa95 in __libc_start_main () from /lib64/libc.so.6
#35 0x000000000040ae9d in _start ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-01-19 21:15:58 UTC
This is a crash in the driver.
Unfortunately the backtrace does not include enough information to say what triggers it.

See: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(In reply to comment #1)
> changed to xrender by mistake cannot get back to opengl after restartin g
> both program and system.
Since you rebooted: did you eventually update kernel, X11 or graphics driver interim?

Please also post the output of glxinfo.
Comment 2 perezomail 2013-01-20 18:49:02 UTC
reinstalled no longer an issue for me

On Sat, Jan 19, 2013 at 3:15 PM, Thomas Lübking
<thomas.luebking@gmail.com> wrote:
> https://bugs.kde.org/show_bug.cgi?id=313520
>
> Thomas Lübking <thomas.luebking@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|---                         |UPSTREAM
>
> --- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> ---
> This is a crash in the driver.
> Unfortunately the backtrace does not include enough information to say what
> triggers it.
>
> See:
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
>
> (In reply to comment #1)
>> changed to xrender by mistake cannot get back to opengl after restartin g
>> both program and system.
> Since you rebooted: did you eventually update kernel, X11 or graphics driver
> interim?
>
> Please also post the output of glxinfo.
>
> --
> You are receiving this mail because:
> You reported the bug.