aticonfig --swap-monitor crashes kicker

Bug #191493 reported by HfX
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have a big desktop configured with 2 monitors and a resolution of 3360*1050.
Sometimes the second monitor is on the left instead of the default on the right. So I use "aticonfig --swap-monitor" to change it quickly. Whenever I do that something crashes. I think it is kicker.
When I do it directly after logging in to kubuntu kicker will restart automatically. If i use it later, when a lot of programs are running I manually have to restart kicker after the aticonfig command.

I don't know, if this is aticonfig related or maybe a bug in kicker or whatever.
My system is up to date with the latest patches.

Here is my xorg.conf and some more info for your needs.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

Hardware:
HP Compaq Notebook 6715b (1680x1050) AMD64 but wit 32Bit Kubuntu Gutsy.

# xorg.conf (xorg X Window System server configuration file)
Section "ServerLayout"
 Identifier "Default Layout"
 screen 0 "Screen[0]" 0 0
 Inputdevice "Generic Keyboard"
 Inputdevice "Configured Mouse"
 Inputdevice "Synaptics Touchpad"
EndSection

Section "Files"
EndSection

Section "Module"
 Load "glx"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de"
 Option "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "Monitor"
 Identifier "Monitor[0]"
 Option "VendorName" "ATI Proprietary Driver"
 Option "ModelName" "Generic Autodetecting Monitor"
 Option "DPMS" "true"
 Horizsync 30.0 - 70.0
 Vertrefresh 50.0 - 160.0
EndSection

Section "Device"
 Identifier "Device[0]"
 Driver "fglrx"
 Option "VideoOverlay" "on"
 Option "OpenGLOverlay" "on"
 Option "DesktopSetup" "horizontal" # enable Big Desktop (reverse=links)
 Option "Mode2" "1280x1024" # Resolution for second monitor
 Option "DesktopSetup" "LVDS,AUTO" # 1st monitor LVDS, 2nd AUTO
 #Option "EnablePrivateBackZ" "yes" # Enable 3d support <- may not work
 Option "HSync2" "65" # Hsync frequency secondary display
 Option "VRefresh2" "60" # refresh rate secondary display
EndSection

Section "Screen"
 Identifier "Screen[0]"
 Device "Device[0]"
 Monitor "Monitor[0]"
 Defaultdepth 24
 SubSection "Display"
  Virtual 1680 1050
  Viewport 0 0
  Depth 24
 EndSubSection
EndSection

Section "Extensions"
 Option "Composite" "0"
EndSection

Revision history for this message
HfX (krasnojarsk) wrote :

I add a crash report now I created using the wizard it is attached now.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

either a kicker or aticonfig bug, but not xorg.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Does this still occur with KDE 3.5.10?

If so, could you please install kdebase-dbg and attach a new crash report with debugging symbols next time it happens?

Changed in kdebase:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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

Other bug subscribers

Bug attachments

Remote bug watches

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