Bug 320719 - Mint 14, after upgrading KDE to 4.10.3 no submenus visible and only one window at a time
Summary: Mint 14, after upgrading KDE to 4.10.3 no submenus visible and only one windo...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: 4.10.3
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs
URL: http://forums.linuxmint.com/viewtopic...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 13:41 UTC by ArkadioG
Modified: 2013-06-14 09:19 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 ArkadioG 2013-06-04 13:41:12 UTC
So, besides what I wrote in mint forum this what I noticed:
- if I choose session type to KDE plasma.... failsafe mode - all works ok - I can change pulpits, add panels, all submenus are visible, I can see multiple windows.
- if I choose other session type f.e: KDE plasma, Default - I cannot see submenus and pop windows, only one window is visible, other dissappears, but using alt-tab I can switch between them
- I tried to clear cache (as I found somewhere in forums) in /var/tmp/kdecache-myuser and deleted all plasma* files but it didn't help
- I did deleting also from new user account i created but it didn't help 
- new user account was set perfectly, I found no bad behave

If any one could just told how to restore default KDE/plasma looks.

I did updates and upgrades and dist-upgrades like in this thread:
http://forums.linuxmint.com/viewtopic.php?f=109&t=124912#p684113

Reproducible: Always

Steps to Reproduce:
1.login using KDE plasma desktop or default session on my account
2. all works perfectly when I use KDE plasma failsafe mode
3.all works perfectly for new user created after updating to 4.10.3
Actual Results:  
I'm using KDE-failsafe mode to login

Expected Results:  
I can log using default or KDE plasma sessions (no failsafe mode)
Comment 1 ArkadioG 2013-06-07 10:28:23 UTC
Bug resolved in 4.10.4