Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages I wasn't quite sure where to put this...so its under general kde now. I've created a shortcut to dolphin in the desktop widget area. Right clicked on the shortcut, properties and then on the preview tab. It then gives a phonon error at the top right stating that playback on my MS Lifechat LX-3000 does not work & falling back to HDA Intel. (Playback does continue as normal on the Lifechat though). Amarok is running in the background. The screen also flashes white for a few seconds and then returns to normal. The taskbar panel is gone after the white flash and then looks like its being rebuilt/redrawn. The window that had the properties in it disappears. It looks like something is crashing & then quickly recovering/resetting itself. I'll gladly provide any other info/logs needed. havocxphere [@@@] gmail.com Thank you Kubuntu 8.10 x86 Kde 4.1.2 Radeonhd drivers Composting = Disabled Everything up-to-date with latest stuff the default repos
I'm not sure if this is a folder view problem, but probably you (plasma-devs) should know :-)
this is a problem with the preview plugin (which isn't plasma, btw). we'll need a backtrace in any case.
Like I said...I wasn't sure where to put it since it seems to involve a number of things. Regarding the backtrace: Can't provide one since its not one of those "standard" crashes where it gives a backtrace. It just gives the phonon error at the top right, redraws/rebuilds the taskbar and the preview dialog goes AWOL. Unless there is another way to get a backtrace? Its not a serious issue...its just something that doesn't look like things went down the way the devs had in mind. So I figured I'd report it. If you guys think its not significant then I'd be OK with this bug being closed. :)
well, it is crashing, and i'd like to know why =) can you run plasma in gdb? (do `run --nofork` when you do) and get a backtrace that way?
Created attachment 28982 [details] info from crash dialog thing
Created attachment 28983 [details] Crash info from gdb
Created attachment 28984 [details] Screenshot of crash
Created attachment 28985 [details] 2nd screenshot. Taskbar AWOL
Now I'm suddenly getting a crash dialog thing. (???) (Maybe its something with the updates that went through today...looked like Openoffice & kernel stuff) The crash happens with shortcuts, but not png and not txt. Also crashes when doing the shortcut preview from dolphin. The crash info doesn't seem to contain a lot of useful info though...loads of debug info missing, but I don't know how to fix that. I also wasn't quite sure if I did the gdb thing right (pretty much 1st week w/ linux). Hope its right ;) The screen shots show what the user is seeing, with screenshot 2 following ~2sec after screenshot 1. The whole screenshot facility thing seems to go down too cause it took a few tries to get a valid screenshot onto the clipboard. Sorry if you/everyone got a bunch of emails due to all the attachments....don't know how to do them all in 1 go. HX
tutorial on creating helpful crash reports: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports it's crashing in xine, possibly a phonon problem. i'm going to shift this bug over there, but they'll want a better backtrace as well. it might be phonon related, but it also might be xine itself that is broken on your system.
Created attachment 29001 [details] New backtrace with more info
Created attachment 29002 [details] Screenshot of KDE info tool on sound tab
I've uploaded a new trace done after installing some xine and phonon -dgb packages. Seems to include more info now. I've also added a screenshot of KDE Info tool which shows some of the sound-related hardware info. The crash report dialog doesn't always appear...very sporadic for this bug.
This bug was fixed in 8.10, but it appears to be back in 9.04. However, I should add that the 9.04 is running in Virtualbox on top of my real 8.10 install, so it might just be the way the Virtualbox emulated GFX card interacts with the OS.
Pasting backtrace into body so it shows up on duplicate searches and we can easily see it. :) A bug doesn't have to be deterministic to exist. Have you seen this lately, though? [KCrash handler] #6 0xafef5b76 in xshm_open_plugin (class_gen=0x8b6bc90, visual_gen=0x89e9e6c) at video_out_xcbshm.c:1161 #7 0xb2495942 in _x_load_video_output_plugin (this=0x8955f70, id=0x0, visual_type=11, visual=0x89e9e6c) at load_plugins.c:1556 #8 0xb24959d8 in xine_open_video_driver (this=0x8955f70, id=0xb251283a "auto", visual_type=11, visual=0x89e9e6c) at load_plugins.c:1620 #9 0xb250e38f in ?? () from /usr/lib/kde4/phonon_xine.so #10 0xb250ed87 in ?? () from /usr/lib/kde4/phonon_xine.so #11 0xb24ffe21 in ?? () from /usr/lib/kde4/phonon_xine.so #12 0xb26435d3 in Phonon::Factory::createVideoWidget (parent=0x89ea568) at /build/buildd/phonon-4.2.0/phonon/factory.cpp:286 #13 0xb2648867 in Phonon::VideoWidgetPrivate::createBackendObject ( this=0x89e9ec8) at /build/buildd/phonon-4.2.0/phonon/videowidget.cpp:70 #14 0xb26484b3 in VideoWidget (this=0x89ea568, parent=0x8952398) at /build/buildd/phonon-4.2.0/phonon/videowidget.cpp:42 #15 0xb265cb4b in ?? () from /usr/lib/kde4/kfileaudiopreview.so #16 0xb265d651 in KPluginFactory::createInstance<KFileAudioPreview, QWidget> () from /usr/lib/kde4/kfileaudiopreview.so #17 0xb78efb67 in KPluginFactory::create () from /usr/lib/libkdecore.so.5 #18 0xb68e28e0 in KFileMetaPreview::createAudioPreview () from /usr/lib/libkio.so.5 #19 0xb68e2e14 in KFileMetaPreview::previewProviderFor () from /usr/lib/libkio.so.5 #20 0xb68e26f7 in KFileMetaPreview::showPreview () from /usr/lib/libkio.so.5 #21 0xb68f50eb in KPreviewPropsPlugin::currentPageChanged () from /usr/lib/libkio.so.5 #22 0xb68f5168 in KPreviewPropsPlugin::qt_metacall () from /usr/lib/libkio.so.5 #23 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #25 0xb7b2ca69 in KPageDialog::currentPageChanged () from /usr/lib/libkdeui.so.5 #26 0xb7b2cb10 in KPageDialog::qt_metacall () from /usr/lib/libkdeui.so.5 #27 0xb68f675a in KPropertiesDialog::qt_metacall () from /usr/lib/libkio.so.5 #28 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #29 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #30 0xb7b333b9 in KPageWidget::currentPageChanged () from /usr/lib/libkdeui.so.5 #31 0xb7b33505 in ?? () from /usr/lib/libkdeui.so.5 #32 0xb7b335ce in KPageWidget::qt_metacall () from /usr/lib/libkdeui.so.5 #33 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #34 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #35 0xb7b2e009 in KPageView::currentPageChanged () from /usr/lib/libkdeui.so.5 #36 0xb7b2edae in ?? () from /usr/lib/libkdeui.so.5 #37 0xb7b2f867 in KPageView::qt_metacall () from /usr/lib/libkdeui.so.5 #38 0xb7b3358a in KPageWidget::qt_metacall () from /usr/lib/libkdeui.so.5 #39 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #40 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #41 0xb70cdf09 in QItemSelectionModel::currentChanged () from /usr/lib/libQtGui.so.4 #42 0xb70ce0ad in QItemSelectionModel::setCurrentIndex () from /usr/lib/libQtGui.so.4 #43 0xb7b30987 in ?? () from /usr/lib/libkdeui.so.5 #44 0xb7b31d01 in ?? () from /usr/lib/libkdeui.so.5 #45 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #46 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #47 0xb6fbc4f3 in QTabWidget::currentChanged () from /usr/lib/libQtGui.so.4 #48 0xb6fbe354 in ?? () from /usr/lib/libQtGui.so.4 #49 0xb6fbe507 in QTabWidget::qt_metacall () from /usr/lib/libQtGui.so.4 #50 0xb7641a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #51 0xb76427e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #52 0xb6fb50d3 in QTabBar::currentChanged () from /usr/lib/libQtGui.so.4 #53 0xb6fb9d8a in QTabBar::setCurrentIndex () from /usr/lib/libQtGui.so.4 #54 0xb6fba0fd in QTabBar::mousePressEvent () from /usr/lib/libQtGui.so.4 #55 0xb6c0d989 in QWidget::event () from /usr/lib/libQtGui.so.4 #56 0xb6fba198 in QTabBar::event () from /usr/lib/libQtGui.so.4 #57 0xb6bb58ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #58 0xb6bbe121 in QApplication::notify () from /usr/lib/libQtGui.so.4 #59 0xb7afb72d in KApplication::notify () from /usr/lib/libkdeui.so.5 #60 0xb762ce61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #61 0xb6bbd3ae in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #62 0xb6c27696 in ?? () from /usr/lib/libQtGui.so.4 #63 0xb6c26a25 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #64 0xb6c507ea in ?? () from /usr/lib/libQtGui.so.4 #65 0xb597b6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #66 0xb597eda3 in ?? () from /usr/lib/libglib-2.0.so.0 #67 0xb597ef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #68 0xb7657478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #69 0xb6c4fee5 in ?? () from /usr/lib/libQtGui.so.4 #70 0xb762b52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #71 0xb762b6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #72 0xb762dda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #73 0xb6bb5767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #74 0xb7fa6491 in kdemain () from /usr/lib/libkdeinit4_plasma.so #75 0x080485b2 in _start () #0 0xb7fee430 in __kernel_vsyscall ()
(In reply to comment #15) > Have you seen this lately, though? I've been running gnome for 9.04 so no new info really. I'll probably return to kde on 9.10 after exams & check then again. If it does occur again I'll post here. If you like you can close this bug for now as it is kinda in limbo atm...I'm guessing I can re-open it later if need be. Not sure what the policy is regarding these things.
Any news on this for current KDE 4.3.4 or KDE SC 4.4 beta 2?
Closing for lack of feedback.