Bug 223784 - Plasma crashes after disabling desktop effects with "radeon" driver with an ATI Radeon HD 2600 Pro [KPixmapCache::Private::mmapFile]
Summary: Plasma crashes after disabling desktop effects with "radeon" driver with an A...
Status: RESOLVED DUPLICATE of bug 182026
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: 2010-01-22 13:34 UTC by Shlomi Fish
Modified: 2010-01-22 23:03 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
A GDB session of plasma-desktop after its crash was triggered (73.23 KB, text/plain)
2010-01-22 15:25 UTC, Shlomi Fish
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shlomi Fish 2010-01-22 13:34:49 UTC
Version:            (using Devel)
Compiler:          gcc-c++-4.4.2-5mnb2 
OS:                Linux
Installed from:    Compiled sources

After I disabled the desktop effects (which by the way made transitioning to a different workspace unbearably slow,as it disabled the panel for many seconds after the switch), plasma crashed. I'm on Mandriva Linux Cooker using kdebase4-workspace-4.3.90-3mdv2010.1 with the "radeon" driver and an ATI Radeon HD 2600 Pro card.
Comment 1 Dario Andres 2010-01-22 13:39:52 UTC
- Is the crash reproducible all the times ?
- Do you get the Crash Handler dialog ?
Regards
Comment 2 Anne-Marie Mahfouf 2010-01-22 13:40:59 UTC
Backtrace?
Comment 3 Shlomi Fish 2010-01-22 13:51:40 UTC
(In reply to comment #1)
> - Is the crash reproducible all the times ?

No, now I've checked it and it isn't. Let me try by starting the desktop when the effects are on and then disabling it. 

> - Do you get the Crash Handler dialog ?

No, I don't. I don't get anything.

> Regards

Regards,

-- Shlomi Fish
Comment 4 Anne-Marie Mahfouf 2010-01-22 13:54:57 UTC
Can you run plasma-desktop through gdb and trigger the crash to get the backtrace please
Comment 5 Shlomi Fish 2010-01-22 15:25:12 UTC
Created attachment 40117 [details]
A GDB session of plasma-desktop after its crash was triggered

Here is the gdb session with the plasma-desktop after it crashed. What I did was try to enable the desktop effects right after start-up. I am providing a backtrace there.
Comment 6 Shlomi Fish 2010-01-22 15:26:03 UTC
Now provided the backtrace, so changing the status to NEW.
Comment 7 Dario Andres 2010-01-22 15:36:42 UTC
Pasting backtrace inline:
---

(gdb) bt
#0  0xb6f1d5b4 in KPixmapCache::Private::mmapFile (this=0x9ea6040, filename=
    ..., info=0x9ea6080, newsize=126341120)                                 
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:482        
#1  0xb6fc8e28 in KPixmapCache::Private::mmapFiles (this=0x9ea6040)         
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:415        
#2  0xb6fc8083 in KPixmapCache::recreateCacheFiles (this=0x9eabcf8)         
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:1232       
#3  0xb6fc8712 in KPixmapCache::Private::checkFileVersion (this=0x9ea6040,  
    filename=...)                                                           
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:732        
#4  0xb6fc89bb in KPixmapCache::Private::init (this=0x9ea6040)              
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:1037       
#5  0xb6fca4fa in KPixmapCache::discard (this=0x9eabcf8)                    
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:1262       
#6  0xb6fcabf1 in KPixmapCache::deleteCache (name=...)                      
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kpixmapcache.cpp:1240       
#7  0xb4f4f43e in Plasma::ThemePrivate::discardCache (this=0x9e5c988)       
    at /usr/src/debug/kdelibs-4.3.90/plasma/theme.cpp:221                   
#8  0xb4f4f6eb in Plasma::ThemePrivate::compositingChanged (this=0x9e5c988) 
    at /usr/src/debug/kdelibs-4.3.90/plasma/theme.cpp:213                   
#9  0xb4f50df7 in Plasma::Theme::qt_metacall (this=0x9e57498, _c=           
    InvokeMetaMethod, _id=2, _a=0xbfee9248)                                 
    at /usr/src/debug/kdelibs-4.3.90/build/plasma/theme.moc:108             
#10 0xb6c71ced in QMetaObject::metacall (object=0x9e57498, cl=176574328, idx=
---Type <return> to continue, or q <return> to quit---                       
    6, argv=0xbfee9248) at kernel/qmetaobject.cpp:237                        
#11 0xb6c80ae6 in QMetaObject::activate (sender=0x9eabf38, m=0xb718a5b0,     
    local_signal_index=0, argv=0xbfee9248) at kernel/qobject.cpp:3286        
#12 0xb6e8f625 in KSelectionWatcher::newOwner (this=0x9eabf38, _t1=20975399) 
    at /usr/src/debug/kdelibs-4.3.90/build/kdeui/kmanagerselection.moc:152   
#13 0xb6f14b00 in KSelectionWatcher::owner (this=0x9eabf38)                  
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kmanagerselection.cpp:451    
#14 0xb6f14cb5 in KSelectionWatcher::filterEvent (this=0x9eabf38, ev_P=      
    0xbfee97cc)                                                              
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kmanagerselection.cpp:468    
#15 0xb708f076 in KSelectionWatcher::Private::x11Event (this=0x9eabf08, ev_P=
    0xbfee97cc)                                                              
    at /usr/src/debug/kdelibs-4.3.90/kdeui/util/kmanagerselection.cpp:395    
