Bug 161731 - crash on configuring the Digital Clock if this is not the most right widget in the panel
Summary: crash on configuring the Digital Clock if this is not the most right widget i...
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 11:04 UTC by Wolfgang Mader
Modified: 2008-07-05 17:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Mader 2008-05-07 11:04:28 UTC
Version:            (using Devel)
Installed from:    Compiled sources

Hello,

here my setting:
-Panel is configured to sit on the top of my screen.
-I do have two physical screens connected to my computer.

What I did:
-Adding the Analog Clock widget to the panel as the most right applet in the panel. On my screen the order from the right is then:
          >Analog Clock
          >Digital Clock, the standard clock of the panel
          >all other things running in the panel

-Removing the Analog Clock from the panel. Now, there is some space where the clock was drawn. Therefore the Digital Clock is the most right applet (at least it should), but it is drawn with space to the right border.

-Right click on the Digital Clock and choose Digital Clock Settings crashes plasma.

Here is the backtrace:
------------------------------------------------------------------------------------
Application: Plasma Workspace (plasma), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb55c5720 (LWP 5288)]
[New Thread 0xb211ab90 (LWP 5291)]
[New Thread 0xb2f31b90 (LWP 5290)]
[New Thread 0xb3b1bb90 (LWP 5289)]
[KCrash handler]
#6  0xb6a37f94 in __cxxabiv1::__class_type_info::__do_upcast ()
   from /usr/lib/libstdc++.so.6
#7  0xb714eaa9 in QGraphicsLayoutItemPrivate::effectiveSizeHints (
    this=0xb733ccf8, constraint=@0xbfee04a0)
    at graphicsview/qgraphicslayoutitem.cpp:157
#8  0xb714ebd8 in QGraphicsLayoutItem::effectiveSizeHint (this=0x80c22a8, 
    which=16, constraint=@0xbfee04a0)
    at graphicsview/qgraphicslayoutitem.cpp:697
#9  0xb7158eda in QGridLayoutItem::sizeHint (this=0x83999a0, 
    which=Qt::PreferredSize, constraint=@0xbfee04a0)
    at graphicsview/qgridlayoutengine.cpp:543
#10 0xb71590df in QGridLayoutItem::box (this=0x83999a0, 
    orientation=<value optimized out>, constraint=-1)
    at graphicsview/qgridlayoutengine.cpp:554
#11 0xb715b728 in QGridLayoutEngine::fillRowData (this=0x8158aa4, 
    rowData=0x8158b08, styleInfo=@0xbfee09ac, orientation=Qt::Horizontal)
    at graphicsview/qgridlayoutengine.cpp:1285
#12 0xb715c87f in QGridLayoutEngine::ensureColumnAndRowData (this=0x8158aa4, 
    styleInfo=@0xbfee09ac) at graphicsview/qgridlayoutengine.cpp:1417
#13 0xb715ca06 in QGridLayoutEngine::ensureGeometries (this=0x8158aa4, 
    styleInfo=@0xbfee09ac, size=@0xbfee0940)
    at graphicsview/qgridlayoutengine.cpp:1432
#14 0xb715cf4c in QGridLayoutEngine::setGeometries (this=0x8158aa4, 
    styleInfo=@0xbfee09ac, contentsGeometry=@0xbfee0988)
    at graphicsview/qgridlayoutengine.cpp:961
#15 0xb714fb6f in QGraphicsLinearLayout::setGeometry (this=0x812c670, 
    rect=@0xbfee0a08) at graphicsview/qgraphicslinearlayout.cpp:489
#16 0xb714dff8 in QGraphicsLayout::activate (this=0x812c670)
    at graphicsview/qgraphicslayout.cpp:251
#17 0xb714e076 in QGraphicsLayout::widgetEvent (this=0x812c670, e=0x853f440)
    at graphicsview/qgraphicslayout.cpp:314
#18 0xb7153383 in QGraphicsWidget::event (this=0x815af20, event=0x853f440)
    at graphicsview/qgraphicswidget.cpp:1153
#19 0xb6ba6e6c in QApplicationPrivate::notify_helper (this=0x8074330, 
    receiver=0x815af20, e=0x853f440) at kernel/qapplication.cpp:3766
#20 0xb6baba09 in QApplication::notify (this=0x805a6a8, receiver=0x815af20, 
    e=0x853f440) at kernel/qapplication.cpp:3360
#21 0xb7acca4d in KApplication::notify (this=0x805a6a8, receiver=0x815af20, 
    event=0x853f440)
    at /tmp/buildd/kde4libs-4.0.72/kdeui/kernel/kapplication.cpp:311
#22 0xb749a1e9 in QCoreApplication::notifyInternal (this=0x805a6a8, 
    receiver=0x815af20, event=0x853f440) at kernel/qcoreapplication.cpp:587
#23 0xb749b599 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x804b430)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 0xb749b7bd in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1091
#25 0xb74c55df in postEventSourceDispatch (s=0x8076520)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#26 0xb5a07978 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb5a0abce in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x08076498 in ?? ()
#29 0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
------------------------------------------------------------------------------------
Comment 1 Alex Merry 2008-07-05 12:38:38 UTC
I can't reproduce this in trunk (either the excess space when removing the analogue clock or the crash).  Can you test with the 4.1 betas or trunk?
Comment 2 Thomas Georgiou 2008-07-05 17:33:20 UTC
aaron said to close bugs as fixed those that cannot be reproduced in 4.1