[Bug 161791] Re: Gparted starts very very slow and "buggy"
I found gparted to suffer of a extremly slow start with one of my few remaining fat32 partitions. While scanning for devices, gparted runs dosfsck -a -v, which, when automatically scans for errors and tries to repair them. For large fats, this takes a long time and greatly impairs the ability to use gparted at all... -- Gparted starts very very slow and "buggy" https://bugs.launchpad.net/bugs/161791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160862] Re: users-admin (System->Administration->Users and Groups) overwrites group file
This happened to me today, and although I was able to restore /etc/group and /etc/gshadow, more things remain broken in my system, for example pulseaudio, networkmanager, bluetooth, policykit, consolekit and (maybe the root cause) dbus... My syslog is being spammed by pulseaudio failing and many tools from system -> administration just segfault. I'm seriously tempted to just format & reinstall... -- users-admin (System->Administration->Users and Groups) overwrites group file https://bugs.launchpad.net/bugs/160862 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160862] Re: users-admin (System->Administration->Users and Groups) overwrites group file
** Attachment added: "users admin destroying groups and users" http://launchpadlibrarian.net/39363327/users-admin-authlog -- users-admin (System->Administration->Users and Groups) overwrites group file https://bugs.launchpad.net/bugs/160862 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570310] Re: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Reinstalling systemd fixed it for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570310 Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1570310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563207] Re: python2.6 assert failure: python: ../../src/xcb_io.c:249: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
** Also affects: exaile Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563207 Title: python2.6 assert failure: python: ../../src/xcb_io.c:249: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555158] Re: glxinfo crashed with SIGSEGV in XF86DRIQueryExtension()
Using a laptop with hybrid graphics (integrated intel & dedicated amd gpu), this bug hits me while running in integrated mode. I am using a hybrid xorg.conf that uses either gpu if activated in bios. For me, the fglrx driver is unfortunately required for proper load-dependent (dynamic) frequency scaling of the dedicated GPU without flickering at frequency changes. With the intel driver running, libgl crashes every time it is used... -- glxinfo crashed with SIGSEGV in XF86DRIQueryExtension() https://bugs.launchpad.net/bugs/555158 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555158] Re: glxinfo crashed with SIGSEGV in XF86DRIQueryExtension()
I found that you don't need uninstall fglrx (or nvidia, as that driver will ship its own libGL as well) to use mesa libGL again - you can use sudo update-alternative --set gl_conf /path/to/ld.so.conf To see the available GL configurations, run update-alternatives --list gl_conf For example, if you run one of the open source drivers such as intel, radeon or nouveau, update the gl configuration alternative to the mesa configuration. sudo update-alternative --set gl_conf/usr/lib/mesa/ld.so.conf Or, if you run fglrx run sudo update-alternative --set gl_conf /usr/lib/fglrx/ld.so.conf Nvidia ships its own GL configuration alternative, which works the same. After doing so, you need to run sudo ldconfig to reconfigure the dynamic linker run-time bindings. It may be better to do so when X is not running, as e.g. fglrx will crash if you switch to mesa while it is running. -- glxinfo crashed with SIGSEGV in XF86DRIQueryExtension() https://bugs.launchpad.net/bugs/555158 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
SIM cards come PIN-locked by default over here, and there is no out-of- the box way of unlocking it without inserting it into a phone that is capable of doing so. NetworkManager does not store the PIN in the keyring, so there's a PIN prompt at every login. Actually, there are currently two PIN unlock dialogues, a small one, a larger, more descriptive one, and a small, plain one. Without auto-connect, I get the larger PIN unlock dialogue at login, and the smaller one if I try to unlock the device later on. Sometimes, it appears to me that both are created at once and one tries to close the other, but that does not impair functionality. The idea of setting the connection of auto-connect was to enter the PIN and have NM connect automatically afterwards, now it's two more clicks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
** Changed in: network-manager-applet (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
Yes, without auto connect, the applet no longer crashes, which is of course a better solution than the workaround. Nevertheless, auto-connect with PIN-locked devices is a valid configuration option (and one that the UI exposes), so I'd still consider this a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] [NEW] nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
Public bug reported: This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb: $ lsusb | grep "Mobile Broadband" Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again. Oh and of course, the full error message (with version 0.8.1.998 from PPA, will see later if the line number changed from the Maverick version) ERROR:applet-device-gsm.c:769:gsm_get_secrets: assertion failed: (info) ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Description changed: This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb: $ lsusb | grep "Mobile Broadband" Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again. + + Oh and of course, the full error message: + + ERROR:applet-device-gsm.c:769:gsm_get_secrets: assertion failed: (info) ** Description changed: This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb: $ lsusb | grep "Mobile Broadband" Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again. - Oh and of course, the full error message: + Oh and of course, the full error message (with version 0.8.1.988 from + PPA, will see later if the line number changed from the Maverick + version) ERROR:applet-device-gsm.c:769:gsm_get_secrets: assertion failed: (info) ** Description changed: This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb: $ lsusb | grep "Mobile Broadband" Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again. - Oh and of course, the full error message (with version 0.8.1.988 from + Oh and of course, the full error message (with version 0.8.1.998 from PPA, will see later if the line number changed from the Maverick version) ERROR:applet-device-gsm.c:769:gsm_get_secrets: assertion failed: (info) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
** Changed in: network-manager-applet (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
Reopening because the crash cannot be reported by ubuntu-bug, the message is (translated from german): The problem can not be reported The application was terminated by an error assertion, but the message could not be loaded. Apport cannot process this crash. (Das Problem kann nicht gemeldet werden: Die Anwendung wurde aufgrund einer fehlerhaften Assertion beendet, doch die Meldung konnte nicht geladen werden. Apport kann diesen Absturz nicht verarbeiten.) I'll attach the .crash if that is of any use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869283/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
apport information ** Tags added: apport-collected ** Description changed: This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb: $ lsusb | grep "Mobile Broadband" Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again. Oh and of course, the full error message (with version 0.8.1.998 from PPA, will see later if the line number changed from the Maverick version) ERROR:applet-device-gsm.c:769:gsm_get_secrets: assertion failed: (info) + --- + Architecture: amd64 + CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden + DistroRelease: Ubuntu 10.10 + IfupdownConfig: + auto lo + iface lo inet loopback + InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) + IpRoute: + 10.146.226.176/29 dev wwan0 proto kernel scope link src 10.146.226.179 metric 3 + 169.254.0.0/16 dev wwan0 scope link metric 1000 + default via 10.146.226.178 dev wwan0 proto static + Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden + Package: network-manager-applet (not installed) + ProcEnviron: + LANG=de_DE.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 + Tags: ubuntu-une maverick + Uname: Linux 2.6.35-25-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Attachment added: "Gconf.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869281/+files/Gconf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] NetDevice.eth0.txt
apport information ** Attachment added: "NetDevice.eth0.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869284/+files/NetDevice.eth0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869282/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869285/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] NetDevice.wlan0.txt
apport information ** Attachment added: "NetDevice.wlan0.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869286/+files/NetDevice.wlan0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869288/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869289/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869290/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] nm-system-settings.conf.txt
apport information ** Attachment added: "nm-system-settings.conf.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869292/+files/nm-system-settings.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] NetDevice.wwan0.txt
apport information ** Attachment added: "NetDevice.wwan0.txt" https://bugs.edge.launchpad.net/bugs/721106/+attachment/1869287/+files/NetDevice.wwan0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
The maverick version crashes as well, I did the apport-collect thing, I hope it will be of use to you. If the report indicates that nm-applet is running happily, it's because I had to use the workaround to get online to report the crash, as it is currently my only option to get online. ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721106] Re: nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
0.4+git.20100809t153145.be28089-0ubuntu1 from maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721106 Title: nm-applet crashes with assertion error in applet-device- gsm.c:769:gsm_get_secrets -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659205] [NEW] [fglrx] fails to detect correct resolution with non-multiple of 64 virtual desktop area
Public bug reported: If you setup a big desktop that spans two monitors, gnome-display- properties is required to add a Virtual line to the subsection "Display" in section "screen" of the xorg.conf as generated by aticonfig. If (at least) the horizontal resolution (maybe the vertical as well) is NOT a multiple of 64, this will render fglrx unable to report the correct resolution of either display to xrandr. For example, for two displays side-by-side with a physical resolution of 1680x1050 each, gnome-display-properties will insert: Virtual 3360 1050 however, after logging off and on, xrandr will no longer report 1680x1050 as a valid resolution (missing from xrandr -q and consequently in the gnome-display-properties ui) for either display unless you increase the virtual resolution to a multiple of 64: Virtual 3392 3392 This is on a Lenovo ThinkPad T500, using the integrated display and DisplayPort output. Steps to reproduce this: a) initiate xorg.conf using sudo aticonfig --initial (if not done already by fglrx-installer; move your own customized xorg.conf away if present) b) log off and on again, make sure you are running fglrx using fglrxinfo and that xrandr -q reports the correct physical resolution of your integrated/primary display c) connect external/secondary display d) make sure xrandr -q reports correct physical resolution of external display e) go to gnome-display-properties, untick clone mode, put displays side-by-side, apply (or do that using xrandr parameters) d) agree to the suggestion that a Virtual line needs to be added to your xorg.conf to accomodate for the larger desktop area e) log off, log on expected behaviour: gnome-display-properties (or xrandr) should now be able to put the two displays in big/extended desktop mode side-by-side with their corresponding physical resolutions actual behaviour: xrandr does no longer detect the correct physical resolution of either display. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Description changed: If you setup a big desktop that spans two monitors, gnome-display- properties is required to add a Virtual line to the subsection "Display" in section "screen" of the xorg.conf as generated by aticonfig. If (at least) the horizontal resolution (maybe the vertical as well) is NOT a multiple of 64, this will render fglrx unable to report the correct resolution of either display to xrandr. For example, for two displays side-by-side with a physical resolution of 1680x1050 each, gnome-display-properties will insert: Virtual 3360 1050 however, after logging off and on, xrandr will no longer report 1680x1050 as a valid resolution (missing from xrandr -q and consequently in the gnome-display-properties ui) for either display unless you increase the virtual resolution to a multiple of 64: Virtual 3392 3392 This is on a Lenovo ThinkPad T500, using the integrated display and DisplayPort output. Steps to reproduce this: - a) initiate xorg.conf using sudo aticonfig --initial (if not done already be fglrx-installer; move your own customized xorg.conf away if present) + a) initiate xorg.conf using sudo aticonfig --initial (if not done already by fglrx-installer; move your own customized xorg.conf away if present) b) log off and on again, make sure you are running fglrx using fglrxinfo and that xrandr -q reports the correct physical resolution of your integrated/primary display c) connect external/secondary display d) make sure xrandr -q reports correct physical resolution of external display e) go to gnome-display-properties, untick clone mode, put displays side-by-side, apply (or do that using xrandr parameters) d) agree to the suggestion that a Virtual line needs to be added to your xorg.conf to accomodate for the larger desktop area e) log off, log on expected behaviour: gnome-display-properties (or xrandr) should not be able to put the two displays in big/extended desktop mode side-by-side with their corresponding physical resolutions actual behaviour: xrandr does no longer detect the correct physical resolution of either display. ** Description changed: If you setup a big desktop that spans two monitors, gnome-display- properties is required to add a Virtual line to the subsection "Display" in section "screen" of the xorg.conf as generated by aticonfig. If (at least) the horizontal resolution (maybe the vertical as well) is NOT a multiple of 64, this will render fglrx unable to report the correct resolution of either display to xrandr. For example, for two displays side-by-side with a physical resolution of 1680x1050 each, gnome-display-properties will insert: Virtual 3360 1050 however, after logging off and on, xrandr will no longer report 1680x1050 as a valid resolution (missing from xrandr -q