#16 0xb702b85a in KAppX11HackWidget::publicx11Event (this=0x9eabf08, e=      
    0xbfee97cc)                                                              
    at /usr/src/debug/kdelibs-4.3.90/kdeui/kernel/kapplication.cpp:903       
#17 0xb6f2f16a in KApplication::x11EventFilter (this=0x9d8d220, _event=      
    0xbfee97cc)                                                              
    at /usr/src/debug/kdelibs-4.3.90/kdeui/kernel/kapplication.cpp:953       
#18 0xb321261c in PlasmaApp::x11EventFilter (this=0x9d8d220, event=0xbfee97cc)
    at /usr/src/debug/kdebase-workspace-4.3.90/plasma/desktop/shell/plasmaapp.cpp:567                                                                           
#19 0xb6208fb1 in qt_x11EventFilter (ev=0xbfee97cc)                             
    at kernel/qapplication_x11.cpp:399                                          
---Type <return> to continue, or q <return> to quit---                          
#20 0xb6218a0f in QApplication::x11ProcessEvent (this=0x9d8d220, event=         
    0xbfee97cc) at kernel/qapplication_x11.cpp:3231                             
#21 0xb6247628 in x11EventSourceDispatch (s=0x9d95a98, callback=0, user_data=   
    0x0) at kernel/qguieventdispatcher_glib.cpp:146                             
#22 0xb5915cc2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0     
#23 0xb5919598 in ?? () from /usr/lib/libglib-2.0.so.0                          
#24 0xb59196be in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0    
#25 0xb6c995e1 in QEventDispatcherGlib::processEvents (this=0x9d925c0, flags=   
    ...) at kernel/qeventdispatcher_glib.cpp:407                                
#26 0xb624717a in QGuiEventDispatcherGlib::processEvents (this=0x9d925c0,       
    flags=...) at kernel/qguieventdispatcher_glib.cpp:202                       
#27 0xb6c6afdd in QEventLoop::processEvents (this=0xbfee9a84, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.                                                                 
)                                                                               
    at kernel/qeventloop.cpp:149                                                
#28 0xb6c6b429 in QEventLoop::exec (this=0xbfee9a84, flags=...)                 
    at kernel/qeventloop.cpp:201                                                
#29 0xb6c6f5b0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981  
#30 0xb6188774 in QApplication::exec () at kernel/qapplication.cpp:3570         
#31 0xb31fa4f6 in kdemain (argc=1, argv=0x9d84750)                              
    at /usr/src/debug/kdebase-workspace-4.3.90/plasma/desktop/shell/main.cpp:112
#32 0x0804e131 in launch (argc=<value optimized out>,                           
    _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0,   
    envs=0x9d59160 "", reset_env=false, tty=0x0, avoid_loops=false,             
    startup_id_str=0x805129a "0")                                               
---Type <return> to continue, or q <return> to quit---                          
    at /usr/src/debug/kdelibs-4.3.90/kinit/kinit.cpp:706                        
#33 0x0804e86d in handle_launcher_request (sock=7, who=<value optimized out>)   
    at /usr/src/debug/kdelibs-4.3.90/kinit/kinit.cpp:1198                       
#34 0x0804f56c in handle_requests (waitForPid=<value optimized out>)            
    at /usr/src/debug/kdelibs-4.3.90/kinit/kinit.cpp:1391                       
#35 0x0804fe25 in main (argc=2, argv=0xbfeea1c4, envp=0xbfeea1d0)               
    at /usr/src/debug/kdelibs-4.3.90/kinit/kinit.cpp:1830
Comment 8 Anne-Marie Mahfouf 2010-01-22 15:51:26 UTC
wWhat about a new user? can you reproduce with default KDE desktop? What plasma theme is used?
Comment 9 Shlomi Fish 2010-01-22 18:49:05 UTC
(In reply to comment #8)
> wWhat about a new user? can you reproduce with default KDE desktop? What plasma
> theme is used?

I'm using the Mandriva Workspace theme, and the Cleanlooks widget style, and the Plastik Window decoration. 

I'll try with a new user and let you know of the outcome.

Regards,

-- Shlomi Fish
Comment 10 Shlomi Fish 2010-01-22 21:44:34 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > wWhat about a new user? can you reproduce with default KDE desktop? What plasma
> > theme is used?
> 
> I'm using the Mandriva Workspace theme, and the Cleanlooks widget style, and
> the Plastik Window decoration. 
> 
> I'll try with a new user and let you know of the outcome.
> 

OK, with a new user with a fresh .kde4, disabling the desktop effects causes kwin to crash and the borders and decorations of the windows to disappear.

Regards,

-- Shlomi Fish

> Regards,
> 
> -- Shlomi Fish
Comment 11 Dario Andres 2010-01-22 21:51:04 UTC
That's probably a different crash you could report to kwin.. (I guess it is a different BT, but it may be somehow related..)
Regards
Comment 12 Fredrik Höglund 2010-01-22 23:03:18 UTC

*** This bug has been marked as a duplicate of bug 182026 ***