[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10
Saw a bunch of at-spi2 errors in .xsession-errors. Reinstalled at- spi2-core, and those errors went away. Still no desktop. Deleting .config/dconf/user did the trick. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run top, it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10
So to be clear: my desktop is still utterly broken, but the one on an installer disc for the same version is not. Hopefully there is a simple configuration problem. I haven't done anything very special, I thought. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run top, it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10
A piece of good news: I did get a working desktop when booting from the 14.10 installer, for the same architecture. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run top, it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10
While the system is in this state, ps does show a compiz process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run top, it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437765] [NEW] No desktop after upgrade to 14.10
Public bug reported: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run top, it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-Fn, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-arrow. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart:
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
The version that was installed on March 31 was 3.13.0.20.24. The version I uninstalled right after that was 3.13.0.18.38. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
According to the dpkg.log for that date, quite a lot: libc-bin for amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6 etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0, libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk, python3-problem-report, python3-apport, binfmt-support, dh-apport, libgtk2-perl, python-boto, python-lxml, python3-lxml, unity-webapps-qml, mobile-broadband-provider-info, python-keystoneclient, The day before I upgraded among other things libffi6 (for i386 and amd64) and libffi-dev, dconf-gsettings-backend, dconf-service, libdconf1, various dconf tools and frontends, libglib2.0-*, libunity- control-center1 and unity-control-center, libido3-0.1-0, lxc and related packages, libapparmor1 and apparmor, libqt5positioning5, libunity-gtk3-parser0, openjdk-7 and icedtea-7, ubuntu-release-upgrader and update-manager, libcompizconfig0, compiz-gnome, compiz-plugins- default, libdecoration0, compiz-core, compiz, im-config, kerneloops- daemon, indicator-*, unity-scope-*, libreoffice, unity, libunity- core-6.0.9, unity-services, ubuntu-mono, libvirt, the kernel, and dh- apparmor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
I first upgraded to 14.10; that didn't change anything. Trying 15.04 now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
No change in 15.04. I can add the resolution with xrandr, and after that I can use it. But after reboot, I have to do it again. The upgrade got stuck with a black screen and no networking, but I eventually got out of it with the apt-get dist-upgrade dance from the console. I hope that hasn't messed things up. It may matter that I've got the monitor's DVI port hooked up to my computer's HDMI port. It was the only way to get things working: the monitor doesn't support its full native resolution on HDMI, and the Haswell builtin graphics only supports the resolution on HDMI. But, the hardware can do it and it used to work from the settings GUI without hackery. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
Something happened to this bug's conversation: the message asking me to upgrade the BIOS has been removed/hidden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
I'm trying the BIOS upgrade as per those instructions. The only applicable option was the flashrom one, which seems to have hosed my BIOS. It's still on now, but I won't be able to boot it again. Kindly mark this bug New again to give me time to recover and retry! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
Okay, I got out of that situation with the help of the flashrom people. My BIOS is now updated. It helped a bit in that I can now define and add my resolution again using xrandr. It won't stay added though: I need to define and add it every time I boot. Otherwise, the resolution is not in the Displays settings dropdown. The dmidecode output is: F7 08/12/2014 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1251257] Re: [SRU] avahi fails in containers
MAAS trunk no longer includes Avahi, so closing this bug there. ** Changed in: maas Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1251257 Title: [SRU] avahi fails in containers Status in MAAS: Fix Released Status in MAAS 1.4 series: Triaged Status in “avahi” package in Ubuntu: Fix Released Status in “avahi” source package in Precise: Fix Released Status in “avahi” source package in Saucy: Fix Released Status in “avahi” source package in Trusty: Fix Released Bug description: installed a brand new maas server on suacy into an lxc container from archive and http://ip/MAAS is not accessible although http://ip is accessible http://ip/MAAS is getting logged to /var/log/apache2/access.log though so request is making it through roaksoax danwest: can you please pastebin apache2's error and access.log danwest http://paste.ubuntu.com/6405411/ danwest http://paste.ubuntu.com/6405412/ roaksoax danwest: I know what it is roaksoax danwest: dbus/avahi roaksoax danwest: try to restart whatever avahi service there is andreas dbus reminds me of https://bugs.launchpad.net/juju-core/+bug/1248283 andreas but that was about the units, not maas itself danwest https://pastebin.canonical.com/100290/ danwest same problem roaksoax danwest: yeah the avahi daemon is failing to start, causing maas to fail roaksoax danwest: maybe restart whatever dbus serviice it is, and then the avahi-daemon matsubara danwest, restart dbus and avahi-daemon, see https://bugs.launchpad.net/maas/+bug/1221059 roaksoax danwest: did avahi-daemon restart corrrectly? danwest nope roaksoax danwest: i guess then an issue with dbus is preventing avahi from working... hence maas failing danwest roaksoax: should not matter but the only thing that is a little unique is that this is in a saucy container roaksoax danwest: ah so then thats the issue... danwest what, the container? roaksoax yeah danwest how so? roaksoax avahi might have issues running in a container danwest hallyn: roaksoax: what should I file that lxc/avahi /maas bug that I hit this morning against? hallyn danwest: i think maas should work around it by unsetting rlimit-nproc hallyn (and/or by running on trusty in a private user ns hallyn smoser: fwiw the problem is that avahi sets its nproc rlimit to exaclty 3, but in a container it's using a uid that is in use on the host - so it exceeds 3 tasks hallyn (i.e. it's reusing uid which is ntp on the host, and ntp is running; or just another avahi) smoser ok... smoser so that doesn't seem like maas's problem to me smoser nor juju's really. hallyn smoser: it is. it needs to pick a unique uid, or configure avahi to ignore the rlimit smoser maas isn't running avahi smoser is it ? hallyn i duno what's actually running it :) it's *for* maas, but it probably is juju smoser what if there was a bug in php, and a user used maas to deploy php. smoser should we fix that in maas ? hallyn you're talking about a bug. i'm talking about a resource conflict hallyn having avahi alwasy run without nprocs, for protection, would be wrong for this. fix is still up for debate on this one... [Impact] Avahi sets the rlimit_nproc to 3, causing avahi to fail running in containers. This This option should not be set in containers at all. This causes avahi-daemon to fail, hence all the applications that use avahi will also fail. In this particular case, MAAS fails because of this. [Test Case] 1. Install a container. 2. Install MAAS 3. Check apache2 log for errors, such as those in [1]. [Regression Potential] Minimal. This has been tested and works as expected. [1]: http://paste.ubuntu.com/6405412/ To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1251257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
