Bug 889043 - system settings -> workspace behavior > virtual desktops crashes plasma-desktop
Summary: system settings -> workspace behavior > virtual desktops crashes plasma-desktop
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-20 05:20 UTC by George R. Goffe
Modified: 2013-02-13 23:36 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:36:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gzip of a "massaged" script file of the gdb of plasma-desktop program (14.12 KB, application/x-gzip)
2012-12-20 05:20 UTC, George R. Goffe
no flags Details

Description George R. Goffe 2012-12-20 05:20:59 UTC
Created attachment 666520 [details]
gzip of a "massaged" script file of the gdb of plasma-desktop program

Description of problem:

attempting to activate "different widgets for each desktop" crashes plasma-desktop

Version-Release number of selected component (if applicable):

kde-workspace-4.8.5-2.fc16.x86_64

How reproducible:

always

Steps to Reproduce:
1.open system settings
2.naviagate to workspace behavior 
3.navigate to virtual desktops
4.select "different widgets for each desktop"
5.poke apply
6.repeat #4-#5 if necessary
  
Actual results:

plasma-desktop produces stack trace

Expected results:


Additional info:

I restarted plasma-desktop and then tried the gdb /usr/bin/plasma-desktop $(pid-of-plasma-desktop)

I altered the settings and got several traces in the enclosed file.

Do you need more info? Let me know, PLEASE.

Comment 1 Kevin Kofler 2012-12-24 00:47:40 UTC
There's not a single backtrace of plasma-desktop in your attachment. They're all of Akonadi, which is aborting because MySQL returns an error to it, and MySQL returns that error because it doesn't like being run as root without special options. Those backtraces have nothing to do with your bug report.

Comment 2 Fedora End Of Life 2013-01-16 20:04:26 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 23:36:58 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.