[Desktop-packages] [Bug 1322418] [NEW] System Settings menu disabled by removing Bluetooth Transfer
Public bug reported: If I go into the Ubuntu Software Center, then click on the "Installed" tab, then remove "Bluetooth Transfer" under "Accessories", a window comes up saying that I must also remove "User level public file sharing..." and "System bluetooth indicator". I click "Remove All". After the removal completes (might take a minute or more), the System Settings item on the "gear" menu is no longer accessible. I reproduced this on 2 very different machines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Thu May 22 23:45:32 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-05-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.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-0ubuntu14 deja-dup 30.0-0ubuntu4 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1322418 Title: System Settings menu disabled by removing Bluetooth Transfer Status in “unity-control-center” package in Ubuntu: New Bug description: If I go into the Ubuntu Software Center, then click on the "Installed" tab, then remove "Bluetooth Transfer" under "Accessories", a window comes up saying that I must also remove "User level public file sharing..." and "System bluetooth indicator". I click "Remove All". After the removal completes (might take a minute or more), the System Settings item on the "gear" menu is no longer accessible. I reproduced this on 2 very different machines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Thu May 22 23:45:32 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-05-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.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-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1322418/+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 1322413] [NEW] Radeon HD 8670M sets wrong color depth
Public bug reported: First of all, I disabled my computer by attempting to fix this, so unfortunately the hardware summary attached to this report is from an unrelated machine. The problem is that when Ubuntu 14.04 boots, it sets a low color depth. This is visible because the default purple desktop background has stairstep color shading with dithering. I attempted to fix this by copying /etc/X11/xorg.conf.failsafe to /etc/X11/xorg.conf and inserting "DefaultDepth 24" before the last "EndSection". Plain vanilla 14.04 can't boot this video chip at all. You need this fix before you can see the above bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1301839 If this can't or won't be fixed, then please inform as to how we should modify xorg.conf or whatever in order to get decent 24 or 32-bit depth. In particular, at 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 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: Thu May 22 23:25:47 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be2] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84a9] InstallationDate: Installed on 2014-05-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: ASUSTeK COMPUTER INC. 1025C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c820310c-64d5-4b7e-930e-c0e07083008a ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1025C.0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1025C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1025C.0701:bd01/06/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x: dmi.product.name: 1025C dmi.product.version: x.x dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 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 May 22 22:48:47 2014 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: modesetting ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 resolution 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/1322413 Title: Radeon HD 8670M sets wrong color depth Status in “xorg” package in Ubuntu: New Bug description: First of all, I disabled my computer by attempting to fix this, so unfortunately the hardware summary attached to this report is from an unrelated machine. The problem is that when Ubuntu 14.04 boots, it sets a low color depth. This is visible because the default purple desktop background has stairstep color shading with dithering. I attempted to fix this by copying /etc/X11/xorg.conf.failsafe to /etc/X11/xorg.conf and inserting "DefaultDepth 24" before the last "EndSection". Plain vanilla 14.04 can't boot this video chip at all. You need this fix before you can see the above bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1301839 If this can't or won't be fixed, then please inform as to how we should modify xorg.conf or whatever in order to get decent 24 or 32-bit depth. In particular, at 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Pr
[Desktop-packages] [Bug 1301839] Re: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty
This bug seems to be half fixed. After a fresh 14.04 install, I do "sudo apt-get update" followed by "sudo apt-get upgrade". Then, the desktop is usable. However, it appears to have low color density because the default purple background shades are all stair-stepped and dithered. I'm positive it's not the Ubuntu desktop background that's at fault, because it looks great on a much older machine. Perhaps there's a workaround through the command line, but this should not be the default behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty Status in X.org XServer - ATI gfx chipset driver: Fix Released Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Status in “xserver-xorg-video-ati” source package in Trusty: Fix Released Status in “xserver-xorg-video-intel” source package in Trusty: Invalid Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * Try to boot to the desktop with 14.04 - Working: Desktop works fine - Bad behavior: You will be ask to run on low-graphic mode, or you will need to add "nomodeset" parameter into grub to boot normally. [Regression Potential] * Low, patches have been taken from upstream. Most likely manifests itself with crash and/or hangs. [Other info] Commits c84230d686c078aac1dc98d82153f8b02521b2e1 and cadb6b493942a84bfeb298751dce0dee39257a06 upstream. [Original bug report] CID: 201305-13624 - AMD Radeon HD 8670A/8670M/8690M[1002:6660] CID: 201309-14197 - AMD Radeon HD 8570A/8570M[1002:6663] This system cannot boot to desktop by "Try Ubuntu" option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add "nomodeset" parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 1
[Desktop-packages] [Bug 1321091] [NEW] readdir function returns inconsistent d_type
Public bug reported: Due to lack of time, I can't investigate this, but I repeatedly observed it. Basically, when you call readdir, it returns a struct dirent. The d_type field is supposed to be DT_LNK for symbolic links when _DIRENT_HAVE_D_TYPE is known to the compiler (which it is). This is usually true, for example /usr/bin/X11 is a circularly-referential symbolic link with DT_LNK asserted. But when I install an Ubuntu 14.04 64-bit desktop image to a USB stick (using either Startup Disk Creator or the Disk utility, sorry I don't recall), I get a similar circularly- referential directory called "ubuntu". This symbolic link does not have DT_LNK set. lstat can get around this problem and see the link attribute, but the bug here is that d_type is not the expected value. I based all this on "man readdir", so it might be just a doc bug. By "circularly referential", I mean a symbolic link to "." (current folder). ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- 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/1321091 Title: readdir function returns inconsistent d_type Status in “gnome-terminal” package in Ubuntu: New Bug description: Due to lack of time, I can't investigate this, but I repeatedly observed it. Basically, when you call readdir, it returns a struct dirent. The d_type field is supposed to be DT_LNK for symbolic links when _DIRENT_HAVE_D_TYPE is known to the compiler (which it is). This is usually true, for example /usr/bin/X11 is a circularly-referential symbolic link with DT_LNK asserted. But when I install an Ubuntu 14.04 64-bit desktop image to a USB stick (using either Startup Disk Creator or the Disk utility, sorry I don't recall), I get a similar circularly-referential directory called "ubuntu". This symbolic link does not have DT_LNK set. lstat can get around this problem and see the link attribute, but the bug here is that d_type is not the expected value. I based all this on "man readdir", so it might be just a doc bug. By "circularly referential", I mean a symbolic link to "." (current folder). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1321091/+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 1321090] [NEW] GLib-CRITICAL g_slice_set_config: assertion
Public bug reported: I don't know where else to go with this. I've gotten them a few times now in terminal. The process number associated with this error message points back to this Firefox session, which was launched because I used ubuntu-bug -w to try to report another bug. So I changed my plans and reported this bug instead. I'm not sure how much ubuntu-bug -w has to do with it, though. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 20 01:00:29 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-18 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1321090 Title: GLib-CRITICAL g_slice_set_config: assertion Status in “gnome-terminal” package in Ubuntu: New Bug description: I don't know where else to go with this. I've gotten them a few times now in terminal. The process number associated with this error message points back to this Firefox session, which was launched because I used ubuntu-bug -w to try to report another bug. So I changed my plans and reported this bug instead. I'm not sure how much ubuntu-bug -w has to do with it, though. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 20 01:00:29 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-18 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1321090/+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 1320648] [NEW] Randomly ignored keystrokes in terminal
Public bug reported: I was just trying to install 64-bit 14.04 LTS. Due to a video bug in the default installation image, I had to boot to a terminal instead of the usual Unity GUI. The video bug is actually fixed already, but I needed to download it. So I just did "sudo apt-get update" followed by "sudo apt-get upgrade". After the latter command, the keyboard (both internal and external) could only get keys through to the terminal about 40% of the time. In other words, I would need to press the same letter 2 or 3 times before it would appear on the screen. What's worse, the actual command that the terminal received was different than both (1) what I actually typed and (2) what appeared on the screen. So for example, I would type "poweroff" as "pwweeeroff". It would appear as "poweroff", but then the terminal would complain that there was no such command as "ppooweroofff". I finally gave up and rebooted. Everything works fine now, even in a terminal. But I've repeated this experiment a few times, immediately after a fresh install, and it always happens. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 18 10:33:06 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-18 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1320648 Title: Randomly ignored keystrokes in terminal Status in “gnome-terminal” package in Ubuntu: New Bug description: I was just trying to install 64-bit 14.04 LTS. Due to a video bug in the default installation image, I had to boot to a terminal instead of the usual Unity GUI. The video bug is actually fixed already, but I needed to download it. So I just did "sudo apt-get update" followed by "sudo apt-get upgrade". After the latter command, the keyboard (both internal and external) could only get keys through to the terminal about 40% of the time. In other words, I would need to press the same letter 2 or 3 times before it would appear on the screen. What's worse, the actual command that the terminal received was different than both (1) what I actually typed and (2) what appeared on the screen. So for example, I would type "poweroff" as "pwweeeroff". It would appear as "poweroff", but then the terminal would complain that there was no such command as "ppooweroofff". I finally gave up and rebooted. Everything works fine now, even in a terminal. But I've repeated this experiment a few times, immediately after a fresh install, and it always happens. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 18 10:33:06 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-18 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1320648/+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
