[Desktop-packages] [Bug 1696261] [NEW] Settings app items have bad text wrapping
Public bug reported: Ubuntu GNOME 17.04 with GNOME 3.24. gnome-control-center: Installed: 1:3.24.1-0ubuntu1 Candidate: 1:3.24.1-0ubuntu1 What actually happened: When I open settings, I find that my perfectly innocuous Region & Language settings have been kidnapped by a stranger named Lan Guage. I don't know who Mr. Guage is but I would like him to return my settings. What I expected to happen: Find settings app that has not been visited by Lan Guage. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 15:57:59 2017 InstallationDate: Installed on 2017-05-30 (7 days ago) InstallationMedia: System76 17.04 "Zesty Zapus" - Release amd64 (20170410) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages zesty ** Attachment added: "Screenshot of Lan Guage" https://bugs.launchpad.net/bugs/1696261/+attachment/4890443/+files/Screenshot%20from%202017-06-06%2015-57-35.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696261 Title: Settings app items have bad text wrapping Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu GNOME 17.04 with GNOME 3.24. gnome-control-center: Installed: 1:3.24.1-0ubuntu1 Candidate: 1:3.24.1-0ubuntu1 What actually happened: When I open settings, I find that my perfectly innocuous Region & Language settings have been kidnapped by a stranger named Lan Guage. I don't know who Mr. Guage is but I would like him to return my settings. What I expected to happen: Find settings app that has not been visited by Lan Guage. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 15:57:59 2017 InstallationDate: Installed on 2017-05-30 (7 days ago) InstallationMedia: System76 17.04 "Zesty Zapus" - Release amd64 (20170410) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1696261/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
Attaching CPU info from two affected Desktop systems. ** Attachment added: "cpuinfo-leox.txt" https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640786/+files/cpuinfo-leox.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: New Status in System76: Triaged Status in llvm-toolchain-3.8 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Bug description: Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs. The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved. I have mesa test packages built against llvm 3.6 here: https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well. My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix. Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug. For concrete examples of System76 hardware effected by this: 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort) Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations. In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg). Also note that so far I've only tested amd64, haven't tested i386. I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu. Old description === Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably oth
[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Second affected system ** Attachment added: "cpuinfo-silw.txt" https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640787/+files/cpuinfo-silw.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: New Status in System76: Triaged Status in llvm-toolchain-3.8 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Bug description: Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs. The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved. I have mesa test packages built against llvm 3.6 here: https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well. My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix. Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug. For concrete examples of System76 hardware effected by this: 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort) Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations. In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg). Also note that so far I've only tested amd64, haven't tested i386. I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu. Old description === Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) A
[Desktop-packages] [Bug 1552798] [NEW] Touchpad on Laptop Can be Disabled on Accident
Public bug reported: In the Mouse and Trackpad Settings plugin, there is an option (when a trackpad is present, e.g. on a laptop) to enable or disable the trackpad. This is a dangerous option because if the setting is toggled on a laptop (where the trackpad is the only built-in pointing device) without first plugging in an external mouse, the trackpad which was used to toggle the setting is disabled and cannot be used to re-enable it. This requires one of three solutions: 1. Plugging in an External Mouse to re-enable the setting 2. Using the [TAB] and [SPACE] keys to navigate the UI and get to the switch and toggle it back on 3. Running a gsettings command in the terminal to reset the option Option 1 may not be available if the user doesn't have an external mouse. Options 2 and 3 aren't discoverable for new users, which can leave someone new to Ubuntu with no way to use their computer. The gsettings key that is toggle by this widget is: org.gnome.desktop.peripherals.touchpad/send-events The key accepts the values "enabled", "disabled", and "disabled-on- external-mouse". The third option would be a much better choice for the disabled item, since that still allows use of the trackpad without an external mouse. The wording of the option could also be updated to something similar to: "Disable touchpad automatically when an external mouse is plugged in". ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 3 09:19:23 2016 SourcePackage: unity-control-center UpgradeStatus: Upgraded to wily on 2016-02-04 (28 days ago) ** Affects: unity-control-center (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 unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1552798 Title: Touchpad on Laptop Can be Disabled on Accident Status in unity-control-center package in Ubuntu: New Bug description: In the Mouse and Trackpad Settings plugin, there is an option (when a trackpad is present, e.g. on a laptop) to enable or disable the trackpad. This is a dangerous option because if the setting is toggled on a laptop (where the trackpad is the only built-in pointing device) without first plugging in an external mouse, the trackpad which was used to toggle the setting is disabled and cannot be used to re-enable it. This requires one of three solutions: 1. Plugging in an External Mouse to re-enable the setting 2. Using the [TAB] and [SPACE] keys to navigate the UI and get to the switch and toggle it back on 3. Running a gsettings command in the terminal to reset the option Option 1 may not be available if the user doesn't have an external mouse. Options 2 and 3 aren't discoverable for new users, which can leave someone new to Ubuntu with no way to use their computer. The gsettings key that is toggle by this widget is: org.gnome.desktop.peripherals.touchpad/send-events The key accepts the values "enabled", "disabled", and "disabled-on- external-mouse". The third option would be a much better choice for the disabled item, since that still allows use of the trackpad without an external mouse. The wording of the option could also be updated to something similar to: "Disable touchpad automatically when an external mouse is plugged in". ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 3 09:19:23 2016 SourcePackage: unity-control-center UpgradeStatus: Upgraded to wily on 2016-02-04 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1552798/+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 1486219] [NEW] Eye of GNOME doesn't display an error if the currently-viewed image is deleted
Public bug reported: Eye of GNOME doesn't display an error if the currently-viewed image is deleted. For example, if you open an image in EoG, close it, delete the image, then attempt to open the image from recent, you will receive an error stating "No images found in 'file:///path/to/image/file.png'." However, if you are currently viewing an image, and delete it from outside of EoG, the the live-update will correctly remove it from display, but EoG remains open and simply displays grey. Using Ubuntu 15.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 18 13:38:57 2015 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- 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/1486219 Title: Eye of GNOME doesn't display an error if the currently-viewed image is deleted Status in eog package in Ubuntu: Confirmed Bug description: Eye of GNOME doesn't display an error if the currently-viewed image is deleted. For example, if you open an image in EoG, close it, delete the image, then attempt to open the image from recent, you will receive an error stating "No images found in 'file:///path/to/image/file.png'." However, if you are currently viewing an image, and delete it from outside of EoG, the the live- update will correctly remove it from display, but EoG remains open and simply displays grey. Using Ubuntu 15.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 18 13:38:57 2015 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1486219/+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 1479524] [NEW] Totem Crashes at launch from missing libwayland-egl
Public bug reported: When trying to open a video file from Ubuntu 14.04.3 Daily Image (2015-07-29), it will not open. If totem is manually run from the terminal, this error occurs: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Using Ubuntu 14.04.3 LTS (Daily Image from: 2015-07-29) 64-bit Totem version: 3.10.1-1ubuntu4 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 29 15:11:30 2015 InstallationDate: Installed on 2015-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150729) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: system76 Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 14.04.3 amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1479524 Title: Totem Crashes at launch from missing libwayland-egl Status in System76: New Status in totem package in Ubuntu: Confirmed Bug description: When trying to open a video file from Ubuntu 14.04.3 Daily Image (2015-07-29), it will not open. If totem is manually run from the terminal, this error occurs: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Using Ubuntu 14.04.3 LTS (Daily Image from: 2015-07-29) 64-bit Totem version: 3.10.1-1ubuntu4 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 29 15:11:30 2015 InstallationDate: Installed on 2015-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150729) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1479524/+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 1188293] [NEW] Terminal window does not retain original window size when un-maximized
Public bug reported: TEST CASE 1. Press Ctrl+Alt+T to open a terminal window. 2. Drag the window to the top panel to maximize it. 3. Restore the window by dragging down from the top panel or using the restore window button. ACTUAL RESULT The terminal window remains large, as if it hadn't been restored (It isn't attached to the screen, though). EXPECTED RESULT The Terminal returns to it's original size. Note that this doesn't happen if the window is maximized using the Maximize window button. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-terminal 3.6.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Thu Jun 6 11:03:12 2013 MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1188293 Title: Terminal window does not retain original window size when un-maximized Status in “gnome-terminal” package in Ubuntu: New Bug description: TEST CASE 1. Press Ctrl+Alt+T to open a terminal window. 2. Drag the window to the top panel to maximize it. 3. Restore the window by dragging down from the top panel or using the restore window button. ACTUAL RESULT The terminal window remains large, as if it hadn't been restored (It isn't attached to the screen, though). EXPECTED RESULT The Terminal returns to it's original size. Note that this doesn't happen if the window is maximized using the Maximize window button. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-terminal 3.6.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Thu Jun 6 11:03:12 2013 MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1188293/+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 1096457] Re: compiz crashed with SIGSEGV in g_type_check_instance_is_a() from unity::launcher::BamfLauncherIcon::UpdateIconGeometries() from unity::launcher::BamfLauncherIcon::
Since this isn't a System76-specific issue, I'm marking this Invalid against System76. ** Changed in: system76 Status: New => Invalid -- 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/1096457 Title: compiz crashed with SIGSEGV in g_type_check_instance_is_a() from unity::launcher::BamfLauncherIcon::UpdateIconGeometries() from unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList() Status in System76: Invalid Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: These types of crashes usually happen shortly after logging in, but in this case, it happened much later. Crashing early doesn't seem to happen with debugging info turned on, as it was for this issue. For more details on this type of crash, please see bug #750386. WORKAROUND: For some of us, this is caused by a corrupt .config/dconf/user file in our home directories. Try removing this file, and report back. Be warned, however, that by removing this file, you will lose many of your desktop environment configuration settings. If this is a concern, rename it and keep it around in case contents of the file are salvageable. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CrashCounter: 1 Date: Sat Jan 5 16:05:46 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2010-10-11 (817 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True ProcCmdline: compiz --replace ProcEnviron: TERM=linux PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7f5669ac469c : testb $0x4,0x16(%rdi) PC (0x7f5669ac469c) ok source "$0x4" ok destination "0x16(%rdi)" (0x567006f73980046) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 unity::launcher::BamfLauncherIcon::UpdateIconGeometries(std::vector, std::allocator > >) () from /usr/lib/compiz/libunityshell.so unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList() () from /usr/lib/compiz/libunityshell.so ?? () Title: compiz crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to quantal on 2012-10-27 (69 days ago) UserGroups: adm admin cdrom dialout lp lpadmin netdev plugdev sambashare whoopsie To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1096457/+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 795458] Re: Display garbled upon connecting external displays
** Changed in: system76 Status: Fix Committed => Fix Released -- 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/795458 Title: Display garbled upon connecting external displays Status in System76: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Natty: Fix Released Bug description: Fixed in natty-proposed Test case: 1. install Unity 3.8.16 2. Plug an external monitor. 3. Choose the resolution of the external monitor in the Monitor Preferences" (System > Preferences > Monitors) With the fglrx driver you have to use Catalyst configuration setting. 4. Verify that the display is not garbled after setting the resolution of the external monitor 5. Unplug the external monitor 6. Verify that the main monitor display returns to a single monitor configuration = Multiple monitor case - Plugging or unplugging an external monitor Display garbled problem observed when plugging in an external display: the corruption happens when connecting the external monitor, and can be restored by dragging things around. When unplugging the external display, the integrated screen becomes garbled as described. This issue is part of bug https://bugs.launchpad.net/ubuntu/+source/unity/+bug/753971 To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/795458/+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
