monitor & Display settings crush

Bug #153083 reported by BGGR
6
Affects Status Importance Assigned to Milestone
displayconfig-gtk (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

on start up of the kubuntu...after the login i get crash message from proccess manager.
The font are on very low quality (and small)
Whene i try to run monitor & Display settings the program crash and on Backtrace i have the following:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210132272 (LWP 6172)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb68e9454 in ?? () from /usr/lib/libXrandr.so.2
#7 0x00020a71 in ?? ()
#8 0x0859a590 in ?? ()
#9 0x00000048 in ?? ()
#10 0xb6bc0b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()

please can help me with this???

before i had the Dapper and it was work with out problem.... now with Feisty.... :(-

Revision history for this message
Sebastian Heinlein (glatzor) wrote :

Seems to be a bug in your graphics card driver. Which card do you use?

Changed in displayconfig-gtk:
status: New → Incomplete
Revision history for this message
BGGR (bg-freemail) wrote :

ATI Radeon X550

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Displayconfig is dead for Intrepid. RIP guidance-display-backend

Changed in displayconfig-gtk:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.