[Ubuntu-x-swat] [Bug 1351262] [NEW] precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)'
Public bug reported: Precise alternate preseeded installations fail with unmet deps due to the following: Jul 31 08:54:29 in-target: The following information may help to resolve the situation: Jul 31 08:54:29 in-target: Jul 31 08:54:29 in-target: The following packages have unmet dependencies: Jul 31 08:54:29 in-target: libgl1-mesa-dri-lts-trusty : Conflicts: libgl1-mesa-dri Jul 31 08:54:29 in-target: libgl1-mesa-glx : Conflicts: libgl1 Jul 31 08:54:29 in-target: libgl1-mesa-glx-lts-trusty : Conflicts: libgl1 Jul 31 08:54:29 in-target: Conflicts: libgl1-mesa-glx Jul 31 08:54:29 in-target: libglapi-mesa-lts-trusty : Conflicts: libglapi-mesa Jul 31 08:54:29 in-target: xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~) Jul 31 08:54:29 in-target:Conflicts: libgl1-mesa-glx (= 0~) Jul 31 08:54:29 in-target:Conflicts: libglapi-mesa (= 0~) Jul 31 08:54:29 in-target: E Jul 31 08:54:29 in-target: : Jul 31 08:54:29 in-target: Unable to correct problems, you have held broken packages. The d-i installs based on iso were broken until 20140731 due to kernel version mismatch between the archive and d-i. Therefore it's proving very hard to find from our side when this was introduced. This issue impacts both amd64 and i386 installations and the failing preseeded install logs can be found: https://jenkins.qa.ubuntu.com/job/precise-alternate-i386_default/ https://jenkins.qa.ubuntu.com/job/precise-alternate-amd64_default/ The installer syslog is attached. The preseed being used for this install is: http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise/view/head:/preseeds-common/base ** Affects: xorg-lts-transitional (Ubuntu) Importance: Undecided Status: New ** Attachment added: d-i-syslog.log https://bugs.launchpad.net/bugs/1351262/+attachment/4167294/+files/d-i-syslog.log ** Package changed: xorg-lts-raring (Ubuntu) = xorg-lts-transitional (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1351262 Title: precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1351262/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1206860] [NEW] xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images
Public bug reported: The precise alternate installations of i386 and amd64 have the following installation error reported. Probably a known issue since report.html lists this package as uninstallable. Bug is required to account the smoke test failure. Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and install software Jul 31 09:00:15 debconf: Adding [ITEM] - [Select and install software] Jul 31 09:00:15 debconf: -- 0 Jul 31 09:00:15 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jul 31 09:00:15 debconf: -- 0 question will be asked Jul 31 09:00:15 debconf: -- GO report.html: == (http://cdimage.ubuntu.com/precise/daily/pending/report.html) xorg-lts-raring 1:7.7+1ubuntu4~precise1 produces uninstallable binaries: xserver-xorg-input-all-lts-raring (amd64 i386) The impacted smoke jobs: == https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-amd64_default/902/console and https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-i386_default/888/console An d-i syslog is attached. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing qa-daily-testing ** Attachment added: d-i syslog.log https://bugs.launchpad.net/bugs/1206860/+attachment/3755815/+files/d-i%20syslog.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1206860 Title: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1206860/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1206860] Re: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images
** Description changed: The precise alternate installations of i386 and amd64 have the - following installation error reported. Probably a known issue since - report.html lists this package as uninstallable. Bug is required to - account the smoke test failure. + following installation error reported with today's images (20130731). + Probably a known issue since report.html lists this package as + uninstallable. Bug is required to account the smoke test failure. + + Steps to reproduce: + 1. Install precise alternate image of 20130731. + 2. Leave the default selections and continue the installations + 3. The error will be seen towards the end of the installation. + Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E - Jul 31 09:00:15 in-target: : + Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. - Jul 31 09:00:15 in-target: + Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and install software Jul 31 09:00:15 debconf: Adding [ITEM] - [Select and install software] Jul 31 09:00:15 debconf: -- 0 Jul 31 09:00:15 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jul 31 09:00:15 debconf: -- 0 question will be asked Jul 31 09:00:15 debconf: -- GO report.html: == (http://cdimage.ubuntu.com/precise/daily/pending/report.html) xorg-lts-raring 1:7.7+1ubuntu4~precise1 produces uninstallable binaries: - xserver-xorg-input-all-lts-raring (amd64 i386) + xserver-xorg-input-all-lts-raring (amd64 i386) The impacted smoke jobs: == https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-amd64_default/902/console and https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-i386_default/888/console An d-i syslog is attached. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1206860 Title: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1206860/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1122072] Re: [Precise amd64 on VirtualBox] Fatal server error: no screen found in Xorg.0.log
Confirmed with ubuntu-desktop-amd64 and ubuntu-desktop-i386 when using VirtualBox. Did not see this issue on virt-manager using KVM and on hardware. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1122072 Title: [Precise amd64 on VirtualBox] Fatal server error: no screen found in Xorg.0.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1122072/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
** Attachment added: with-1-1-5-2.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3482830/+files/with-1-1-5-2.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
xserver-xorg-video-cirrus 1:1.5.2-0ubuntu1 has NOT fixed the issue. Please see the screenshot attached above. Thanks -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
This only occurs with with KVM and not with VBox. The installation of 20121210 on VBox came up with correct desktop. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
@bryce: Booting with quantal kernel does not work around the problem. The desktop is still corrupted. Please see attached image ** Attachment added: with_quantal_kernel.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3446108/+files/with_quantal_kernel.png ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: xserver-xorg-video-cirrus (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
Right, thanks for the workaround. Raring VMs work fine when started with -vga std. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1080674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1065113] Re: Xorg crashed with SIGABRT in free()
Tried with quantal final image and i could not reproduce this after more than 5 attempts. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1065113 Title: Xorg crashed with SIGABRT in free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1065113/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1065113] Re: Xorg crashed with SIGABRT in free()
I have tried a few times today to reproduce this without success. I'll keep trying and would add the trace once i hit the bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1065113 Title: Xorg crashed with SIGABRT in free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1065113/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
** Attachment added: dmesg_bad_second_boot https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401556/+files/dmesg_bad_second_boot -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
** Attachment added: dmesg_good_first_boot https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401554/+files/dmesg_good_first_boot -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
Failure was observed in the second boot -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
When attempted with plymouth-splash disabled I am able to bring up the desktop in the standard graphics mode. When plymouth-splash was re- enabled, the issue is reproducible with mainline kernel 3.5.5. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Was able to reproduce with 3.5.4 mainline kernel version as well -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Occurs with 3.5.3 mainline kernel as well with plymouth-splash enabled -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
A fresh install with quantal desktop - amd+mac 20121011 also has the same issue. First boot after the installation went well but the subsequent ones do not boot in standard graphics mode. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
When tried with 20120724.2 amd+mac quantal desktop, this issue was not reproducible (with ~10 reboots). Hence looking at bug 1066228 it appears be a regression that occurred between alpha3 and beta 1. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
So here is the list of test runs, 20120724.2 - worked 20120918.1-worked 20121001 - worked 20121011 - FAILED The kernel was updated to the latest on top of a working 20121001 and it still worked -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
@apw Rebooted many times (more than 20) after updating the kernel to the latest on a known (20121001) good image, it worked ok, no failures could be observed. Removing /var/lib/ureadahead/pack from the known bad image seem to solve the issue. When it was made sure the file is removed before the reboot, the next reboot did not have this issue, the desktop came up on the standard gfx mode. When the file was present the next reboot failed, not so deterministically every time, but most of the times. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] [NEW] Fatal server error: Can not run in framebuffer mode on reboot
Public bug reported: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 qa-manual-testing quantal rls-q-incoming running-unity ubuntu ** Description changed: - Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. - The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. + Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. + The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: - + Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Apple Inc. Device [106b:00e6] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal
[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
The above logs were taken from the first boot, hence does not have the error information. The attached tar contains the log after the failure ** Attachment added: log.tar.gz https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3398945/+files/log.tar.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Reproducible with 20121015.2 as well, after entire disk fresh installation -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1065113] [NEW] Xorg crashed with SIGABRT in free()
Public bug reported: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started 1. Start your machine with the install media in place 1.1 Wait to hear the drums 2. Press Ctrl+s to start the screen-reader 3. Press Alt+Tab to change to the installer 4. Press Up or Down arrow to select your language(default is English) 5. Press Tab once to Try Ubuntu 6. Press Enter 7. Wait for the Desktop to begin the installation. 8. Press Super+1 to begin the installation. Super is the left windows key *** The crash occurred at this point ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background none vt7 :0 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity Signal: 6 SourcePackage: xorg-server StacktraceTop: free () from /lib/x86_64-linux-gnu/libc.so.6 SrvXkbFreeServerMap () SrvXkbFreeKeyboard () XkbFreeInfo () ?? () Title: Xorg crashed with SIGABRT in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N4010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 q-manual-testing quantal ubuntu ** Visibility changed to: Public ** Description changed: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started + + 1. Start your machine with the install media in place + 1.1 Wait to hear the drums + 2. Press Ctrl+s to start the screen-reader + 3. Press Alt+Tab to change to the installer + 4. Press Up or Down arrow to select your language(default is English) + 5. Press Tab once to Try Ubuntu + 6. Press Enter + 7. Wait for the Desktop to begin the installation. + 8. Press Super+1 to begin the installation. Super is the left windows key + + *** The crash occurred at this point + ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0456] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background
[Ubuntu-x-swat] [Bug 1064418] [NEW] Xorg crashed with SIGABRT in cirRefreshArea()
Public bug reported: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=396df7fe-1541-4c33-9642-1ffbcc8091c0 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 cirRefreshArea () from /usr/lib/xorg/modules/drivers/cirrus_drv.so ?? () from /usr/lib/xorg/modules/libshadowfb.so ?? () ?? () Title: Xorg crashed with SIGABRT in cirRefreshArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace qa-manual-testing quantal rls-q-incoming ubuntu ** Visibility changed to: Public ** Description changed: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner - 2. The workspace switcher was clicked *** at this point the vm logged out and logged in + 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: - + ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: - Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) -Subsystem: Red Hat, Inc Device [1af4:1100] + Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) + Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: - + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic
[Ubuntu-x-swat] [Bug 1064418] Re: Xorg crashed with SIGABRT in cirRefreshArea()
Occurrs in an i386 vm with 20121009 on a different amd64 host as well. ** Description changed: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner - 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself + 2. The workspace switcher was clicked *** at this point the vm logged out by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=396df7fe-1541-4c33-9642-1ffbcc8091c0 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 cirRefreshArea () from /usr/lib/xorg/modules/drivers/cirrus_drv.so ?? () from /usr/lib/xorg/modules/libshadowfb.so ?? () ?? () Title: Xorg crashed with SIGABRT in cirRefreshArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1064418 Title: Xorg crashed with SIGABRT in cirRefreshArea() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1064418/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
