[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]
I also get the same bug on xorg (ubuntu 22.10). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934579 Title: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()] Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Jammy: In Progress Status in nautilus source package in Kinetic: In Progress Bug description: [ Impact ] Nautilus crashes when a bookmarked place is opened from dock icon context menu [ Test case ] 1. Open Nautilus (and ensure you've a location in the sidebar bookmarks) 2. Right-click ubuntu dock nautilus icon 3. Activate one of the bookmarks 4. Nautilus should open that location without crashing. [ Regression potential ] A window may not be raised when opened under wayland. --- After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: BugDistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782188] [NEW] package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-op
Public bug reported: hi, I was updating Ubuntu after long time...years My laptop is more than 10 years old Best regards teo ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-304 (not installed) ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Tue Jul 17 16:33:27 2018 DuplicateSignature: package:nvidia-opencl-icd-304:(not installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 InstallationDate: Installed on 2012-09-01 (2145 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: nvidia-graphics-drivers-304 Title: package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 UpgradeStatus: Upgraded to trusty on 2015-11-11 (978 days ago) ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1782188 Title: package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: hi, I was updating Ubuntu after long time...years My laptop is more than 10 years old Best regards teo ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-304 (not installed) ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Tue Jul 17 16:33:27 2018 DuplicateSignature: package:nvidia-opencl-icd-304:(not installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 InstallationDate: Installed on 2012-09-01 (2145 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: nvidia-graphics-drivers-304 Title: package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 UpgradeStatus: Upgraded to trusty on 2015-11-11 (978 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1782188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1539938] [NEW] Show Desktop keyboard shortcut stops working after taking screenshot
Public bug reported: These steps systematically reproduce the issue: 1. make sure you have some application window on the foreground (e.g. Google Chrome) 2. hit Shift+PrintScreen to take a partial screenshot 3. Select the area for the screenshot by clicking and dragging 4. (IMPORTANT) Use the dropdown selector to choose a location other than the default for choosing the folder to save the screenshot to (if you skip this step you won't reproduce the issue) 5. hit Ok => the screenshot is saved and the Screenshot application is closed 6. Hit Ctrl+Super+D (repeat several times if you like) Expedted behavior: after step 5 focus should be returned to the application that had it before you took the screenshot. And most importantly, whether or not this happens, step 6 should show desktop Observed behavior: after step 5 the application on the foreground has lost focus, and at step 6 Ctrl+Super+D does nothing Note that even if it's the Screenshot application triggering the issue, either Xorg or Unity, or whatever piece of software is responsible for keyboard shortcuts and for showing the Desktop, MUST guarantee that (i) keyboard shortcuts always work and (ii) show desktop always work. So, no matter whether or not the Screenshot application is doing something wrong, the mere fact that a buggy (or malicious) application can prevent Show Desktop from working as expected represents a bug in the piece of software responsible of keyboard shortcuts or of the Show Desktop action (whichever of them is failing). The Screenshot application probably has a bug in that it fails to return focus to the application which had it, but again, this should not prevent the Show Desktop shortcut from working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151016-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jan 30 17:19:40 2016 InstallationDate: Installed on 2013-10-11 (840 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Also affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Show Desktop keyboard shortcut stops working + Show Desktop keyboard shortcut stops working after taking screenshot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1539938 Title: Show Desktop keyboard shortcut stops working after taking screenshot Status in gnome-screenshot package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: These steps systematically reproduce the issue: 1. make sure you have some application window on the foreground (e.g. Google Chrome) 2. hit Shift+PrintScreen to take a partial screenshot 3. Select the area for the screenshot by clicking and dragging 4. (IMPORTANT) Use the dropdown selector to choose a location other than the default for choosing the folder to save the screenshot to (if you skip this step you won't reproduce the issue) 5. hit Ok => the screenshot is saved and the Screenshot application is closed 6. Hit Ctrl+Super+D (repeat several times if you like) Expedted behavior: after step 5 focus should be returned to the application that had it before you took the screenshot. And most importantly, whether or not this happens, step 6 should show desktop Observed behavior: after step 5 the application on the foreground has lost focus, and at step 6 Ctrl+Super+D does nothing Note that even if it's the Screenshot application triggering the issue, either Xorg or Unity, or whatever piece of software is responsible for keyboard shortcuts and for showing the Desktop, MUST guarantee that (i) keyboard shortcuts always work and (ii) show desktop always work. So, no matter whether or not the Screenshot application is doing something wrong, the mere fact that a buggy (or malicious) application can prevent Show Desktop from working as expected represents a bug in the piece of software responsible of keyboard shortcuts or of the Show Desktop action (whichever of them is failing). The Screenshot application probably has a bug in that it fails to return focus to the application which had it, but again, this should not prevent the Show Desktop shortcut from working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151016-0ubuntu1 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1539964] [NEW] file information not shown on rollover on tab if window is maximized
Public bug reported: Steps to reproduce: 1. open several files in Gedit 2. maximize the window 3. move the cursor over each tab Expected behavior: every time you roll over a tab, a black rectangle should appear with white text with information about the file (full path, mime type...) Observed result: for the left-most tabs and while the cursor x position is lower than a certain point, the info box is not shown. Instead, a strange flickering can be observed on the top left corner of the screen (not even in the area where the info box is supposed to be shown); sometimes you may see the info box appear for a fraction of an instant. If you move the cursor to the right of a certain threshold and for subsequent tabs, it works as expected. Just another pathetic regression in f***ing-unusable 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 30 19:09:37 2016 InstallationDate: Installed on 2013-10-11 (841 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1539964 Title: file information not shown on rollover on tab if window is maximized Status in gedit package in Ubuntu: New Bug description: Steps to reproduce: 1. open several files in Gedit 2. maximize the window 3. move the cursor over each tab Expected behavior: every time you roll over a tab, a black rectangle should appear with white text with information about the file (full path, mime type...) Observed result: for the left-most tabs and while the cursor x position is lower than a certain point, the info box is not shown. Instead, a strange flickering can be observed on the top left corner of the screen (not even in the area where the info box is supposed to be shown); sometimes you may see the info box appear for a fraction of an instant. If you move the cursor to the right of a certain threshold and for subsequent tabs, it works as expected. Just another pathetic regression in f***ing-unusable 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 30 19:09:37 2016 InstallationDate: Installed on 2013-10-11 (841 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1539964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1483388] Re: System randomly won't complete boot
*** This bug is a duplicate of bug 1516216 *** https://bugs.launchpad.net/bugs/1516216 Are you sure it's a duplicate? This one happened randomly, the other one is described as 100% systematic. This one results in the "Ubuntu..." screen being displayed forever, the other one results in a black screen. In my case the issue disappeared after I uninstalled/purged the nvidia drivers and (probably weeks later) reinstalled them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1483388 Title: System randomly won't complete boot Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: Since the incomplete/broken "fix" for #1431753 was released, and hence NVidia drivers version 340 were installed AND enabled on my machine (where previously I had 331 installed and disabled) this has started happening: About 50-75% of the times (very rough estimation), when I boot, the boot gets stuck at the purple screen with the "Ubuntu" word with four red dots below. Systematically, when this happens, that screen is preceded by a black screen with a lot of errors, of which I attach a picture (yes, I know, it's unreadable, but it's all I can do). If anybody tells me in which log files those errors can be found, I will be happy to attach them. Normally, that is, when the issue does not happen and the boot is succesful, the black screen preceding the purple screen would only contain one line with an unrelated error that has to do with USB. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150603-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Aug 10 21:15:32 2015 InstallationDate: Installed on 2013-10-11 (668 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1483388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535456] Re: Xorg crashed when attempting to turn on laptop's builtin display
WTF a xorg crasher "medium"?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1535456 Title: Xorg crashed when attempting to turn on laptop's builtin display Status in xorg package in Ubuntu: Confirmed Bug description: Having been hit by bug #1535452 (please see the description), I went back to Display settings and I tried to manually turn on the laptop's builtin display that I had previously turned off (obviously did this while the external monitor was connected). When I clicked on the button to turn on the builtin display, xorg crashed. Since this is a crasher, and potentially leads to disastrous data loss (imagine you are left with no monitor and can't save your work prior to switching off the laptop), I'll set this to confirm because there's no point in waiting for some other random user to confirm it. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:33:36 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535452] Re: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
Importance "medium"??? Do you realize the possible consequences of not being able to turn the screen on? You may suspend with a screen connected, disconnect it, take the laptop away, resume from suspend where you don't have a screen available, and you would be unable to save your work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged Status in xorg package in Ubuntu: Confirmed Bug description: I used to have my display settings so that only one external monitor would be used when available, and the laptop's builtin monitor would be disabled. When plugging and unplugging the external monitor (whether in the VGA or HDMI port), monitors would switch automatically, as is obviously expected. After upgrading from 15.04 to 15.10, as per bug #1535436, these settings were lost, and after reboot, the two monitors were both enabled in extended desktop mode (or whatever it's called). So I went to Settings -> Displays (while I had an HDMI monitor connected), and turned off the builtin display. That worked, but when unplugging the HDMI monitor, the builtin one remains turned off despite being the only available monitor. No matter how many times I plug and unplug the external HDMI monitor, the builtin one never turns on (the external one does work). This is a HUGE regression as it may leave you without screen. By plugging a monitor via the VGA port, it works as expected. I'm testing with the same monitors and cables (and computer) as I was using in 15.04 when everything worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:18:48 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change.
[Desktop-packages] [Bug 1535439] [NEW] ubuntu-bug should check for internet connection before it starts doing anything
Public bug reported: Steps to reproduce: 1. Disconnect from the internet 2. from a terminal, run "ubuntu-bug some-package" Expected result: should immediately warn me that I am not connected to the internet. Observed result: wastes my time collecting bug data and, in some cases depending on the package, prompting for the sudo password. Only after that, when it tries to connect to send the bug report, does it realize there's no internet connection and it issues an error saying so. Also note that there's no "Retry" button, which makes the issue worse. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 21:33:57 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1535439 Title: ubuntu-bug should check for internet connection before it starts doing anything Status in apport package in Ubuntu: New Bug description: Steps to reproduce: 1. Disconnect from the internet 2. from a terminal, run "ubuntu-bug some-package" Expected result: should immediately warn me that I am not connected to the internet. Observed result: wastes my time collecting bug data and, in some cases depending on the package, prompting for the sudo password. Only after that, when it tries to connect to send the bug report, does it realize there's no internet connection and it issues an error saying so. Also note that there's no "Retry" button, which makes the issue worse. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 21:33:57 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1535439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535452] [NEW] [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
Public bug reported: I used to have my display settings so that only one external monitor would be used when available, and the laptop's builtin monitor would be disabled. When plugging and unplugging the external monitor (whether in the VGA or HDMI port), monitors would switch automatically, as is obviously expected. After upgrading from 15.04 to 15.10, as per bug #1535436, these settings were lost, and after reboot, the two monitors were both enabled in extended desktop mode (or whatever it's called). So I went to Settings -> Displays (while I had an HDMI monitor connected), and turned off the builtin display. That worked, but when unplugging the HDMI monitor, the builtin one remains turned off despite being the only available monitor. No matter how many times I plug and unplug the external HDMI monitor, the builtin one never turns on (the external one does work). This is a HUGE regression as it may leave you without screen. By plugging a monitor via the VGA port, it works as expected. I'm testing with the same monitors and cables (and computer) as I was using in 15.04 when everything worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:18:48 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged Status in xorg package in Ubuntu: New Bug description: I used to have my display settings so that only one external monitor would be used when available, and the laptop's
[Desktop-packages] [Bug 1535456] [NEW] Xorg crashed when attempting to turn on laptop's builtin display
Public bug reported: Having been hit by bug #1535452 (please see the description), I went back to Display settings and I tried to manually turn on the laptop's builtin display that I had previously turned off (obviously did this while the external monitor was connected). When I clicked on the button to turn on the builtin display, xorg crashed. Since this is a crasher, and potentially leads to disastrous data loss (imagine you are left with no monitor and can't save your work prior to switching off the laptop), I'll set this to confirm because there's no point in waiting for some other random user to confirm it. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:33:36 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug ubuntu wily ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1535456 Title: Xorg crashed when attempting to turn on laptop's builtin display Status in xorg package in Ubuntu: Confirmed Bug description: Having been hit by bug #1535452 (please see the description), I went back to Display settings and I tried to manually turn on the laptop's builtin display that I had previously turned off (obviously did this while the external monitor was connected). When I clicked on the button to turn on the builtin display, xorg crashed. Since this is a crasher, and potentially leads to disastrous data loss (imagine you are left with no monitor and can't save your work prior to switching off the laptop), I'll set this to confirm because there's no point in waiting for some other
[Desktop-packages] [Bug 1535461] [NEW] [15.10 REGRESSION] Find has become sensitive to differences in accents
Public bug reported: Steps to reproduce: - write (or paste, or load) a text containing the string "maría" - hit Ctrl+F - in the search box, type "maria" Expected: should find the string "maría" in the text, because í and i only differ by an accent. This is the way it used to work, and it is the way every decent editor works Observed: doesn't find the matching string unless you type it exactly with the same accents. I already reported this upstream at https://bugzilla.gnome.org/show_bug.cgi?id=760810 However, they'll probably tell me that I'm using a too old version. - Please check whether it is already fixed in a later version upstream - if so, release the fixed version in Ubuntu - if not, either patch it or immediately roll back to the version without the issue. This makes ctrl+F unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:54:37 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1535461 Title: [15.10 REGRESSION] Find has become sensitive to differences in accents Status in gedit package in Ubuntu: New Bug description: Steps to reproduce: - write (or paste, or load) a text containing the string "maría" - hit Ctrl+F - in the search box, type "maria" Expected: should find the string "maría" in the text, because í and i only differ by an accent. This is the way it used to work, and it is the way every decent editor works Observed: doesn't find the matching string unless you type it exactly with the same accents. I already reported this upstream at https://bugzilla.gnome.org/show_bug.cgi?id=760810 However, they'll probably tell me that I'm using a too old version. - Please check whether it is already fixed in a later version upstream - if so, release the fixed version in Ubuntu - if not, either patch it or immediately roll back to the version without the issue. This makes ctrl+F unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:54:37 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1535461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526082] [NEW] Area of screenshot remains highlighted until application closed
Public bug reported: Steps to reproduce: - hit shift+PrintScreen - Drag and drop to select a rectangular area of the screen to take a screenshot of - don't close the Gnome Screenshot dialog. Minimize it if you want Observed issue: the rectangular area that has been captured remains slightly highlighted (i.e. brighter) as long as the Gnome Screenshot application's dialog is open. No matter what window is on the foreground (or even fullscreen for that matter), you'll keep noticing the slightly brighter rectangle. See attachment screenshot: you can see the rectangle approximately at the center of the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-screenshot 3.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 14 23:20:01 2015 InstallationDate: Installed on 2013-10-11 (794 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to vivid on 2015-08-15 (121 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Screenshot from 2015-12-14 23:20:30.png" https://bugs.launchpad.net/bugs/1526082/+attachment/4534777/+files/Screenshot%20from%202015-12-14%2023%3A20%3A30.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1526082 Title: Area of screenshot remains highlighted until application closed Status in gnome-screenshot package in Ubuntu: New Bug description: Steps to reproduce: - hit shift+PrintScreen - Drag and drop to select a rectangular area of the screen to take a screenshot of - don't close the Gnome Screenshot dialog. Minimize it if you want Observed issue: the rectangular area that has been captured remains slightly highlighted (i.e. brighter) as long as the Gnome Screenshot application's dialog is open. No matter what window is on the foreground (or even fullscreen for that matter), you'll keep noticing the slightly brighter rectangle. See attachment screenshot: you can see the rectangle approximately at the center of the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-screenshot 3.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 14 23:20:01 2015 InstallationDate: Installed on 2013-10-11 (794 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to vivid on 2015-08-15 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1526082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445954] [NEW] Sorting of folders by modification date is meaningless
Public bug reported: Steps to reproduce - open a folder that contains subfolders (and optionally files), of which at least some contains in turn at least a couple of levels of subfolders with files inside it - select list view - click on the modified column to sort items by modification date Expected: * both the files and folders should be ordered by modification date. For folders, modification date should be the date of last modification of the item most recently modified inside the folder, RECURSIVELY. That is, for example, the folder containing the file most recently modified, at ANY level of its subtree, should be considered the most recently modified folder Observed: * Files stright inside the current folder are ordered correctly, but folders are ordered in a seemingly random manner. Often, the folder that you'd expect to be on the top of the list (in reverse chronological order) is pretty close, but many times it's not, and the overall sorting certainly doesn't satisfy the expected criteria. I suspect the modification dates of items inside the folders are taken into account but not recursively. If that is the case, it's a meaningless and hence wrong criteria. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 18:22:28 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (554 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (329 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445954 Title: Sorting of folders by modification date is meaningless Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce - open a folder that contains subfolders (and optionally files), of which at least some contains in turn at least a couple of levels of subfolders with files inside it - select list view - click on the modified column to sort items by modification date Expected: * both the files and folders should be ordered by modification date. For folders, modification date should be the date of last modification of the item most recently modified inside the folder, RECURSIVELY. That is, for example, the folder containing the file most recently modified, at ANY level of its subtree, should be considered the most recently modified folder Observed: * Files stright inside the current folder are ordered correctly, but folders are ordered in a seemingly random manner. Often, the folder that you'd expect to be on the top of the list (in reverse chronological order) is pretty close, but many times it's not, and the overall sorting certainly doesn't satisfy the expected criteria. I suspect the modification dates of items inside the folders are taken into account but not recursively. If that is the case, it's a meaningless and hence wrong criteria. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 18:22:28 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (554 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1445954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 907411] Re: printer tray icon doesn't appear (any more) when printing
The bug is still present in 14.04. @3 instead of just marking it as invalid you could have changed the package to the correct one. This way perhaps it wouldn't have gone unfixed for two years ** Also affects: indicator-printers Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/907411 Title: printer tray icon doesn't appear (any more) when printing Status in Print Indicator: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: I'm not sure where the bug is but it's almost certainly somehow related to the change of gnome in favor to unity. In ubuntu 10.10 and earlier, when I printed any document (no matter from what application), a tray icon of a printer appeared on the upper-right size of the . By clicking on it I could see the printing queue, the status of the jobs, I could manage printing jobs etc. Now in ubuntu 11.10 that icon does not appear any more. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.24.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Wed Dec 21 17:10:33 2011 DistUpgraded: Log time: 2011-12-07 19:34:40.350850 DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: nVidia Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15d2] InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) JockeyStatus: xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) pkg:sl-modem-daemon - Software modem (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-12-07 (13 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-printers/+bug/907411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
I like the official Nvidia drivers better regardless because they are built specifically for and by Nvidia for Nvidia products Except they don't support Optimus boards on Linux, so they are just not an option for those of us who have one. https://www.youtube.com/watch?v=iYWzMvlj2RQ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: New Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430578] [NEW] Drag'n'drop a file onto a zip file gives nonsense error message
Public bug reported: Steps to reproduce: - pick or create a zip file (e.g. select some files and compress them) - drag another file and drop it over the zip file Expected: should add the dragged file to the contents of the compressed file. Observed: shows a popup with this error message that doesn't even make sense: An error occurred while adding files to the archive. You can't add an archive to itself ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.6 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 23:28:08 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (515 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (290 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1430578 Title: Drag'n'drop a file onto a zip file gives nonsense error message Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: - pick or create a zip file (e.g. select some files and compress them) - drag another file and drop it over the zip file Expected: should add the dragged file to the contents of the compressed file. Observed: shows a popup with this error message that doesn't even make sense: An error occurred while adding files to the archive. You can't add an archive to itself ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.6 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 23:28:08 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (515 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (290 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1430578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390892] [NEW] Windows stacking (foreground/background) gets completely screwed up
Public bug reported: I have reported several issues (none of which got the slightest attention, by the way) but I now realize they ALWAYS happen all together, so they are most surely just consequences of one same issue. At random times it happens that the front/back or in-front/behind relation between windows becomes badly screwed up in several ways: 1 - windows are on top of Launcher while Launcher should always be the topmost 1b - even the context menu of Launcher icons that appear by right-clicking on them turns out to be behind maximized windows (or non maximized windows) 2 - the window-switching selector that shows up when you hit Alt+Tab is on the background (hence invisible most of the time unless you minimize all windows or show desktop) 3 - Fullscreen content from any browser, such as for example fullscreen of video or flash content, goes fullscreen on the background instead of on the foreground; even clicking on it (if some portion of it is visible behind the foremost windows) doesn't bring to the foreground, the only workaround (which was difficult to figure out) being: ctrl+super+d and then click on the browser launcher icon. Sometimes (3) is slightly different, in that the fullscreen content stays on top of everything except Launcher. All of this is very annoying and this issue has been around for a very long time, certainly more than a year (i.e. two releases) if not forever. This cripples the usability of the whole system to the point that one is forced to restart, which is painful. This should be high priority. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Nov 9 12:46:03 2014 InstallationDate: Installed on 2013-10-11 (393 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (168 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1390892 Title: Windows stacking (foreground/background) gets completely screwed up Status in “unity” package in Ubuntu: New Bug description: I have reported several issues (none of which got the slightest attention, by the way) but I now realize they ALWAYS happen all together, so they are most surely just consequences of one same issue. At random times it happens that the front/back or in-front/behind relation between windows becomes badly screwed up in several ways: 1 - windows are on top of Launcher while Launcher should always be the topmost 1b - even the context menu of Launcher icons that appear by right-clicking on them turns out to be behind maximized windows (or non maximized windows) 2 - the window-switching selector that shows up when you hit Alt+Tab is on the background (hence invisible most of the time unless you minimize all windows or show desktop) 3 - Fullscreen content from any browser, such as for example fullscreen of video or flash content, goes fullscreen on the background instead of on the foreground; even clicking on it (if some portion of it is visible behind the foremost windows) doesn't bring to the foreground, the only workaround (which was difficult to figure out) being: ctrl+super+d and then click on the browser launcher icon. Sometimes (3) is slightly different, in that the fullscreen content stays on top of everything except Launcher. All of this is very annoying and this issue has been around for a very long time, certainly more than a year (i.e. two releases) if not forever. This cripples the usability of the whole system to the point that one is forced to restart, which is painful. This should be high priority. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Nov 9 12:46:03 2014 InstallationDate: Installed on 2013-10-11 (393 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (168 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1390892/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1380320] [NEW] [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
Public bug reported: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag- and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - [REGRESSION] touchpad behavior broken: left button click not caught if finger is on touchpad + [REGRESSION] touchpad behavior broken: left button click delayed if finger is on touchpad ** Summary changed: - [REGRESSION] touchpad behavior broken: left button click delayed if finger is on touchpad + [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad Status in “unity” package in Ubuntu: New Bug description: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result:
[Desktop-packages] [Bug 1301083] Re: Drag and Drop File Auto Opens Folders
How can this even be importance low? Doesn't anybody realize the huge SECURITY RISK this bug involves? You drag a file onto a folder, for just a fraction of a second more than the time it takes for the folder to auto-open. Then you drop it, but when you do, the folder has just opened and you have accidentally dropped the file onto a subfolder within the folder. Unless you double check, you may not realize where you have moved the file and you may loose it forever. You may have moved it (without realizing) into a subfolder that you will later delete, without knowing it contains a file that you never intended to move into it. This is DISASTROUS. We already know that Nautilus development has degenerated into complete dementia, and that until it gets repleced with something else in Ubuntu, it constantly needs patching to revert regressions like this one (which are made on purpose, because of demential design). But an issue like this should be considered high importance, if not critical, as it can lead to DATA LOSS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1301083 Title: Drag and Drop File Auto Opens Folders Status in “nautilus” package in Ubuntu: Confirmed Bug description: When dragging and dropping a file, if the mouse hovers over a folder for a split second, the folder opens. This behaviour is quite jarring. Whether or not you intended to drop into that folder, you may not have intended to open that folder. The hover time can't be set. And the behaviour can't be disabled. It's a very significant usability issue for Ubuntu 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Apr 1 20:21:16 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1144x859+1331+77' b'org.gnome.nautilus.window-state' b'sidebar-width' b'140' InstallationDate: Installed on 2014-03-18 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no username) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1301083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
It's no surprise that Ubuntu is still what it is as long as bug reports get managed this ridiculous way. This issue is intermittent, happens randomly, and is a regression (i.e. has started happening at a certain update, never happened before). Ignoring it just because the reporter doesn't have the latest bios is ridiculous. This is most probably not even in Linux; I chose linux just because I have no idea what package it belongs to, and there's no generic ubuntu package to report bugs against. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working Status in “linux” package in Ubuntu: Expired Status in “unity” package in Ubuntu: New Bug description: All of a sudden, the volume keys from the keyboard have stopped working. The volume control on the top right corner of the screen does work if used with the mouse. I have both an external usb keyboard with dedicated volume + and - keys, and the builtin laptop keyboard where the volume +/-keys are the combination of the Fn key plus the up/down arrows. All these used to work up to a few minutes ago. Now none of them works. I think they stopped working with the last reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2303 F pulseaudio /dev/snd/pcmC0D0p: teo2303 F...m pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 23:13:35 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378046] [NEW] Can't switch between maximized windows of the same program sometimes
Public bug reported: Note: this is intermittent and I don't know of a way to systematically reproduce this, but I've observed it dozens of times. - I have two windows of the same program both maximized - I click on the program's icon on the Launcher (one icon with two tips indicating there are two windows open) = the downscaled previews of the two windows are shown one on top of the other as expected - I click on one of them Expected result: the one I clicked should get focus and be brought to front (maximized, as it was) Observed result: whichever I pick, only one of them, systematically always the same one, will get chosen. That is, if I click on window A, it's window A, if I click on window B, it's window A allthesame. Additionally, the title bar on the top of the screen is not displayed. I can click on the foreground window (which is not the expected one) and interact with it. If I click on the top of the screen, where the window title is not shown, then the correct window will be brought to front (not sure this _always_ work, but I have observed it sometimes). One thing that fixes the issue is to de-maximize both windows and then remaximize them. I've only observed this on maximized windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 20:00:03 2014 InstallationDate: Installed on 2013-10-11 (360 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (135 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Can't switch between maximized windows at random times + Can't switch between maximized windows of the same program sometimes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1378046 Title: Can't switch between maximized windows of the same program sometimes Status in “unity” package in Ubuntu: New Bug description: Note: this is intermittent and I don't know of a way to systematically reproduce this, but I've observed it dozens of times. - I have two windows of the same program both maximized - I click on the program's icon on the Launcher (one icon with two tips indicating there are two windows open) = the downscaled previews of the two windows are shown one on top of the other as expected - I click on one of them Expected result: the one I clicked should get focus and be brought to front (maximized, as it was) Observed result: whichever I pick, only one of them, systematically always the same one, will get chosen. That is, if I click on window A, it's window A, if I click on window B, it's window A allthesame. Additionally, the title bar on the top of the screen is not displayed. I can click on the foreground window (which is not the expected one) and interact with it. If I click on the top of the screen, where the window title is not shown, then the correct window will be brought to front (not sure this _always_ work, but I have observed it sometimes). One thing that fixes the issue is to de-maximize both windows and then remaximize them. I've only observed this on maximized windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 20:00:03 2014 InstallationDate: Installed on 2013-10-11 (360 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
As usual, importance (after months undecided) gets wrongly assigned https://wiki.ubuntu.com/Bugs/Bug%20importances If those criteria are not up to date, please update that page. Otherwise try to respect them. This issue meets two of the criteria of High: - Has a severe impact on a small portion of Ubuntu users (estimated) [not being able to copy file among common devices is definitely severe impact] - Renders essential features or functionality of the application or dependencies broken or ineffective [copying files is an essential feature] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gnome-vfs-obexftp” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353620] [NEW] Laptop Screen systematically freezes every few minutes when external screen disconnected; Ctlr+Alt+F1,Ctrl+Alt+F7 fixes the issue. Then system unrecoverably free
Public bug reported: I've started observing this bug since i've started using NVidia's additional drivers (yesterday). Before that I was using nouveau, which happened to use the builtin Intel GPU and not the NVidia card. I have an external monitor which I usually connect to the laptop. I have it configured so it's the only screen when it's connected. When I unplug it, automatically the laptop's builtin screen turns on, and when I plug it, the laptop's builtin screen turns off. This has worked just fine until yesterday. Then I switched to NVidia's proprietary drivers. Now the problem, 100% systematically reproducible, is as follows: - I disconnect the external screen (and external keyboard and mouse), move my laptop and start using it alone. At the beginning everything works fine, then: - from time to time (every few minutes), the system seems to freeze: - mouse cursor doesn't move. Nothing responds to touchpad movements or clicks - nothing apparently responds to keystrokes, such as alt+tab to switch window, or Ctrl+Alt+T to open a terminal. I'm not sure this ever happened while I was typing and had a focused window where to type, so I cannot tell for sure it wouldn't respond to typing - no signs of abnormal CPU consumption, though, nor of disk activity - hitting ctlr+Alt+F1 does work and immediately brings the virtual console - hitting ctrl+Alt+F7 brings the graphics screen again and it works, that is, it fixes the issue, reesstablishing normal functioning - unless it happens again. The first time I observed it (this is the second), this also happened: - then I plug in the external monitor again. It turns on, shows the screen output as expected; the builtin screen turns off, everything looks normal - except the system is frozen again - and this time not even Ctrl+Alt+F1 work. Completely frozen. No way out except a hard reboot - unplugging the external monitor doesn't fix the issue, either ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Wed Aug 6 19:51:09 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (299 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to trusty on 2014-05-24 (74 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1353003] [NEW] windows of an application spawned from another are not given focus when they should
Public bug reported: I don't know whether this is supposed to be a new brilliantly designed feature which is working as [wrongly] intended or if it is just a regression, but it is certainly annoying. When an application opens up a window of another application, what used to happen (and the correct and expected behavior) was that that window was given focus. Now it is not. It is just highlighted in a barely perceptible way in the Launcher. Examples: - in Thunderbird, click a link in an email = this opens the link in a new tab in the default Browser (Google Chrome in my case). Google Chrome should be given focus but it isn't. Its icon in the Launcher just is highlighted - In Google Chrome, download a file. Then, when it appears on the bottom, click the down arrow next to it and choose the show in folder option. This opens a new Nautilus windows. This window isn't given focus as it should, and again is only slightly highlighted in the Launcher. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Aug 5 18:37:59 2014 InstallationDate: Installed on 2013-10-11 (297 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (72 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1353003 Title: windows of an application spawned from another are not given focus when they should Status in “unity” package in Ubuntu: New Bug description: I don't know whether this is supposed to be a new brilliantly designed feature which is working as [wrongly] intended or if it is just a regression, but it is certainly annoying. When an application opens up a window of another application, what used to happen (and the correct and expected behavior) was that that window was given focus. Now it is not. It is just highlighted in a barely perceptible way in the Launcher. Examples: - in Thunderbird, click a link in an email = this opens the link in a new tab in the default Browser (Google Chrome in my case). Google Chrome should be given focus but it isn't. Its icon in the Launcher just is highlighted - In Google Chrome, download a file. Then, when it appears on the bottom, click the down arrow next to it and choose the show in folder option. This opens a new Nautilus windows. This window isn't given focus as it should, and again is only slightly highlighted in the Launcher. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Aug 5 18:37:59 2014 InstallationDate: Installed on 2013-10-11 (297 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1353003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353065] [NEW] NVidia GeForce 710M is not properly detected
Public bug reported: I installed Ubuntu 13.04 on a new laptop which has an NVidia GeForce 710M and later upgraded it to Ubuntu 13.10 and finally 14.04. After almost a year, I'm astonished to find out that my NVidia card is not even being used. The Intel Graphics card built into the motherboard is being used instead. The Additional Drivers tab under Software Updates shows what you can see in the attached screenshot: NVIDIA Corporation: GeForce 710M This device is using an alternative driver and the selected item in the list is Using X.Org X server - Nouveau display driver from xserver-xorg-video-nouveau (open source) I knew that means I'm not using the proprietary NVidia drivers, but isn't nouveau supposed to support NVidia? Here's the output of glxinfo |grep OpenGL: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.3 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.1.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: Is there a workaround? Also, I wonder whether it's safe to select NVidia's proprietary drivers in the Additional Drivers tab. I ask because once upon a time I tried to install them using sudo apt-get install nvidia-something and it screwed up Xorg completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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 Aug 5 21:22:53 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.1 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: Mon Aug 4 18:06:36 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is
[Desktop-packages] [Bug 1353065] Re: NVidia GeForce 710M is not properly detected
** Attachment added: Screenshot from 2014-08-05 21:25:52.png https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1353065/+attachment/4170622/+files/Screenshot%20from%202014-08-05%2021%3A25%3A52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1353065 Title: NVidia GeForce 710M is not properly detected Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: I installed Ubuntu 13.04 on a new laptop which has an NVidia GeForce 710M and later upgraded it to Ubuntu 13.10 and finally 14.04. After almost a year, I'm astonished to find out that my NVidia card is not even being used. The Intel Graphics card built into the motherboard is being used instead. The Additional Drivers tab under Software Updates shows what you can see in the attached screenshot: NVIDIA Corporation: GeForce 710M This device is using an alternative driver and the selected item in the list is Using X.Org X server - Nouveau display driver from xserver-xorg-video-nouveau (open source) I knew that means I'm not using the proprietary NVidia drivers, but isn't nouveau supposed to support NVidia? Here's the output of glxinfo |grep OpenGL: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.3 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.1.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: Is there a workaround? Also, I wonder whether it's safe to select NVidia's proprietary drivers in the Additional Drivers tab. I ask because once upon a time I tried to install them using sudo apt-get install nvidia-something and it screwed up Xorg completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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 Aug 5 21:22:53 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (298 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
My volume up/down keys were working fine and they have stopped working right NOW. Was there some recent update that attempted to fix this bug and instead screwed things up further? Or am I experiencing a different (though apparently identical) issue? This did NOT work for me: gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down Is there any other workaround? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
Is this the same as https://bugs.launchpad.net/ubuntu/+source/gnome- settings-daemon/+bug/1248368 or not? My volume keys were working until a few MINUTES AGO (last reboot). This didn't fix them: gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down Any other workaround? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069507] Re: (REGRESSION) printable area is not taken into account correctly
Is this so difficult to fix (or to even decide the importance of)? It's been almost 2 years and this makes something as basic as printing a hell of the problem AND IT USED TO WORK BEFORE the regression. A little hint for the importance: * Renders essential features or functionality of the application or dependencies broken or ineffective Perhaps the impact of this issue is being underestimated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1069507 Title: (REGRESSION) printable area is not taken into account correctly Status in “cups” package in Ubuntu: Confirmed Status in “hplip” package in Ubuntu: Confirmed Bug description: NOTE: I have no idea which package this bug is in, I chose cups only because it's the only one I know related to printing. Whenever I print anything, e.g. a pdf file from the Document viewer or a web page from Google Chrome or a document of any kind from OpenOffice (they all share the same system dialog for printing options), the top of the document is always printed outside of the printable area, and hence lost. I use a HP Deskjet 940c and this is the printer that the system is configured to use (e.g. it is listed as Deskjet 940c when I choose it for printing). Even if I choose shrink to printable area or fit to printable area, the actual printing always exceeds the top border of the printable area. So either the software doesn't take into account the printable area correctly, or the printable area information for this particular printer is wrong. This is a REGRESSION in some recent or not-so-recent upgrade, as in the past I had used this very same printer on this same system and it used to print properly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Sun Oct 21 21:21:59 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) Lpstat: device for DESKJET-940C: hp:/usb/DeskJet_940C?serial=MY17O671S5BH device for DESKJET-970C: usb://HP/DESKJET%20970C?serial=MY17O671S5BH device for HP-Photosmart-C6200-series: hp:/net/Photosmart_C6200_series?zc=HP586D2D device for Photosmart-C6200-series: hp:/usb/Photosmart_C6200_series?serial=MY7B6H51S40506 MachineType: ASUSTeK Computer Inc. M51Sn Papersize: letter PpdFiles: HP-Photosmart-C6200-series: HP Photosmart c6200 Series, hpcups 3.12.2 Photosmart-C6200-series: HP Photosmart c6200 Series, hpcups 3.12.2 DESKJET-970C: HP Deskjet 970c, hpcups 3.11.7 DESKJET-940C: HP Deskjet 940c, hpcups 3.12.2 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2012-05-17 (157 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1069507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1348644] [NEW] Network icon gone from notification area
Public bug reported: After reboot, the usual network icon is not present in the notification area. See screenshot (if Launchpad will let me attach it) The network works and it has automatically connected to my wifi router, but the icon still does not appear. Disabling and reenabling wifi via hardware does not fix the issue. I tried to report this with ubuntu-bug nm-applet (rather than network- manager) but it tells me that the package is not installed, which seems ridiculous. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 15:22:26 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (286 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-05-24 (61 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-05-20T16:34:16.034908 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 43:29:1A:07:53:91 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1348644 Title: Network icon gone from notification area Status in “network-manager” package in Ubuntu: New Bug description: After reboot, the usual network icon is not present in the notification area. See screenshot (if Launchpad will let me attach it) The network works and it has automatically connected to my wifi router, but the icon still does not appear. Disabling and reenabling wifi via hardware does not fix the issue. I tried to report this with ubuntu-bug nm-applet (rather than network-manager) but it tells me that the package is not installed, which seems ridiculous. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 25 15:22:26 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (286 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-05-24 (61 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-05-20T16:34:16.034908 nmcli-dev: DEVICE TYPE STATE DBUS-PATH 43:29:1A:07:53:91 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1348644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever
This shouldn't have been marked as incomplete. All the tests #7 asks to do he can do himself unless he has tried and been unable to reproduce the issue. If #7 provided enough instructions for the affected users (i.e. us) to produce the needed information, we could do that, but I don't know what a gcore/bt dump is and I'm not going to read man pages just to figure out what we're being asked to do. Please provide commands to copy and paste. Same for check top o/p. Now, to answer the only question that I can answer, i.e. second question in #7, yes, all local in my case. ** Changed in: nautilus (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1133477 Title: cut-n-paste move files got stuck forever Status in “nautilus” package in Ubuntu: Confirmed Bug description: With Nautilus, I navigated to a folder that contained about 2,000 gif files. I selected all of them I cut with Ctrl+X I navigated to another folder I pasted with Ctrl+V = A popup window appeared saying Preparing to move N files, and it got stuck there forever. Nautilus stopped responding. I waited half an hour, then I had to kill it. Actually some of the files were moved. Which is the worst thing that could happen. I tried again with the remaining files and it happened again!! It's systematic!! I suspect it has to do with displaying the previews of a big number of files. Nautilus becomes completely unmanageable whenever you open folders with lots of files. Maximum priority should be given to the UI and actual operations; displaying of the previews should be done in the background and should never, ever slow down user operations the slightest bit. Seems pretty obvious. Also note that 2000 is not even that much. Actually it's very few files. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Tue Feb 26 18:23:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1312x713+64+71' b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationDate: Installed on 2010-06-23 (979 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692668] Re: nonsense behaviour when dragging the + sign next to a folder
Yeah, looks like it's fixed. (btw I was astonished to see that tree view didn't work any more. It wouldn't have occurred to me to look for a setting, I thought they had just eliminated tree view. I wonder why they do this sort of things. So counterintuitive. It would be better to list them as 3 separate modes: icons, list, tree ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/692668 Title: nonsense behaviour when dragging the + sign next to a folder Status in “nautilus” package in Ubuntu: Incomplete Bug description: Binary package hint: nautilus Steps to reproduce: 1 Open Nautilus and put it in list view. 2 Suppose you have 3 folders: A, B and C 3 Click once on folder A to _select_ it 4 Click on the [+] sign on the left of folder B (as if you wanted to expand it) and don't release the mouse button 5 Drag it somewhere, for example into folder C, and drop it. Expected result: NOTHING should happen. Dragging the [+] sign makes no sense. It shouldn't even give you any visual feedback that you are doing something, like when you try to drag a button. An other, less correct but acceptable behaviour, would be that you would be dragging folder B, the one whose [+] sign you have clicked and dragged. Observed result: folder A, not B (not the one whose [+] sign you have dragged, but the one that was previously selected when you clicked on the completely unrelated [+] sign) is moved into where you drop, in this case into C. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11 Uname: Linux 2.6.32-26-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Dec 20 18:47:05 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/692668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device
How can this have importance low?? Btw, for me turning on USB debugging does NOT fix the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device Status in “gvfs” package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1338265] [NEW] crash report window stops responding
Public bug reported: The usual crash report window appeared. (in this case related to VirtualBox) After clicking on the Details button, almost everything in the window stop responding: - the Continue button wouldn't work - the scroll bars wouldn't move - clicking anywhere within the details box wouldn't select/unfold anything I'm not sure I tried the cancel button. The window's very close button (the X), however, did work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashReports: 640:0:110:10698:2014-07-06 18:58:13.477624177 +0200:2014-07-06 18:58:14.477624177 +0200:/var/crash/virtualbox-4.3.0.crash CurrentDesktop: Unity Date: Sun Jul 6 18:59:23 2014 InstallationDate: Installed on 2013-10-11 (267 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-24 (42 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot from 2014-07-06 18:59:14.png https://bugs.launchpad.net/bugs/1338265/+attachment/4146687/+files/Screenshot%20from%202014-07-06%2018%3A59%3A14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1338265 Title: crash report window stops responding Status in “apport” package in Ubuntu: New Bug description: The usual crash report window appeared. (in this case related to VirtualBox) After clicking on the Details button, almost everything in the window stop responding: - the Continue button wouldn't work - the scroll bars wouldn't move - clicking anywhere within the details box wouldn't select/unfold anything I'm not sure I tried the cancel button. The window's very close button (the X), however, did work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashReports: 640:0:110:10698:2014-07-06 18:58:13.477624177 +0200:2014-07-06 18:58:14.477624177 +0200:/var/crash/virtualbox-4.3.0.crash CurrentDesktop: Unity Date: Sun Jul 6 18:59:23 2014 InstallationDate: Installed on 2013-10-11 (267 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-24 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1338265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335410] [NEW] Crash Reporter offers to report a problem, only to tell me that the problem cannot be reported because third party
Public bug reported: Something crashes. Observed behavior: A window pops up spontaneusly telling me that a problem was detected and offers me the option to Report problem (see first screenshot). If I do click Report problem, after wasting a few seconds collecting information for the report to be sent, a second window appears that says the problem cannot be reported because it belongs to a third-party package (whose name was already visible in the first popup). Expected: If you cannot report the problem, then don't offer me the option to do so. Only an informative message should appear saying that a program has crashed, which program, and with the option to show details, but there shouldn't exist a send report option whose only reult is to make the user waste time trying something that it known in advance to be impossible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashReports: 640:1000:110:26779720:2014-06-20 23:01:35.185835261 +0200:2014-06-20 23:01:57.545835840 +0200:/var/crash/_opt_google_chrome_chrome.1000.crash 640:0:110:19789193:2014-06-20 23:01:45.137835519 +0200:2014-06-20 23:01:45.141835519 +0200:/var/crash/_usr_bin_Xorg.0.crash 640:0:110:2507:2014-06-27 17:03:51.846314668 +0200:2014-06-27 17:03:52.846314668 +0200:/var/crash/virtualbox-4.3.0.crash 600:106:110:0:2014-06-27 17:02:52.282317168 +0200:2014-06-27 17:02:52.282317168 +0200:/var/crash/virtualbox-4.3.0.uploaded 644:0:110:0:2014-06-27 17:02:50.146317258 +0200:2014-06-27 17:02:50.146317258 +0200:/var/crash/virtualbox-4.3.0.upload CurrentDesktop: Unity Date: Sat Jun 28 13:13:54 2014 InstallationDate: Installed on 2013-10-11 (259 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-24 (34 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot from 2014-06-27 17:02:46.png https://bugs.launchpad.net/bugs/1335410/+attachment/4141257/+files/Screenshot%20from%202014-06-27%2017%3A02%3A46.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1335410 Title: Crash Reporter offers to report a problem, only to tell me that the problem cannot be reported because third party Status in “apport” package in Ubuntu: New Bug description: Something crashes. Observed behavior: A window pops up spontaneusly telling me that a problem was detected and offers me the option to Report problem (see first screenshot). If I do click Report problem, after wasting a few seconds collecting information for the report to be sent, a second window appears that says the problem cannot be reported because it belongs to a third-party package (whose name was already visible in the first popup). Expected: If you cannot report the problem, then don't offer me the option to do so. Only an informative message should appear saying that a program has crashed, which program, and with the option to show details, but there shouldn't exist a send report option whose only reult is to make the user waste time trying something that it known in advance to be impossible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashReports: 640:1000:110:26779720:2014-06-20 23:01:35.185835261 +0200:2014-06-20 23:01:57.545835840 +0200:/var/crash/_opt_google_chrome_chrome.1000.crash 640:0:110:19789193:2014-06-20 23:01:45.137835519 +0200:2014-06-20 23:01:45.141835519 +0200:/var/crash/_usr_bin_Xorg.0.crash 640:0:110:2507:2014-06-27 17:03:51.846314668 +0200:2014-06-27 17:03:52.846314668 +0200:/var/crash/virtualbox-4.3.0.crash 600:106:110:0:2014-06-27 17:02:52.282317168 +0200:2014-06-27 17:02:52.282317168 +0200:/var/crash/virtualbox-4.3.0.uploaded 644:0:110:0:2014-06-27 17:02:50.146317258 +0200:2014-06-27 17:02:50.146317258 +0200:/var/crash/virtualbox-4.3.0.upload CurrentDesktop: Unity Date: Sat Jun 28 13:13:54 2014 InstallationDate: Installed on 2013-10-11 (259 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-24 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1335410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1332712] [NEW] Random xorg crash
Public bug reported: I was watching a Youtube video (actually a youtube Ad just before the video). I had just put it in fullscreen. The whole system stopped responding (couldn't exit fullscreen, couldn't switch window; aound continued to play, or maybe looped, but the video's image freezed), then cpu usage went high (can tell because of the noise of the fan), then the mouse cursor stopped moving, and then suddenly I got LOGGED OUT of Unity. That is, the system did not reboot, but I had to login again (and all the apps that were open were not anymore, and all the unsaved data lost, obviously). This indicates a xorg crash, right? I hope apport will automatically attach the logs needed to track the cause of the crash. Obviously this is not reproducible (or at least I have no clue how to reproduce it). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Fri Jun 20 23:03:18 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (252 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-24 (27 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.1 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: Fri Jun 20 23:01:47 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1332712 Title: Random xorg crash Status in “xorg” package in Ubuntu: New Bug description: I was watching a Youtube video (actually a youtube Ad just before the video). I had just put it in fullscreen. The whole system stopped responding (couldn't exit fullscreen, couldn't switch window; aound continued to play, or maybe looped, but the video's image freezed), then cpu usage went high (can tell because of the noise of the fan), then the mouse cursor stopped moving, and then suddenly I got LOGGED OUT of Unity. That is, the system did not reboot, but I had to login again (and all the apps that were open were not anymore, and all the unsaved data lost,
[Desktop-packages] [Bug 1330222] Re: All paper options are unavailable when printing to pdf
If it's the expected behavior, then it's wrong or insufficient. You can call it a feature request but it's a pretty basic feature. You _should_ be able to rescale a document to a different paper size when printing, without having to modify the document's properties. A pdf has a page size of its own too, yet when you print it with, say, Evince or Acrobat Reader, you can choose any paper size other than the document's own, and then decide whether to shrink/expand the document to the printable area or not, and whether to center it or not (it does lack the ability to choose a positioning, other than centering or aligning to top-left, which I reported to Evince btw) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1330222 Title: All paper options are unavailable when printing to pdf Status in “inkscape” package in Ubuntu: Confirmed Bug description: Steps to reproduce: File/print - select print to pdf as the printer Go to the Page Setup tab Expected: the Paper options, such as paper size, should work Observed: they are sall greyed out and you can only print to a custom paper size equal to the paper size of the document. When you print to pdf with ANY other program, those options are available. Inkscape should allow you to choose a different paper size and offer the options to scale, center or move to place the printed document in whatever manner relative to the printing area. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:06:55 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1330222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330222] [NEW] All paper options are unavailable when printing to pdf
Public bug reported: Steps to reproduce: File/print - select print to pdf as the printer Go to the Page Setup tab Expected: the Paper options, such as paper size, should work Observed: they are sall greyed out and you can only print to a custom paper size equal to the paper size of the document. When you print to pdf with ANY other program, those options are available. Inkscape should allow you to choose a different paper size and offer the options to scale, center or move to place the printed document in whatever manner relative to the printing area. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:06:55 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1330222 Title: All paper options are unavailable when printing to pdf Status in “inkscape” package in Ubuntu: New Bug description: Steps to reproduce: File/print - select print to pdf as the printer Go to the Page Setup tab Expected: the Paper options, such as paper size, should work Observed: they are sall greyed out and you can only print to a custom paper size equal to the paper size of the document. When you print to pdf with ANY other program, those options are available. Inkscape should allow you to choose a different paper size and offer the options to scale, center or move to place the printed document in whatever manner relative to the printing area. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:06:55 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1330222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330226] [NEW] document viewer has a ridiculous limit for zoomin which depends on the document size
Public bug reported: I am opening a pdf whose page size is of about 2 meters by 1.7 meters, and Evince doesn't let me zoom in to more that 46%. The maximum allowed zoom in should be a fixed percentage, not a fixed total size. There's no need to render the whole document to display only the visible part, and a lot of other programs can handle that same document and view it at any arbitrary zoom, so this limit is simply ridiculous. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:15:51 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1330226 Title: document viewer has a ridiculous limit for zoomin which depends on the document size Status in “evince” package in Ubuntu: New Bug description: I am opening a pdf whose page size is of about 2 meters by 1.7 meters, and Evince doesn't let me zoom in to more that 46%. The maximum allowed zoom in should be a fixed percentage, not a fixed total size. There's no need to render the whole document to display only the visible part, and a lot of other programs can handle that same document and view it at any arbitrary zoom, so this limit is simply ridiculous. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:15:51 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1330226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330227] [NEW] No positioning options in Page Handling when printing!!!
Public bug reported: Open a document, print it select a physical printer select a paper size that doesn't match the document size, e.g. paper size smaller than document Expected: there should be options to set how to POSITION the printed document relative to the paper media: centering, aligning to top-left, top-right, etc, and arbitrary positioning. Observed: there's nothing of that. In the Page Setup tab there is a scale setting expressed as a percentage. In the Page Handling tab there's another Page scaling setting which allows you to choose between None, Fit to printable area, or Shrink to printable area. By the way, it is not clear how this setting would interact with the Scale setting in the other tab. But there's no X and Y or Top and Left settings, so if the document is smaller than the paper size, you can't choose where to print it, and if it is bigger, you can't choose which portion of it to print. How can it lack such a basic vital setting? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:25:38 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1330227 Title: No positioning options in Page Handling when printing!!! Status in “evince” package in Ubuntu: New Bug description: Open a document, print it select a physical printer select a paper size that doesn't match the document size, e.g. paper size smaller than document Expected: there should be options to set how to POSITION the printed document relative to the paper media: centering, aligning to top-left, top-right, etc, and arbitrary positioning. Observed: there's nothing of that. In the Page Setup tab there is a scale setting expressed as a percentage. In the Page Handling tab there's another Page scaling setting which allows you to choose between None, Fit to printable area, or Shrink to printable area. By the way, it is not clear how this setting would interact with the Scale setting in the other tab. But there's no X and Y or Top and Left settings, so if the document is smaller than the paper size, you can't choose where to print it, and if it is bigger, you can't choose which portion of it to print. How can it lack such a basic vital setting? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 18:25:38 2014 InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1330227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330241] [NEW] The file changed on disk alert does not show up unless you switch tab
Public bug reported: Open a file in gedit swicth to some other program, and modify the file that is open in Gedit switch back to gedit Expected: the file changed on disk alert should show up, and prompt you whether to reload the file or keep editing Observed: that doesn't happen until you switch to another tab in gedit and switch back to the tab where that file is open. If you don't have several tabs open, you will NEVER be warned that the file has been changed This is HUGE. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 20:53:53 2014 InstallationDate: Installed on 2013-10-11 (247 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to trusty on 2014-05-24 (22 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1330241 Title: The file changed on disk alert does not show up unless you switch tab Status in “gedit” package in Ubuntu: New Bug description: Open a file in gedit swicth to some other program, and modify the file that is open in Gedit switch back to gedit Expected: the file changed on disk alert should show up, and prompt you whether to reload the file or keep editing Observed: that doesn't happen until you switch to another tab in gedit and switch back to the tab where that file is open. If you don't have several tabs open, you will NEVER be warned that the file has been changed This is HUGE. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 20:53:53 2014 InstallationDate: Installed on 2013-10-11 (247 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to trusty on 2014-05-24 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1330241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330244] [NEW] fails SILENTLY to show images linked in SVG when they cannot be found
Public bug reported: Try to open the attached SVG file in eog Expected behavior: it should show an error message because the SVG references an image that cannot be found. The error message MUST contain the path of the image as indicated in the svg file Observed: no error message. Just silently fails to load the image and shows the document without the image in it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 21:16:42 2014 InstallationDate: Installed on 2013-10-11 (247 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (22 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: image_linked.svg https://bugs.launchpad.net/bugs/1330244/+attachment/4131981/+files/image_linked.svg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1330244 Title: fails SILENTLY to show images linked in SVG when they cannot be found Status in “eog” package in Ubuntu: New Bug description: Try to open the attached SVG file in eog Expected behavior: it should show an error message because the SVG references an image that cannot be found. The error message MUST contain the path of the image as indicated in the svg file Observed: no error message. Just silently fails to load the image and shows the document without the image in it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 15 21:16:42 2014 InstallationDate: Installed on 2013-10-11 (247 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1330244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330103] [NEW] a launcher icon (Terminal) randomly stops responding to clicks and to Alt+tab switching
Public bug reported: Not sure whether this is an issue in whatever part of the system manages window switching, or in the Terminal itself. And this is NOT easily reproducible. I'm observing it for the first time now. I have 3 terminal windows open, which I opened several hours ago, probably even yesterday prior to suspending and resuming. And I have several other windows open. You can see my Launcher in the attached screenshot. If I click on any of the launcher icons except the Terminal's one, they work as expected, bringing the corresponding window to front. However, if I click on the Terminal launcher icon nothing happens (expected: should bring to front one of the terminal windows). And if I click on the very left of it, nothing happens either (expected: should show the three existing windows and allow me to choose one of them). Nothing. If I hit Alt+Tab and try switch to Terminal, it does not work (nothing happens). However, if I hit Alt+Tab until Terminal is highlighted and then keep holding Alt and wait, it does show me the three windows and allow me to switch to any of them by further hitting Tab. And once I do that and have finally one terminal window focused, it does work and the terminal does respond and work, it is not unresponsive or anything. Right now this is only affecting Terminal and no other application. After closing two of the terminal windows (which were accessible with the last method described above), now I have only one, so I can't access it in any way because the alt+tab+and-hold method is not applicable. Finally, my workaround was: - open a new terminal with Ctrl+Alt+T (the issue remained) - ps aux | grep term to figure out the terminal's process id - killed it. Then the launcher icon (I have it locked to launcher) allowed me to open a new terminal window and starting from now everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jun 14 18:57:26 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1330103 Title: a launcher icon (Terminal) randomly stops responding to clicks and to Alt+tab switching Status in “unity” package in Ubuntu: New Bug description: Not sure whether this is an issue in whatever part of the system manages window switching, or in the Terminal itself. And this is NOT easily reproducible. I'm observing it for the first time now. I have 3 terminal windows open, which I opened several hours ago, probably even yesterday prior to suspending and resuming. And I have several other windows open. You can see my Launcher in the attached screenshot. If I click on any of the launcher icons except the Terminal's one, they work as expected, bringing the corresponding window to front. However, if I click on the Terminal launcher icon nothing happens (expected: should bring to front one of the terminal windows). And if I click on the very left of it, nothing happens either (expected: should show the three existing windows and allow me to choose one of them). Nothing. If I hit Alt+Tab and try switch to Terminal, it does not work (nothing happens). However, if I hit Alt+Tab until Terminal is highlighted and then keep holding Alt and wait, it does show me the three windows and allow me to switch to any of them by further hitting Tab. And once I do that and have finally one terminal window focused, it does work and the terminal does respond and work, it is not unresponsive or anything. Right now this is only affecting Terminal and no other application. After closing two of the terminal windows (which were accessible with the last method described above), now I have only one, so I can't access it in any way because the alt+tab+and-hold method is not applicable. Finally, my workaround was: - open a new terminal with Ctrl+Alt+T (the issue remained) - ps aux | grep term to figure out the terminal's process id - killed it. Then the launcher icon (I have it locked to launcher) allowed me to open a new terminal window and starting from now everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1330131] [NEW] all windows suddenly stopped responding to mouse interaction (closing, moving and switching windows)
Public bug reported: All of a sudden, compiz went completely berserk. All basic window functionality related to mouse clicks stopped working: - I could not close a window by clicking on its close button (you could see the button being pressed, but it wouldn't close the window) - I could not move a window by clicking on its title bar and dragging - I could not give focus to a window by clicking on it. At first I thought the system had become unresponsive due to some process eating much CPU (discarded that running top) or eating much memory hence causing thrashing. But then I realized the system was not unresponsive at all. I could switch windows seamlessly using alt+tab. Once focused, each and every application responded well to keyboard. I killed some processes that I wrongly though may be hanging the system: Google Chrome, Nautilus, Thunderbird... nothing fixed the issue. Finally I realized it was purely a window interaction thing, so I killed compiz (which caused it to restart) and the issue was fixed. The last thing I had done at the moment when the issue started, was double clicking on an svg file in Nautilus to open it in eog. During all the time the issue lasted, the file never even opened in eog, and there was not even any eog process running. (it was a pretty big svg file, but I have been opening it in svg thousands of times in these days). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140423-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sun Jun 15 00:26:23 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (246 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.1 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: Thu Jun 12 20:32:35 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.15.1-0ubuntu2 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1330131 Title: all windows suddenly stopped responding to mouse interaction (closing, moving and switching windows)
[Desktop-packages] [Bug 1329869] [NEW] Text tool is counterintuitive beyond unusability
Public bug reported: I click on the A on the left panel in order to create text. I click on the T on the right panel so that text properties such as font face, size, alignment and the like show up. I select Dejavu Sans Mono, bold and centered. I draw a rectangle in the document to create the area for writing text. At this point all the text properties I had set are forgotten, and go back to Sans, normal, and left-aligned. Plus black is now selected as the fill color despite I had selected white like a dozen times before. So I select white again. So, while the text rectangle is there and the cursor is blinking, I go to the Text and Font window which is still open, and I select Dejavu Sans Mono, bold and centered AGAIN. I click Apply. Now finally I can write my text and it preserves the properties. Now I draw another text rectangle somwhere else. Fuck, it has again all the default values for everything. I set them right. NOTE that you must remember to do this AFTER you have drawn the text area rectangle and while it is selected, not before, otherwise it will be useless. Now I want to move and resize a little bit the former text area. So I click within it, that selects it. Fine. But I only see a small diamond on the lower right corner, not on the top-left, so i can only resize from that end. I can't seem to be able to move the textbox. After trying clicking here and there, I find out that by clicking on the diamond on the bottom right corner, a square appears on the top-left too, so I do can move it and resize it as expected; took a while to figure out, though. All this process is painful. Compare this to doing the same task in GIMP, for example, that's waay easier and more intuitive. And note that GIMP is far from being a brilliant example of usability. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 19:21:01 2014 InstallationDate: Installed on 2013-10-11 (244 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (19 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1329869 Title: Text tool is counterintuitive beyond unusability Status in “inkscape” package in Ubuntu: New Bug description: I click on the A on the left panel in order to create text. I click on the T on the right panel so that text properties such as font face, size, alignment and the like show up. I select Dejavu Sans Mono, bold and centered. I draw a rectangle in the document to create the area for writing text. At this point all the text properties I had set are forgotten, and go back to Sans, normal, and left-aligned. Plus black is now selected as the fill color despite I had selected white like a dozen times before. So I select white again. So, while the text rectangle is there and the cursor is blinking, I go to the Text and Font window which is still open, and I select Dejavu Sans Mono, bold and centered AGAIN. I click Apply. Now finally I can write my text and it preserves the properties. Now I draw another text rectangle somwhere else. Fuck, it has again all the default values for everything. I set them right. NOTE that you must remember to do this AFTER you have drawn the text area rectangle and while it is selected, not before, otherwise it will be useless. Now I want to move and resize a little bit the former text area. So I click within it, that selects it. Fine. But I only see a small diamond on the lower right corner, not on the top-left, so i can only resize from that end. I can't seem to be able to move the textbox. After trying clicking here and there, I find out that by clicking on the diamond on the bottom right corner, a square appears on the top-left too, so I do can move it and resize it as expected; took a while to figure out, though. All this process is painful. Compare this to doing the same task in GIMP, for example, that's waay easier and more intuitive. And note that GIMP is far from being a brilliant example of usability. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 19:21:01 2014 InstallationDate: Installed on 2013-10-11 (244 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage:
[Desktop-packages] [Bug 1329886] [NEW] saves ghost empty text boxes
Public bug reported: Steps to reproduce: - select the text tool - draw the area where you want to write the text - Whops, that was not exactly the area I want it, let's redraw it from scratch - One more time - save into plain SVG (I guess Inkscape SVG would do as well) Expected result: the empty textboxes should be completely forgotten and deleted; OR they should be visible and accessible, so that you know they are there and you can move, modify, or remove them Observed: everything looks like those text boxes you accidentally drew and left empty don't exist. You can't see them, you can't select them, you can't reuse them and write into them, or delete them. YET they are saved into the SVG file. You get garbage empty useless invisible text areas that you can't even delete. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 20:06:08 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1329886 Title: saves ghost empty text boxes Status in “inkscape” package in Ubuntu: New Bug description: Steps to reproduce: - select the text tool - draw the area where you want to write the text - Whops, that was not exactly the area I want it, let's redraw it from scratch - One more time - save into plain SVG (I guess Inkscape SVG would do as well) Expected result: the empty textboxes should be completely forgotten and deleted; OR they should be visible and accessible, so that you know they are there and you can move, modify, or remove them Observed: everything looks like those text boxes you accidentally drew and left empty don't exist. You can't see them, you can't select them, you can't reuse them and write into them, or delete them. YET they are saved into the SVG file. You get garbage empty useless invisible text areas that you can't even delete. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 20:06:08 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1329886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329900] [NEW] fix flowed text in svg
Public bug reported: I ran into the problem described at http://wiki.inkscape.org/wiki/index.php/FAQ#What_about_flowed_text.3F If however you really need flowed text, you will have to convert it to regular (non-flowed) text by the Convert to text command in the Text menu. THIS COMMAND FULLY PRESERVES THE APPEARANCE AND FORMATTED OF YOUR FLOWED TEXT but makes it non-flowed and SVG 1.1-compliant. (emphasys added) The part in uppercase is bullshit. If you chose the text and do convert to text, the text completely changes its positioning. For example, I have a text centered to a certain area, and it moves to the left to an apparently random position. Also, if you have decided to keep the flowed text feature, it makes NO SENSE to keep it in its current broken status which corresponds to an obsolete version of the specs until the SVG 1.2 draft becomes final. You should fix the implementation to conform to the current status of the standard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 20:25:11 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: I ran into the problem described at http://wiki.inkscape.org/wiki/index.php/FAQ#What_about_flowed_text.3F If however you really need flowed text, you will have to convert it to regular (non-flowed) text by the Convert to text command in the Text menu. THIS COMMAND FULLY PRESERVES THE APPEARANCE AND FORMATTED OF YOUR FLOWED TEXT but makes it non-flowed and SVG 1.1-compliant. (emphasys added) The part in uppercase is bullshit. If you chose the text and do convert - to text, the text completely changes it's appearance. For example, I - have a text centered to a certain area, and it becomes aligned to the - left and even moves to a position that has nothing to do with the left - border of the original text area. + to text, the text completely changes its positioning. For example, I + have a text centered to a certain area, and it moves to the left to an + apparently random position. - - Also, if you have decided to keep the flowed text feature, it makes NO SENSE to keep it in its current broken status which corresponds to an obsolete version of the specs until the SVG 1.2 draft becomes final. You should fix the implementation to conform to the current status of the standard. + Also, if you have decided to keep the flowed text feature, it makes NO + SENSE to keep it in its current broken status which corresponds to an + obsolete version of the specs until the SVG 1.2 draft becomes final. You + should fix the implementation to conform to the current status of the + standard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 20:25:11 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1329900 Title: fix flowed text in svg Status in “inkscape” package in Ubuntu: New Bug description: I ran into the problem described at http://wiki.inkscape.org/wiki/index.php/FAQ#What_about_flowed_text.3F If however you really need flowed text, you will have to convert it to regular (non-flowed) text by the Convert to text command in the Text menu. THIS COMMAND FULLY PRESERVES THE APPEARANCE AND FORMATTED OF YOUR FLOWED TEXT but makes it non-flowed and SVG 1.1-compliant. (emphasys added) The part in uppercase is bullshit. If you chose the text and do convert to text, the text completely changes its positioning. For example, I have a text centered to a certain area, and it moves to the left to an apparently random position. Also, if you have decided to keep the flowed text feature, it makes NO SENSE to keep it in its current broken status which corresponds to an obsolete version of the specs until the SVG 1.2 draft becomes final. You should fix the implementation to conform to the current status of the standard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1329900] Re: fix flowed text in svg
How is one supposed to achieve centering text into a given area without flowed text? Even if you fix the conversion of flowed to regular text, that wouldn't be enough because if one edits the text he will need to recenter it manually. You should provide tools to achieve with regular text the same that you can achieve with flowed text if you're not going to fix the support for flowed text. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1329900 Title: fix flowed text in svg Status in “inkscape” package in Ubuntu: New Bug description: I ran into the problem described at http://wiki.inkscape.org/wiki/index.php/FAQ#What_about_flowed_text.3F If however you really need flowed text, you will have to convert it to regular (non-flowed) text by the Convert to text command in the Text menu. THIS COMMAND FULLY PRESERVES THE APPEARANCE AND FORMATTED OF YOUR FLOWED TEXT but makes it non-flowed and SVG 1.1-compliant. (emphasys added) The part in uppercase is bullshit. If you chose the text and do convert to text, the text completely changes its positioning. For example, I have a text centered to a certain area, and it moves to the left to an apparently random position. Also, if you have decided to keep the flowed text feature, it makes NO SENSE to keep it in its current broken status which corresponds to an obsolete version of the specs until the SVG 1.2 draft becomes final. You should fix the implementation to conform to the current status of the standard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 20:25:11 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1329900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] [NEW] absolute text size changes wildly depending on zoom
Public bug reported: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot from 2014-06-13 21:12:29.png https://bugs.launchpad.net/bugs/1329924/+attachment/4131146/+files/Screenshot%20from%202014-06-13%2021%3A12%3A29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:02:43.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131150/+files/Screenshot%20from%202014-06-13%2021%3A02%3A43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:01:56.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131152/+files/Screenshot%20from%202014-06-13%2021%3A01%3A56.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:11:12.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131149/+files/Screenshot%20from%202014-06-13%2021%3A11%3A12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
Sorry, even the SVG file itself is too big. I don't think you really need it to triage the issue. I guess any svg file with text will do -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:01:06.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131154/+files/Screenshot%20from%202014-06-13%2021%3A01%3A06.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:01:34.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131153/+files/Screenshot%20from%202014-06-13%2021%3A01%3A34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329924] Re: absolute text size changes wildly depending on zoom
** Attachment added: Screenshot from 2014-06-13 21:02:29.png https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+attachment/4131151/+files/Screenshot%20from%202014-06-13%2021%3A02%3A29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329924 Title: absolute text size changes wildly depending on zoom Status in “eog” package in Ubuntu: New Bug description: Look at the screenshots. It's the same SVG file viewed with different zooms in Image Viewer. Look at the second line of text on the top-left and how it's size relative to the image below varies a lot at different zooms. I also attach the SVG, though it includes a linked raster image that you won't see and that I can't include because it's huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 21:00:38 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 156201] Re: gedit handles opening big files badly
I mean (just in case i wasn't clear), the problem is not only in bad handling of truly unmanageable files (which should fail gently), but also in a tremendous inefficiency that makes it impossible to handle files that could perfectly be handled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/156201 Title: gedit handles opening big files badly Status in Light-Weight Text Editor for Gnome: Confirmed Status in “gedit” package in Ubuntu: Triaged Bug description: Binary package hint: gedit Opening big text files (400 MB, 750 MB) in gedit is bad - from a usability standpoint - There's no progress bar or cancel button for the action, and the load takes a long time. - from a system standpoint: - In earlier versions, gedit would take so much memory until the system swapped all other applications to disk, and the system became unusable. - Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but the message failed to allocate X bytes in the console. Original description: I just opened a 400 MB text file (mbox mail file) in gedit, and it my system has now been unresponsive for minutes. Other editors can open large files without a problem. Also, there's no progress bar or cancel button that would make it easy to see how long gedit is loading the file or to cancel the load. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 156201] Re: gedit handles opening big files badly
It's much worse than described. It's not just that you don't (and should) see a progress bar, that the whole UI blocks (and shouldn't) and that you don't get a warning when the file actually can't be properly handled. It's also that handling of big files is ridiculously inefficient. A file as small as 30MB hangs gedit, takes ages to load, and renders the UI unresponsive every once in a while when trying to scroll it. I can open the very same file in VIM seamlessly in a fraction of a second and navigate through it. And vim does syntax highlight too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/156201 Title: gedit handles opening big files badly Status in Light-Weight Text Editor for Gnome: Confirmed Status in “gedit” package in Ubuntu: Triaged Bug description: Binary package hint: gedit Opening big text files (400 MB, 750 MB) in gedit is bad - from a usability standpoint - There's no progress bar or cancel button for the action, and the load takes a long time. - from a system standpoint: - In earlier versions, gedit would take so much memory until the system swapped all other applications to disk, and the system became unusable. - Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but the message failed to allocate X bytes in the console. Original description: I just opened a 400 MB text file (mbox mail file) in gedit, and it my system has now been unresponsive for minutes. Other editors can open large files without a problem. Also, there's no progress bar or cancel button that would make it easy to see how long gedit is loading the file or to cancel the load. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329963] [NEW] Normal scrollbars lack up/down buttons
Public bug reported: On 14.04, I have disabled the annoying, and buggy overlay scrollbars that I've hated since they appeared, with the method described here: http://ubuntuhandbook.org/index.php/2013/10/disable-overlay-scrollbars-ubuntu13-10/ So now I have normal scrollbars, which is good, except that THEY LACK THE UP/DOWN BUTTON that should be present at the top and bottom (either an up button at the top and a down button at the bottom, or both either at top or bottom). Why the developers of Ubuntu keep destroying the usability of such basic, obvious things as scrollbars, is beyond me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 13 23:36:03 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1329963 Title: Normal scrollbars lack up/down buttons Status in “unity” package in Ubuntu: New Bug description: On 14.04, I have disabled the annoying, and buggy overlay scrollbars that I've hated since they appeared, with the method described here: http://ubuntuhandbook.org/index.php/2013/10/disable-overlay-scrollbars-ubuntu13-10/ So now I have normal scrollbars, which is good, except that THEY LACK THE UP/DOWN BUTTON that should be present at the top and bottom (either an up button at the top and a down button at the bottom, or both either at top or bottom). Why the developers of Ubuntu keep destroying the usability of such basic, obvious things as scrollbars, is beyond me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 13 23:36:03 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1329963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329964] [NEW] Scrollbars don't behave properly (completely unusable) if content is slow to render
Public bug reported: Open a file that takes a lot of memory and/or is cpu-intensive to render, such as a huge SVG file with a lot of stuff. Zoom in so that the document is significantly bigger than the window Compare these two cases: 1) (works as expected) Click somewhere and drag to somewhere else, to move the document relative to the window 2) (BROKEN) Drag the vertical or horizontal scrollbar to scroll the document vertically or horizontally Expected: in both cases, after you're done moving, the program will take its time to render the new visible portion of the document and when it's done you'll see the document at the position where you have moved. The distance the document should have moved should be exactly equal to the distance the mouse cursor have moved while dragging. Observed: case (1) works as expected. But in case 2, the scrollbar will only move a very little bit and the document will only scroll a little bit. The scrollbar won't ever reach the point where the mouse cursor is, not even closely. Scrollbars just can't be used to navigate in a document that is costly to draw. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 23:50:21 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1329964 Title: Scrollbars don't behave properly (completely unusable) if content is slow to render Status in “eog” package in Ubuntu: New Bug description: Open a file that takes a lot of memory and/or is cpu-intensive to render, such as a huge SVG file with a lot of stuff. Zoom in so that the document is significantly bigger than the window Compare these two cases: 1) (works as expected) Click somewhere and drag to somewhere else, to move the document relative to the window 2) (BROKEN) Drag the vertical or horizontal scrollbar to scroll the document vertically or horizontally Expected: in both cases, after you're done moving, the program will take its time to render the new visible portion of the document and when it's done you'll see the document at the position where you have moved. The distance the document should have moved should be exactly equal to the distance the mouse cursor have moved while dragging. Observed: case (1) works as expected. But in case 2, the scrollbar will only move a very little bit and the document will only scroll a little bit. The scrollbar won't ever reach the point where the mouse cursor is, not even closely. Scrollbars just can't be used to navigate in a document that is costly to draw. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 13 23:50:21 2014 InstallationDate: Installed on 2013-10-11 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1329964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328655] [NEW] image viewer suddenly and randomly becomes unresponsive when viewing big image and hangs the whole system - only option hard shut down
Public bug reported: I have a png image with a size of 8580 by 6000 pixels. The file is about 83MB in size (I know, the image uncompressed into memory is much bigger, should be in the order of 147 or perhaps 196 MB; not that much, anyway). I can usually view and handle it easily with Image Viewer: zoom in, zoom out, move around, without issues. I never modify and save it from within Image Viewer, I just use it to view it. Every once in a while, I close Image Viewer, I regenerate the image, and I open it again in Image Viewer. Everything works fine for a few times. Then suddenly, when I have already opened the image and zoomed in and out and moved around a few times and it seems to be working just fine, the loading progress bar shows up on the bottom right corner of Image Viewer, as if it was reloading the image (though it has NOT been modified); the progress bar gets stuck around 18% or so, and the program becomes completely unresponsive, and the whole system does. It looks like Image Viewer suddenly starts eating up a lot of memory, causing thrashing. It's the typical symptoms. The system won't respond to clicks and keystrokes (the mouse cursor does move, but jerkily). So I can't even close Image Viewer or switch to a terminal or virtual console and kill it; the only thing I can do is to physically power off the computer. The last part is a more system-wide bug in Ubuntu (an OS should never, ever stall unrecoverably because of the misbehavior of a single program, no matter how bad), but the fact that Image Viewer suddenly begins eating up memory exponentially (or whatever it is that it does causing the system collapse) is certainly a bug in ImageViewer, and a critical one. It happens SYSTEMATICALLY after a few times I open and close the image. I can't tell if it's systematically after a given number of times, but sooner or later, it will happen, guaranteed. I have already rebooted with the hardware button like 5 or 6 times in a few hours because of this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 20:57:23 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1328655 Title: image viewer suddenly and randomly becomes unresponsive when viewing big image and hangs the whole system - only option hard shut down Status in “eog” package in Ubuntu: New Bug description: I have a png image with a size of 8580 by 6000 pixels. The file is about 83MB in size (I know, the image uncompressed into memory is much bigger, should be in the order of 147 or perhaps 196 MB; not that much, anyway). I can usually view and handle it easily with Image Viewer: zoom in, zoom out, move around, without issues. I never modify and save it from within Image Viewer, I just use it to view it. Every once in a while, I close Image Viewer, I regenerate the image, and I open it again in Image Viewer. Everything works fine for a few times. Then suddenly, when I have already opened the image and zoomed in and out and moved around a few times and it seems to be working just fine, the loading progress bar shows up on the bottom right corner of Image Viewer, as if it was reloading the image (though it has NOT been modified); the progress bar gets stuck around 18% or so, and the program becomes completely unresponsive, and the whole system does. It looks like Image Viewer suddenly starts eating up a lot of memory, causing thrashing. It's the typical symptoms. The system won't respond to clicks and keystrokes (the mouse cursor does move, but jerkily). So I can't even close Image Viewer or switch to a terminal or virtual console and kill it; the only thing I can do is to physically power off the computer. The last part is a more system-wide bug in Ubuntu (an OS should never, ever stall unrecoverably because of the misbehavior of a single program, no matter how bad), but the fact that Image Viewer suddenly begins eating up memory exponentially (or whatever it is that it does causing the system collapse) is certainly a bug in ImageViewer, and a critical one. It happens SYSTEMATICALLY after a few times I open and close the image. I can't tell if it's systematically after a given number of times, but sooner or later, it will happen, guaranteed. I have already rebooted with the hardware button like 5 or 6 times in a few hours
[Desktop-packages] [Bug 1328655] Re: image viewer suddenly and randomly becomes unresponsive when viewing big image and hangs the whole system - only option hard shut down
OMFG, I've found out what triggers this. It's not randomly opening and closing the image several times. It's when I accidentally hit the spacebar, which in ImageViewer is stupidly used as a keyboard shortcut for loading the next image in the folder, which happens to be a huge svg file of several GB. So the issue happens to be the combination of two issues: - (the huge one) when attempting to load a file too large to be manageable, instead of issuing an error message or warning, eog tries to load it and eat up as much memory as required, hanging the whole OS - (a small one) image viewer uses a ridiculous shortcut for next which is the space bar (I wonder what's the shortcut for previous) which is unexpected, counterintuitive, and in contrast with prevailing conventions in other similar software. I'll file these as separate bugs and close this one. ** Changed in: eog (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1328655 Title: image viewer suddenly and randomly becomes unresponsive when viewing big image and hangs the whole system - only option hard shut down Status in “eog” package in Ubuntu: Invalid Bug description: I have a png image with a size of 8580 by 6000 pixels. The file is about 83MB in size (I know, the image uncompressed into memory is much bigger, should be in the order of 147 or perhaps 196 MB; not that much, anyway). I can usually view and handle it easily with Image Viewer: zoom in, zoom out, move around, without issues. I never modify and save it from within Image Viewer, I just use it to view it. Every once in a while, I close Image Viewer, I regenerate the image, and I open it again in Image Viewer. Everything works fine for a few times. Then suddenly, when I have already opened the image and zoomed in and out and moved around a few times and it seems to be working just fine, the loading progress bar shows up on the bottom right corner of Image Viewer, as if it was reloading the image (though it has NOT been modified); the progress bar gets stuck around 18% or so, and the program becomes completely unresponsive, and the whole system does. It looks like Image Viewer suddenly starts eating up a lot of memory, causing thrashing. It's the typical symptoms. The system won't respond to clicks and keystrokes (the mouse cursor does move, but jerkily). So I can't even close Image Viewer or switch to a terminal or virtual console and kill it; the only thing I can do is to physically power off the computer. The last part is a more system-wide bug in Ubuntu (an OS should never, ever stall unrecoverably because of the misbehavior of a single program, no matter how bad), but the fact that Image Viewer suddenly begins eating up memory exponentially (or whatever it is that it does causing the system collapse) is certainly a bug in ImageViewer, and a critical one. It happens SYSTEMATICALLY after a few times I open and close the image. I can't tell if it's systematically after a given number of times, but sooner or later, it will happen, guaranteed. I have already rebooted with the hardware button like 5 or 6 times in a few hours because of this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 20:57:23 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1328655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328666] [NEW] in attempt to load a huge svg file, eats up too much memory and renders whole os unresponsive
Public bug reported: Steps to reproduce: - pick a huge unmanageable multi-GB SVG file - try to open it in Image Viewer (in real life you would obviously do it by accident) Expected behavior: - an error message should be displayed, such as File too big or, if it the exact point where a file becomes too big to be managed cannot be predicted (which I doubt), then a warning, such as this file may be too big and bla bla bla. Are you sure you wish to continue? - in ANY case, when memory consumption does start to render the program unresponsive, a possibility should be given to the user to abort loading the file. Actually, the UI should ALWAYS remain responsive and allow you to at least force close the program Observed behavior: - Image Viewer blindly tries to load the file as if it was any normal size file, and it will end up eating up too much memory and become unresponsive (this will actually render the whole system unworkable in an unrecoverable way, but that part is a bug in the OS, as it should always guarantee the system's stability in presence of misbehavior of one process) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 21:42:48 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1328666 Title: in attempt to load a huge svg file, eats up too much memory and renders whole os unresponsive Status in “eog” package in Ubuntu: New Bug description: Steps to reproduce: - pick a huge unmanageable multi-GB SVG file - try to open it in Image Viewer (in real life you would obviously do it by accident) Expected behavior: - an error message should be displayed, such as File too big or, if it the exact point where a file becomes too big to be managed cannot be predicted (which I doubt), then a warning, such as this file may be too big and bla bla bla. Are you sure you wish to continue? - in ANY case, when memory consumption does start to render the program unresponsive, a possibility should be given to the user to abort loading the file. Actually, the UI should ALWAYS remain responsive and allow you to at least force close the program Observed behavior: - Image Viewer blindly tries to load the file as if it was any normal size file, and it will end up eating up too much memory and become unresponsive (this will actually render the whole system unworkable in an unrecoverable way, but that part is a bug in the OS, as it should always guarantee the system's stability in presence of misbehavior of one process) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 21:42:48 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1328666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328670] [NEW] spacebar shortcut for load next image in the folder is a very bad idea
Public bug reported: In MOST graphics editing and viewing software, the spacebar usually allows you to move the document around with the mouse relative to the window. This is a very widespread convention and has been so for decades. In Image Viewer, you can do that by just clicking and dragging, so it's OK that the space bar is not needed for that, but it is a TERRIBLE idea to use it as a shortcut for something else. And even a worse idea is to use it as the shortcut for load the next file in the folder. Nobody in his right mind would expect the space bar to do that. It's one of the most counterintuitive keyboard shortcuts I've ever seen. And when the set of shortcuts is not supposed to be intuitive (when there are a lot of functions for which to design a shortcut, it's ok to give up intuitiveness and have the user learn the shortcuts by looking at the menus), then it is common and good practice to avoid obvious and common keys (such as the space bar), that can be hit by mistake, for non-obvious tasks (such as load another file in the folder). Also, the key or key combination used for load next file should have an obvious counterpart for load previous file. So, for example, the pagedown key would be a reasonable choice for next, because you could then have pageup for previous. Or perhaps the right arrow combined with ctrl, shift or something (not alone, because you expect that to move the image), because its obvious counterpart for previous would be the left arrow. The spacebar doesn't have any obvious opposite key so it's intrinsically a bad candidate as a shortcut for next file. So there are at least 3 reasons why the space bar is a terrible keyboard shortcut for the action of loading the next file in the folder. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 21:42:59 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1328670 Title: spacebar shortcut for load next image in the folder is a very bad idea Status in “eog” package in Ubuntu: New Bug description: In MOST graphics editing and viewing software, the spacebar usually allows you to move the document around with the mouse relative to the window. This is a very widespread convention and has been so for decades. In Image Viewer, you can do that by just clicking and dragging, so it's OK that the space bar is not needed for that, but it is a TERRIBLE idea to use it as a shortcut for something else. And even a worse idea is to use it as the shortcut for load the next file in the folder. Nobody in his right mind would expect the space bar to do that. It's one of the most counterintuitive keyboard shortcuts I've ever seen. And when the set of shortcuts is not supposed to be intuitive (when there are a lot of functions for which to design a shortcut, it's ok to give up intuitiveness and have the user learn the shortcuts by looking at the menus), then it is common and good practice to avoid obvious and common keys (such as the space bar), that can be hit by mistake, for non-obvious tasks (such as load another file in the folder). Also, the key or key combination used for load next file should have an obvious counterpart for load previous file. So, for example, the pagedown key would be a reasonable choice for next, because you could then have pageup for previous. Or perhaps the right arrow combined with ctrl, shift or something (not alone, because you expect that to move the image), because its obvious counterpart for previous would be the left arrow. The spacebar doesn't have any obvious opposite key so it's intrinsically a bad candidate as a shortcut for next file. So there are at least 3 reasons why the space bar is a terrible keyboard shortcut for the action of loading the next file in the folder. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 21:42:59 2014 InstallationDate: Installed on 2013-10-11 (242 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: eog UpgradeStatus: Upgraded to trusty on 2014-05-24 (17 days ago) To manage notifications about this bug
[Desktop-packages] [Bug 1328213] [NEW] you can accidentally resize windows when they are not even visible while in show desktop mode
Public bug reported: This is unbelievable. Steps to reproduce: 1. make sure you have a few windows open and not maximized 2. hit ctrl+super+D to hide all windows and show the desktop 3. move the mouse around slowly, especially around where you remember some windows' edges were when the windows were visible Expected: nothing: the mouse cursor should remain the default one and any mouse action should always interact with the desktop and its icons Observed: the mouse cursor behaves as if the hidden windows were there. You suddenly see the mouse cursor change to the window-resizing cursor, and if you then click and drag, you will actually resize the windows that you are not seing. When you then hit Ctrl+Super+D again and the windows show up back, you'll see what you've done to them. Not to mention this often prevents you from properly interacting with the icons on the desktop.ç One more screwed-upness of the poorly designed and worse implemented show/hide desktop feature in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jun 9 20:13:36 2014 InstallationDate: Installed on 2013-10-11 (241 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (16 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1328213 Title: you can accidentally resize windows when they are not even visible while in show desktop mode Status in “unity” package in Ubuntu: New Bug description: This is unbelievable. Steps to reproduce: 1. make sure you have a few windows open and not maximized 2. hit ctrl+super+D to hide all windows and show the desktop 3. move the mouse around slowly, especially around where you remember some windows' edges were when the windows were visible Expected: nothing: the mouse cursor should remain the default one and any mouse action should always interact with the desktop and its icons Observed: the mouse cursor behaves as if the hidden windows were there. You suddenly see the mouse cursor change to the window- resizing cursor, and if you then click and drag, you will actually resize the windows that you are not seing. When you then hit Ctrl+Super+D again and the windows show up back, you'll see what you've done to them. Not to mention this often prevents you from properly interacting with the icons on the desktop.ç One more screwed-upness of the poorly designed and worse implemented show/hide desktop feature in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jun 9 20:13:36 2014 InstallationDate: Installed on 2013-10-11 (241 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1328213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328217] [NEW] space bar should allow to easily move around the document without using scrollbars
Public bug reported: Since, I believe, the Nineties, all graphic editing and viewing software I have ever seen allows you to navigate horizontally and vertically through the document by hitting the space bar and moving the mouse, or by hitting the spacebar, clicking and dragging. Inkscape lacks this essential feature and obliges you to move through the document horizontally and vertically separately by using the scrollbars, which is tremendously annoying. Or perhaps it has another keyboard shortcut to allow you to easily move around the document using the mouse, different from the universal convention that has been omnipresent in every other graphic editing software in the last 20 years or so. In either case, it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 9 20:22:25 2014 InstallationDate: Installed on 2013-10-11 (241 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (16 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1328217 Title: space bar should allow to easily move around the document without using scrollbars Status in “inkscape” package in Ubuntu: New Bug description: Since, I believe, the Nineties, all graphic editing and viewing software I have ever seen allows you to navigate horizontally and vertically through the document by hitting the space bar and moving the mouse, or by hitting the spacebar, clicking and dragging. Inkscape lacks this essential feature and obliges you to move through the document horizontally and vertically separately by using the scrollbars, which is tremendously annoying. Or perhaps it has another keyboard shortcut to allow you to easily move around the document using the mouse, different from the universal convention that has been omnipresent in every other graphic editing software in the last 20 years or so. In either case, it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: inkscape 0.48.4-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 9 20:22:25 2014 InstallationDate: Installed on 2013-10-11 (241 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: inkscape UpgradeStatus: Upgraded to trusty on 2014-05-24 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1328217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326948] [NEW] Misses an option to break big pages into smaller sheets (or viceversa) when printing
Public bug reported: When you print a PDF document, and you choose a print paper size which is different from the document's paper size, you can shrink or fit to printable area (or neither), but there is no way to: - break big pages into smaller ones, such as for example break each A3 page into two printed A4 sheets - combine small pages into bigger paper Those are OBVIOUS options that should be present when printing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 21:53:08 2014 InstallationDate: Installed on 2013-10-11 (237 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (12 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1326948 Title: Misses an option to break big pages into smaller sheets (or viceversa) when printing Status in “evince” package in Ubuntu: New Bug description: When you print a PDF document, and you choose a print paper size which is different from the document's paper size, you can shrink or fit to printable area (or neither), but there is no way to: - break big pages into smaller ones, such as for example break each A3 page into two printed A4 sheets - combine small pages into bigger paper Those are OBVIOUS options that should be present when printing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 21:53:08 2014 InstallationDate: Installed on 2013-10-11 (237 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-05-24 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1326948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1324298] [NEW] Incorrect (perhaps outdated) number of windows displayed next to launcher icons
Public bug reported: The number of white arrows on the left of Launcher icons, which is supposed to indicate the number of open windows of a given application, often is incorrect; I think it is because it doesn't always get updated when the number of windows changes (e.g. a window of the same application is open or closed). Switching to another application and then back to the affected one fixes the issue. For example, i have observed only one arrow next to the Terminal icon on Launcher, when I did have two terminal windows open. AND viceversa, on another occasion, there were two arrows next to Google Chrome's Launcher icon when I there was only one open Google Chrome window (I had closed the second window several minutes earlier). I'm almost sure this is a regression in Ubuntu 14.04, because I had never observed it before the upgrade, and now, after upgrading, I have already observed it twice in just a couple of days. Unless that's just an unlikely coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 29 01:01:20 2014 InstallationDate: Installed on 2013-10-11 (229 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (4 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1324298 Title: Incorrect (perhaps outdated) number of windows displayed next to launcher icons Status in “unity” package in Ubuntu: New Bug description: The number of white arrows on the left of Launcher icons, which is supposed to indicate the number of open windows of a given application, often is incorrect; I think it is because it doesn't always get updated when the number of windows changes (e.g. a window of the same application is open or closed). Switching to another application and then back to the affected one fixes the issue. For example, i have observed only one arrow next to the Terminal icon on Launcher, when I did have two terminal windows open. AND viceversa, on another occasion, there were two arrows next to Google Chrome's Launcher icon when I there was only one open Google Chrome window (I had closed the second window several minutes earlier). I'm almost sure this is a regression in Ubuntu 14.04, because I had never observed it before the upgrade, and now, after upgrading, I have already observed it twice in just a couple of days. Unless that's just an unlikely coincidence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 29 01:01:20 2014 InstallationDate: Installed on 2013-10-11 (229 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1324298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244778] LightdmGreeterLog.txt
apport information ** Attachment added: LightdmGreeterLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114451/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Re: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files
apport information ** Tags added: apport-collected compiz-0.9 saucy ubuntu ** Description changed: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.12.5-0ubuntu2.2 + 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 + DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job + DistroCodename: saucy + DistroRelease: Ubuntu 13.10 + DistroVariant: ubuntu + DkmsStatus: + vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed + vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed + vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed + vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed + vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Acer Incorporated [ALI] Device [1025:0647] + NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] + InstallationDate: Installed on 2013-10-11 (217 days ago) + InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) + MachineType: Acer Aspire V3-571G + MarkForUpload: True + Package: xorg 1:7.7+1ubuntu6 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 + Tags: saucy ubuntu compiz-0.9 + Uname: Linux 3.11.0-20-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + dmi.bios.date: 10/15/2012 + dmi.bios.vendor: Acer + dmi.bios.version: V2.07 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: VA50_HC_CR + dmi.board.vendor: Acer + dmi.board.version: Type2 - Board Version + dmi.chassis.type: 10 + dmi.chassis.vendor: Acer + dmi.chassis.version: V2.07 + dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: + dmi.product.name: Aspire V3-571G + dmi.product.version: V2.07 + dmi.sys.vendor: Acer + version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.46-1ubuntu1 + version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 + version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 + xserver.bootTime: Fri May 16 15:53:10 2014 + xserver.configfile: default + xserver.errors: + Failed to load module nvidia (module does not exist, 0) + Failed to load module nvidia (module does not exist, 0) + NOUVEAU(G0): [XvMC] Failed to initialize extension. + xserver.logfile: /var/log/Xorg.0.log + xserver.outputs: + product id8940 + vendor AUO + xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1244778/+attachment/411/+files/BootDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg
[Desktop-packages] [Bug 1244778] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114457/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114460/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114461/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] LightdmGreeterLogOld.txt
apport information ** Attachment added: LightdmGreeterLogOld.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114452/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114453/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114463/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114446/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114455/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114454/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114449/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114445/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114462/+files/UdevLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] MonitorsUser.xml.txt
apport information ** Attachment added: MonitorsUser.xml.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114456/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114459/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] LightdmDisplayLog.txt
apport information ** Attachment added: LightdmDisplayLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114450/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114464/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114448/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114447/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Re: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files
Ok so I have collected the information that I was asked, which is completely irrelevant to the bug as anyone reading the bug description would notice, and also completely meaningless as I am not (nor can I ever be anymore) on any of the computers where I observed the issue (but again, that's irrelevant). ** Changed in: xorg (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor
[Desktop-packages] [Bug 1244778] Re: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files
Ok so I have added the apport information, which is completely irrelevant to the issue, as anybody willing to read the issue description will notice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114467/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114468/+files/xserver.devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114465/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114466/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1244778] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1244778/+attachment/4114458/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1244778 Title: Xorg should be way more resilient or at least print detailed information in presence of errors in configuration files Status in “xorg” package in Ubuntu: New Bug description: Basically the real issue is that whenever there's an error in some xorg configruation file, xorg fails to start, instead of trying to fallback to some minimal working settings and/or printing debuggable information about the error. It's too fragile. By doing something wrong with some xorg configuration file, you may end up with a system that won't even boot and allow you to fix the error. I'll delete the original description as it is not relevant. (I guess it can be seen anyway in the edit history) See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 which is a somehow related case (an error in some xorg config file rendering the whole system unusable, and no clue to the user about it) --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2014-02-23 01:23:33,436 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.11.0-17-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.2, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (217 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-20-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-02-23 (83 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri May 16 15:53:10 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244778/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1225527] [NEW] buzzing sound emits from speakers when no audio is played. input is turned off.
Public bug reported: suspect it is caused by the digital audio driver clashing with the analog audio output. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joey 2252 F pulseaudio /dev/snd/pcmC1D0p: joey 2252 F...m pulseaudio /dev/snd/controlC0: joey 2252 F pulseaudio Date: Sun Sep 15 04:36:09 2013 InstallationDate: Installed on 2013-08-31 (14 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN26WW(V1.07) dmi.board.asset.tag: YB00068940 dmi.board.name: 20216 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: YB00068940 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y410P dmi.modalias: dmi:bvnLENOVO:bvr74CN26WW(V1.07):bd05/08/2013:svnLENOVO:pn20216:pvrLenovoIdeaPadY410P:rvnLENOVO:rn20216:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY410P: dmi.product.name: 20216 dmi.product.version: Lenovo IdeaPad Y410P dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1225527 Title: buzzing sound emits from speakers when no audio is played. input is turned off. Status in “pulseaudio” package in Ubuntu: New Bug description: suspect it is caused by the digital audio driver clashing with the analog audio output. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joey 2252 F pulseaudio /dev/snd/pcmC1D0p: joey 2252 F...m pulseaudio /dev/snd/controlC0: joey 2252 F pulseaudio Date: Sun Sep 15 04:36:09 2013 InstallationDate: Installed on 2013-08-31 (14 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN26WW(V1.07) dmi.board.asset.tag: YB00068940 dmi.board.name: 20216 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: YB00068940 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y410P dmi.modalias: dmi:bvnLENOVO:bvr74CN26WW(V1.07):bd05/08/2013:svnLENOVO:pn20216:pvrLenovoIdeaPadY410P:rvnLENOVO:rn20216:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY410P: dmi.product.name: 20216 dmi.product.version: Lenovo IdeaPad Y410P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1225527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
