Simply, after upgraded to Oneiric, KDE-Plasma do not "work" (graphical objects are displayed such as "fractal")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kde4libs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just what I've written in the summary: after login on a KDE session the display does not work: it's"trying" to generate and/or refresh the usual objects I expect, but they're partially invisible, seem like broken. All Ican do is reset the system by the "physical" button.
This behaviour began with the upgrade to 11.10, two weeks ago.
A Gnome session starts OK (unity or classic), I'm writing on a Ubuntu session.
thank you
Alessandro Ognissanti
(sorry for my english: I'm Italian, eh eh...)
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: kdelibs-bin 4:4.7.2-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 28 22:02:08 2011
ExecutablePath: /usr/bin/kded4
ProcCmdline: /usr/bin/kded4 --nocrashhandler
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
Solid:
ConnectionUsag
?? () from /usr/lib/
Title: kded4 crashed with SIGSEGV in Solid::
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (14 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev scanner video
XsessionErrors:
(nm-applet:4014): libnotify-WARNING **: Failed to connect to proxy
(nautilus:4017): libnotify-WARNING **: Failed to connect to proxy
(nautilus:4017): Gtk-CRITICAL **: gtk_action_
(nautilus:4017): Gtk-CRITICAL **: gtk_action_
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #846054, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.