Application: systemsettings (1.0) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.0.0-17-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: Clicking on Profile Information crashes KolorManager every time. Selecting one device and then an other one crashes KolorManager every time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [Current thread is 1 (Thread 0x7f5951bfd7a0 (LWP 2728))] Thread 2 (Thread 0x7f593bf01700 (LWP 2729)): #0 0x00007f594f0a9473 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f594c956f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f594c957429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f594f8245a6 in QEventDispatcherGlib::processEvents (this=0x1f00d50, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f594f7f3d82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f594f7f3fd7 in QEventLoop::exec (this=0x7f593bf00db0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f594f6f3077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #7 0x00007f594f7d3aff in QInotifyFileSystemWatcherEngine::run (this=0x1efb940) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f594f6f609b in QThreadPrivate::start (arg=0x1efb940) at thread/qthread_unix.cpp:298 #9 0x00007f594ce28efc in start_thread (arg=0x7f593bf01700) at pthread_create.c:304 #10 0x00007f594f0b559d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f5951bfd7a0 (LWP 2728)): [KCrash Handler] #6 _int_malloc (av=0x7f594f36e1c0, bytes=24) at malloc.c:4428 #7 0x00007f594f0503cd in __GI___libc_malloc (bytes=24) at malloc.c:3660 #8 0x00007f593a800c9b in CUPSGetDevices () from /usr/lib/colour/modules/liboyranos_CUPS_cmm_module.so.0.4.0 #9 0x00007f593a801f83 in CUPSConfigs_FromPattern () from /usr/lib/colour/modules/liboyranos_CUPS_cmm_module.so.0.4.0 #10 0x00007f593b297e36 in oyConfigs_FromDomain () from /usr/lib/liboyranos.so.0 #11 0x00007f593b2981bf in oyConfigs_FromDeviceClass () from /usr/lib/liboyranos.so.0 #12 0x00007f593b29c396 in oyDevicesGet () from /usr/lib/liboyranos.so.0 #13 0x00007f59327ff2b3 in kminfo::populateDeviceProfiles (this=<optimized out>, deviceListTree=0x80338c0) at /home/rj/Downloads/kolor-manager/information/kminfo.cpp:278 #14 0x00007f59327ffda9 in kminfo::populateInstalledProfileList (this=0x80242e0) at /home/rj/Downloads/kolor-manager/information/kminfo.cpp:219 #15 0x00007f5932800918 in kminfo::kminfo (this=0x80242e0, parent=<optimized out>) at /home/rj/Downloads/kolor-manager/information/kminfo.cpp:163 #16 0x00007f5932803f94 in KPluginFactory::createInstance<kminfo, QWidget> (parentWidget=<optimized out>, parent=<optimized out>, args=...) at /usr/include/kpluginfactory.h:477 #17 0x00007f594ffe6481 in KPluginFactory::create (this=0x1e49450, iface=0x7f595131d0c0 "KCModule", parentWidget=0x0, parent=0x770b910, args=..., keyword=<optimized out>) at ../../kdecore/util/kpluginfactory.cpp:203 #18 0x00007f59517f946e in create<KCModule> (parent=0x770b910, this=0x1e49450, args=..., keyword=..., parentWidget=0x0) at ../../kdecore/util/kpluginfactory.h:531 #19 createInstance<KCModule> (error=0x7fff29824d70, args=..., parent=0x770b910, parentWidget=0x0, this=0x1d45b40) at ../../kdecore/services/kservice.h:553 #20 createInstance<KCModule> (error=0x7fff29824d70, args=..., parent=0x770b910, this=0x1d45b40) at ../../kdecore/services/kservice.h:530 #21 KCModuleLoader::loadModule (mod=..., report=KCModuleLoader::Inline, parent=0x770b910, args=...) at ../../kutils/kcmoduleloader.cpp:89 #22 0x00007f59517fe4d8 in KCModuleProxyPrivate::loadModule (this=0x1f690a0) at ../../kutils/kcmoduleproxy.cpp:106 #23 0x00007f59517ff1f5 in KCModuleProxy::realModule (this=<optimized out>) at ../../kutils/kcmoduleproxy.cpp:83 #24 0x00007f59517ff232 in KCModuleProxy::showEvent (this=0x770b910, ev=0x7fff29825c00) at ../../kutils/kcmoduleproxy.cpp:197 #25 0x00007f59504b6da5 in QWidget::event (this=0x770b910, event=0x7fff29825c00) at kernel/qwidget.cpp:8569 #26 0x00007f59504662e4 in notify_helper (e=0x7fff29825c00, receiver=0x770b910, this=0x1ae6200) at kernel/qapplication.cpp:4559 #27 QApplicationPrivate::notify_helper (this=0x1ae6200, receiver=0x770b910, e=0x7fff29825c00) at kernel/qapplication.cpp:4531 #28 0x00007f595046b163 in QApplication::notify (this=0x7fff29828020, receiver=0x770b910, e=0x7fff29825c00) at kernel/qapplication.cpp:4420 #29 0x00007f5951198bf6 in KApplication::notify (this=0x7fff29828020, receiver=0x770b910, event=0x7fff29825c00) at ../../kdeui/kernel/kapplication.cpp:311 #30 0x00007f594f7f4f9c in QCoreApplication::notifyInternal (this=0x7fff29828020, receiver=0x770b910, event=0x7fff29825c00) at kernel/qcoreapplication.cpp:876 #31 0x00007f59504b91c0 in sendEvent (event=0x7fff29825c00, receiver=0x770b910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #32 QWidgetPrivate::show_helper (this=0x770ed40) at kernel/qwidget.cpp:7542 #33 0x00007f59504b8fb7 in QWidgetPrivate::showChildren (this=<optimized out>, spontaneous=false) at kernel/qwidget.cpp:7850 #34 0x00007f59504b90ad in QWidgetPrivate::show_helper (this=<optimized out>) at kernel/qwidget.cpp:7489 #35 0x00007f59504b94b2 in QWidget::setVisible (this=0x1ddf230, visible=<optimized out>) at kernel/qwidget.cpp:7764 #36 0x00007f59504b9026 in show (this=0x1ddf230) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:494 #37 QWidgetPrivate::showChildren (this=<optimized out>, spontaneous=false) at kernel/qwidget.cpp:7852 #38 0x00007f59504b90ad in QWidgetPrivate::show_helper (this=<optimized out>) at kernel/qwidget.cpp:7489 #39 0x00007f59504b94b2 in QWidget::setVisible (this=0x1ddf2e0, visible=<optimized out>) at kernel/qwidget.cpp:7764 #40 0x00007f595049ad19 in show (this=0x1ddf2e0) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:494 #41 QStackedLayout::setCurrentIndex (this=0x1dd9a50, index=3) at kernel/qstackedlayout.cpp:311 #42 0x00007f59511c8577 in KPageViewPrivate::_k_pageSelected (this=0x1dd9570, index=<optimized out>, previous=...) at ../../kdeui/paged/kpageview.cpp:235 #43 0x00007f59511c8742 in KPageView::qt_metacall (this=0x1dd9530, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff29826150) at ./kpageview.moc:100 #44 0x00007f59511cba30 in KPageWidget::qt_metacall (this=0x1dd9530, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff29826150) at ./kpagewidget.moc:76 #45 0x00007f594f809589 in QMetaObject::activate (sender=0x7a46500, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff29826150) at kernel/qobject.cpp:3566 #46 0x00007f59509e04d7 in QItemSelectionModel::selectionChanged (this=<optimized out>, _t1=<optimized out>, _t2=<optimized out>) at .moc/release-shared/moc_qitemselectionmodel.cpp:166 #47 0x00007f59509e5f11 in QItemSelectionModel::emitSelectionChanged (this=0x7a46500, newSelection=<optimized out>, oldSelection=<optimized out>) at itemviews/qitemselectionmodel.cpp:1600 #48 0x00007f59509e72c1 in QItemSelectionModel::select (this=0x7a46500, selection=<optimized out>, command=...) at itemviews/qitemselectionmodel.cpp:1110 #49 0x00007f59511c92bc in select (command=<optimized out>, selection=<optimized out>, this=<optimized out>) at ../../kdeui/paged/kpageview_p.cpp:619 #50 KDEPrivate::SelectionModel::select (this=<optimized out>, selection=<optimized out>, command=<optimized out>) at ../../kdeui/paged/kpageview_p.cpp:613 #51 0x00007f59509b2ce5 in QListView::setSelection (this=<optimized out>, rect=<optimized out>, command=...) at itemviews/qlistview.cpp:1379 #52 0x00007f595098ed9a in QAbstractItemView::mousePressEvent (this=0x1dde420, event=<optimized out>) at itemviews/qabstractitemview.cpp:1690 #53 0x00007f59504b6dd9 in QWidget::event (this=0x1dde420, event=0x7fff29827320) at kernel/qwidget.cpp:8358 #54 0x00007f5950873dd6 in QFrame::event (this=0x1dde420, e=0x7fff29827320) at widgets/qframe.cpp:557 #55 0x00007f595098853b in QAbstractItemView::viewportEvent (this=0x1dde420, event=0x7fff29827320) at itemviews/qabstractitemview.cpp:1644 #56 0x00007f594f7f5128 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x770f5d0, event=0x7fff29827320) at kernel/qcoreapplication.cpp:986 #57 0x00007f59504662af in notify_helper (e=0x7fff29827320, receiver=0x770f5d0, this=0x1ae6200) at kernel/qapplication.cpp:4555 #58 QApplicationPrivate::notify_helper (this=0x1ae6200, receiver=0x770f5d0, e=0x7fff29827320) at kernel/qapplication.cpp:4531 #59 0x00007f595046bb0f in QApplication::notify (this=<optimized out>, receiver=0x770f5d0, e=0x7fff29827320) at kernel/qapplication.cpp:4102 #60 0x00007f5951198bf6 in KApplication::notify (this=0x7fff29828020, receiver=0x770f5d0, event=0x7fff29827320) at ../../kdeui/kernel/kapplication.cpp:311 #61 0x00007f594f7f4f9c in QCoreApplication::notifyInternal (this=0x7fff29828020, receiver=0x770f5d0, event=0x7fff29827320) at kernel/qcoreapplication.cpp:876 #62 0x00007f59504672b2 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #63 QApplicationPrivate::sendMouseEvent (receiver=0x770f5d0, event=0x7fff29827320, alienWidget=0x770f5d0, nativeWidget=0x1c7cb30, buttonDown=0x770f5d0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170 #64 0x00007f59504e3955 in QETWidget::translateMouseEvent (this=0x1c7cb30, event=<optimized out>) at kernel/qapplication_x11.cpp:4617 #65 0x00007f59504e280a in QApplication::x11ProcessEvent (this=0x7fff29828020, event=0x7fff29827be0) at kernel/qapplication_x11.cpp:3732 #66 0x00007f595050b862 in x11EventSourceDispatch (s=0x1adbe30, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #67 0x00007f594c956a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #68 0x00007f594c957258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #69 0x00007f594c957429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #70 0x00007f594f82453f in QEventDispatcherGlib::processEvents (this=0x1a9d4b0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #71 0x00007f595050b4ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #72 0x00007f594f7f3d82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #73 0x00007f594f7f3fd7 in QEventLoop::exec (this=0x7fff29827fb0, flags=...) at kernel/qeventloop.cpp:204 #74 0x00007f594f7f9067 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #75 0x000000000040a7d5 in main (argc=5, argv=0x7fff298282e8) at ../../../systemsettings/app/main.cpp:49 Reported using DrKonqi
Unfortunately I can not reproduce. It looks like the crash happens in the Oyranos CUPS module. But that appears to have no debug symbols. Can you post your PPD's, under which the crash occurs, in the hope to reproduce?
The PPD's with crash Oyranos are appreciated to see.
Do you by any chance have multiple printers/printer drivers installed? It seems that I can slightly reproduce the error by installing 3 or more PPDs on my system.
(In reply to comment #3) > Do you by any chance have multiple printers/printer drivers installed? It > seems that I can slightly reproduce the error by installing 3 or more PPDs > on my system. Great, so you can already reproduce. Can you send me your PPD's please? I would like to install them here temporarily and check. valgrind keeps here totally silent.
Created attachment 70574 [details] Collection of PPDs used to reproduce error. All three of these PPD files should be used together to reproduce bug.
(In reply to comment #5) > Created attachment 70574 [details] > Collection of PPDs used to reproduce error. > > All three of these PPD files should be used together to reproduce bug. Thanks, can reproduce.
pushed a fix into Oyranos git 76412f29 * [CUPS]: check string lenght Please let us know, if that fixes the issue.
(In reply to comment #1) > Unfortunately I can not reproduce. > It looks like the crash happens in the Oyranos CUPS module. But that appears > to have no debug symbols. > Can you post your PPD's, under which the crash occurs, in the hope to > reproduce? Sorry, i have not been online over the weekend. Do you still need the PPDs? I have three different printers installed. Btw. one of them is shown three times in the KolorManager window.
(In reply to comment #8) > (In reply to comment #1) > > Unfortunately I can not reproduce. > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > to have no debug symbols. > > Can you post your PPD's, under which the crash occurs, in the hope to > > reproduce? > > Sorry, i have not been online over the weekend. > Do you still need the PPDs? > I have three different printers installed. > Btw. one of them is shown three times in the KolorManager window. Can you check Oyranos from git? How does you build Oyranos on ubuntu?
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #1) > > > Unfortunately I can not reproduce. > > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > > to have no debug symbols. > > > Can you post your PPD's, under which the crash occurs, in the hope to > > > reproduce? > > > > Sorry, i have not been online over the weekend. > > Do you still need the PPDs? > > I have three different printers installed. > > Btw. one of them is shown three times in the KolorManager window. > > Can you check Oyranos from git? How does you build Oyranos on ubuntu? (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #1) > > > Unfortunately I can not reproduce. > > > It looks like the crash happens in the Oyranos CUPS module. But that appears > > > to have no debug symbols. > > > Can you post your PPD's, under which the crash occurs, in the hope to > > > reproduce? > > > > Sorry, i have not been online over the weekend. > > Do you still need the PPDs? > > I have three different printers installed. > > Btw. one of them is shown three times in the KolorManager window. > > Can you check Oyranos from git? How does you build Oyranos on ubuntu? i have installed the one, provided via GetDeb. never tried to deploy it myself. i will have a look at it - maybe i am able to build it.
The CUPS plug-in had a print queue string length limit of 24 characters inside. As a workaround you might want to test shorter print queue names.
(In reply to comment #11) > The CUPS plug-in had a print queue string length limit of 24 characters > inside. As a workaround you might want to test shorter print queue names. after building oyranos and kolorManager from git, i do not see any devices at all....
(In reply to comment #12) > (In reply to comment #11) > > The CUPS plug-in had a print queue string length limit of 24 characters > > inside. As a workaround you might want to test shorter print queue names. > > after building oyranos and kolorManager from git, i do not see any devices > at all.... I think to had to remove all elder Oyranos modules and after that devices showed up again.
(In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > The CUPS plug-in had a print queue string length limit of 24 characters > > > inside. As a workaround you might want to test shorter print queue names. > > > > after building oyranos and kolorManager from git, i do not see any devices > > at all.... > > I think to had to remove all elder Oyranos modules and after that devices > showed up again. thx - its working now (without crashing)!! just one additional question: i have my new monitor connected via display port and get always: WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_() found issues bytes_after_return: 128 WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414 oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031 2560x1440+0+0 WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450 oyX1GetMonitorInfo_() no EDID available from X properties: "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA" using Xorg log fallback. any hint ?
(In reply to comment #14) > thx - its working now (without crashing)!! Thanks for reporting!
> just one additional question: > i have my new monitor connected via display port and get always: > > WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_() > found issues bytes_after_return: 128 > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414 > oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031 > 2560x1440+0+0 > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450 > oyX1GetMonitorInfo_() > no EDID available from X properties: > "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA" > using Xorg log fallback. > > any hint ? Some drivers do not appropriately report EDID information from monitors. Oyranos needs that information to identify the device and eventually create as a fallback a basic ICC profile. $ xprop -len 4 -root | grep EDID or $ xrandr --props should show you the availability of a EDID data block. You use ATI, nvidia, intel graphics and with proprietary or open source driver?
(In reply to comment #16) > > just one additional question: > > i have my new monitor connected via display port and get always: > > > > WARNING 8.390000: [-1] oyranos_monitor_x11.c:179 oyX1Monitor_getProperty_() > > found issues bytes_after_return: 128 > > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:414 > > oyX1GetMonitorInfo_() found /var/log/Xorg.0.log in ":0.0": FUS 2031 > > 2560x1440+0+0 > > WARNING 8.390000: oyOptions_s[20258]="oyOptions_s" oyranos_monitor_x11.c:450 > > oyX1GetMonitorInfo_() > > no EDID available from X properties: > > "XFree86_DDC_EDID1_RAWDATA"/"EDID_DATA" > > using Xorg log fallback. > > > > any hint ? > > Some drivers do not appropriately report EDID information from monitors. > Oyranos needs that information to identify the device and eventually create > as a fallback a basic ICC profile. > $ xprop -len 4 -root | grep EDID > or > $ xrandr --props > should show you the availability of a EDID data block. > You use ATI, nvidia, intel graphics and with proprietary or open source > driver? its an ATI FirePro V4800 using the proprietary driver for 10bit. here is the output of the commands above: rj@Desktop:~/Downloads/test/kolor-manager/build$ xprop -len 4 -root | grep EDID XFree86_DDC_EDID1_RAWDATA(INTEGER) = 0, -1, -1, -1 rj@Desktop:~/Downloads/test/kolor-manager/build$ xrandr --props Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 2560 x 2560 DFP1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm _ICC_PROFILE: ... EDID_DATA: 00ffffffffffff001ab3ef07c6020000 2f150104b53c22783a8e05ad4f33b026 0d5054a54b00a940b300950081008180 010101010101565e00a0a0a029503020 350055502100001e000000fd00174c0f 631e000a202020202020000000fc0050 3237542d36204950530a2020000000ff 00595635573030303731300a202001dc SignalFormat: DisplayPort ConnectorType: DisplayPort 2560x1440 60.0*+ ......