[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~)'

2014-08-01 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1206860] [NEW] xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images

2013-07-31 Thread Parameswaran Sivatharman
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:

[Ubuntu-x-swat] [Bug 1206860] Re: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images

2013-07-31 Thread Parameswaran Sivatharman
** 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

[Ubuntu-x-swat] [Bug 1122072] Re: [Precise amd64 on VirtualBox] Fatal server error: no screen found in Xorg.0.log

2013-02-11 Thread Parameswaran Sivatharman
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.

[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.

2013-01-14 Thread Parameswaran Sivatharman
** 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.

[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.

2013-01-14 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)

2012-12-10 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)

2012-11-28 Thread Parameswaran Sivatharman
@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 **

[Ubuntu-x-swat] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)

2012-11-21 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1065113] Re: Xorg crashed with SIGABRT in free()

2012-11-13 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1065113] Re: Xorg crashed with SIGABRT in free()

2012-10-24 Thread Parameswaran Sivatharman
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:

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-17 Thread Parameswaran Sivatharman
** 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.

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-17 Thread Parameswaran Sivatharman
** 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.

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-17 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-16 Thread Parameswaran Sivatharman
@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

[Ubuntu-x-swat] [Bug 1066883] [NEW] Fatal server error: Can not run in framebuffer mode on reboot

2012-10-15 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot

2012-10-15 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot

2012-10-15 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1065113] [NEW] Xorg crashed with SIGABRT in free()

2012-10-10 Thread Parameswaran Sivatharman
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.

[Ubuntu-x-swat] [Bug 1064418] [NEW] Xorg crashed with SIGABRT in cirRefreshArea()

2012-10-09 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 1064418] Re: Xorg crashed with SIGABRT in cirRefreshArea()

2012-10-09 Thread Parameswaran Sivatharman
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

[Ubuntu-x-swat] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

2012-09-17 Thread Parameswaran Sivatharman
** 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'