[Desktop-packages] [Bug 1875991] [NEW] Screen unlocks without password
Public bug reported: I think this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1870803 however, I can't find out to add my machine information to it. A little more information I can add - not sure if it's the same for original reporter - when I first log into my account I get some sort of notification about gnome-screensaver not being enabled because gnome isn't installed; or something to that effect. This started upon upgrade to Focal. TLDR: If I lock my account using the gnome-menu, then press ctrl+alt+F7, it immediately goes to my session without needing to type a password, bypassing all security. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 29 16:25:35 2020 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2016-04-29 (1461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-19 (41 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1875991 Title: Screen unlocks without password Status in gnome-screensaver package in Ubuntu: New Bug description: I think this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1870803 however, I can't find out to add my machine information to it. A little more information I can add - not sure if it's the same for original reporter - when I first log into my account I get some sort of notification about gnome-screensaver not being enabled because gnome isn't installed; or something to that effect. This started upon upgrade to Focal. TLDR: If I lock my account using the gnome-menu, then press ctrl+alt+F7, it immediately goes to my session without needing to type a password, bypassing all security. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 29 16:25:35 2020 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2016-04-29 (1461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1875991/+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 982742] Re: Open file dialogue forgets sorting preferences
Looks like it's been fixed at some point -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/982742 Title: Open file dialogue forgets sorting preferences Status in chromium-browser package in Ubuntu: Incomplete Bug description: Not sure if this is a chromium issue, or nautilus, but the open file dialogue does not remember sorting preferences. Steps to reproduce: - Go to a page that requires a file upload - Click upload, the select file dialogue should display - Sort the entries by last accessed - Close the dialogue. - Open the dialogue again. Expected results - The dialogue should retain the sorting preferences Actual results - The dialogue always sorts by name. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 20:51:23 2012 Desktop-Session: DESKTOP_SESSION = gnome-shell XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-shell:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome-shell:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-04-02 (13 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/982742/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
After going on the #radeon channel on Freenode, we narrowed the problem down to the switcheroo-control package. We started by hand making an xorg.conf file and disabling gpu-manager, but still had issues. Looking at the dmesg log, we saw that the discrete gpu is enabled at first, then disabled sometime in the systemd start up. After trying to disable various things, including switcheroo, from the kernel parameters and having the problem still occur, we narrowed it down to being a service that was writing to `/sys/kernel/debug/vgaswitcheroo/switch`. I looked at my enabled services, and saw `switcheroo-control`, after disabling, everything started working again. Given that the package was integrated into gnome in late 2016 [0][1], it lines up timewise with when I started having problems. [0] https://askubuntu.com/questions/1034882/gnome-does-not-show-the-option-to-use-dedicated-graphics-card-on-right-click [1] http://www.hadess.net/2016/10/dual-gpu-integration-in-gnome.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: Invalid Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: Invalid Status in switcheroo-control package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Also affects: switcheroo-control (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New => Invalid ** Changed in: lightdm Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: Invalid Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: Invalid Status in switcheroo-control package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Attachment added: "xorg log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235697/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
Added gpu-manager log It says "Unsupported discrete card vendor: 1002", Does this mean my discrete card is no longer supported? ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235683/+files/gpu-manager.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
I filmed my computer boot up to better show what happens. The right monitor is on the integrated video card (the R7), and doesn't show anything initially. The center and left monitor turn on and mirror each other during boot, and show grub and most of the kernel and systemd messages, then at some point all output is sent to the right monitor. I believe the systemd log says something along the lines of "detecting all video cards" at that point. ** Attachment added: "Computerbootup.webm" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235238/+files/Computerbootup.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235234/+files/dmesg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
I've come across this again after upgrading to 18.10 $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:KAVERI @ pci::00:01.0 $ sudo lspci -nn | grep -E 'VGA|Display' [sudo] password for richard: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] Only the built-in Radeon R7 is being used ** Changed in: lightdm Status: Invalid => New ** Changed in: lightdm (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 955546] Re: gnome-terminal crashes with forked command not found if path is too long
No worries. I can't reproduce it any more, I assume it was fixed at some point. -- 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/955546 Title: gnome-terminal crashes with forked command not found if path is too long Status in command-not-found package in Ubuntu: Incomplete Status in gnome-terminal package in Ubuntu: Incomplete Bug description: The affected package could also be the command-not-found package. There seems to be a bug with the way either gnome-terminal or command- not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path. My testcase (which may have to be fiddled with): ~$ mkdir 123456789012345678 ~$ cd 123456789012345678 ~/123456789012345678$ pwd /home/redbrick/123456789012345678 ~/123456789012345678$ a& * gnome-terminal crashes * I've reproduced this on three different machines. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 14 15:55:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/command-not-found/+bug/955546/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
Is there anything I can do to move this along? I'm fairly certain it's a kernel or driver issue since zesty since I'm currently running 16.04 on live USB and all three monitors work just fine. I've tried using the 4.8 kernel from yakkety, but I couldn't get it to boot, I'm assuming it was compiled specifically for yakkety. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: New Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1590661] Re: Unable to unlock: "Time has expired"
I just saw this on 17.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1590661 Title: Unable to unlock: "Time has expired" Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Sometimes when coming back after locking the screen I am unable to unlock. The login box on the screen has a disabled password input field with the buttons also disabled. Except for the mouse, the entire screen is frozen. Even the time in the top of the screen stops going. The only way to continue is to move to a tty (Ctrl-Alt-F1), log in and kill gnome-screensaver. Since the time also stops going I have deduced that this seems to happen on days and times that correspond to when the cleaners are here. Because of this I speculate that they accidentally press some keys, including the enter key. This of course fails to unlock and after a certain timeout it then proceeds to freeze. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 9 08:59:15 2016 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2016-05-27 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1590661/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
Some more information: - If I switch my primary display adapter in BIOS to the onboard GPU, I can get all three monitors and two cards working, but the framerate on the monitors attached to the PEG GPU is so low that it's almost unusable. - If I set the PEG GPU as primary display adapter, all three monitors work until it gets to the lightdm greeter where only the monitor attached to the integrated gpu works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: New Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
I'm beginning to think this is a driver issue. I have a builtin "Kaveri" amd gpu, and pci Radeon HD 4850. I usually have the 4850 as my primary card/monitor setup. However, since upgrading to Ubuntu 17.04, once lightdm is started, only the monitor on the Kaveri works. I dropped to VT1, and ran `X -configure` after shutting lightdm down, and received an error: amdgpu_device_initialize: DRM version is 2.49.0 but this driver is only compatible with 3.x.x -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: New Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
lspci and lshw show 2 GPUs. The builtin one, and the actual card, but xrandr only lists one provider. $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:KAVERI @ pci::00:01.0 Might be a bug in the radeon driver? ** Also affects: lightdm Importance: Undecided Status: New ** Also affects: xserver-xorg-driver-radeonhd Importance: Undecided Status: New ** Attachment added: "lspci -vvv" https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1692437/+attachment/4881502/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: New Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Attachment added: "lshw output" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/4881175/+files/lshw.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+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 1692437] [NEW] Monitors on second GPU not working after upgrade to zesty
Public bug reported: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+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 1400206] Re: Chromium hangs: GPU process hung
@Chris: I'm not 100% sure, for my home machine it was either a Radeon HD 4850 or a Radeon R7 200 series. I think this bug was "fixed" on both machines once I upgraded to Ubuntu 15.10. (Although on my work machine 15.10 caused a different system freeze bug starting with that release that didn't fix until I changed the graphics card again.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS="" modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] Re: Chromium hangs: GPU process hung
@Olivier: No, I haven't seen this bug in a while since I changed my video cards. (I do still see the tooltip graphical artefacts when hovering over the tabs, but it doesn't lock my browser.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS="" modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1543782] Re: Complete system freeze some time after lock screen starts
I think this is/was either a bug in the radeon driver, or a faulty graphics card. (however, it was only triggered when on the lightdm gtk greeter screen). I've replaced my card with another one, and no longer have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after lock screen starts Status in LightDM GTK+ Greeter: New Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1543782/+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 1543782] Re: Complete system freeze some time after lock screen starts
The only note-worthy log entries I see in that folder are in x-0-greeter.log, and I'm not 100% sure they're related to this bug, I've attached the log file. I have just managed to reproduce this again: 1) I sshed into my machine from another machine to verify when my machine crashes 2) On my machine I hit ctrl+alt+L to start the lock screen 3) Waited a few minutes (not sure how long I actually need to wait) 4) pressed the num lock key At that point, the LED lights on my keyboard and mouse turned off, and the monitors displayed the "not connected" message. On the machine that I used to ssh with, the terminal had frozen. The reason I assigned this to lightdm is because I've reproduced this bug on the greeter screen where (I think) it's the only thing running, and it crashes the greeter leaving just the background image/colour displaying. ** Attachment added: "x-0-greeter.log" https://bugs.launchpad.net/ubuntu-gnome/+bug/1543782/+attachment/4648181/+files/x-0-greeter.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after lock screen starts Status in Light Display Manager: Incomplete Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1543782/+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 1543782] Re: Complete system freeze some time after lock screen starts
I have a new computer, and installed a new copy of Ubuntu 16.04 on it, and I still get this issue. It's most likely related something new added in 15.10 that is still causing issues in 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after lock screen starts Status in Light Display Manager: New Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1543782/+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 1543782] Re: Complete system freeze some time after lock screen starts
As an experiment, I tried logging out of my account and leaving it (over the weekend). When I came back, the computer had frozen, and all the login UI had disappeared. Perhaps a bug in X or lightdm? ** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after lock screen starts Status in Light Display Manager: New Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1543782/+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 1543782] Re: Complete system freeze some time after some inactivity
Another interesting data point: Last week I disabled the screensaver + monitor turning off, and instead of locking the screen, I just turned my monitors off, when I got to work this morning, my computer hadn't frozen. So, this bug appears to be related to the lock screen. I'm not sure what I'm using for a lock screen, to start it I've used both `dm- tool lock` and ctrl+alt+L, both cause my computer to freeze. ** Summary changed: - Complete system freeze some time after some inactivity + Complete system freeze some time after lock screen starts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after lock screen starts Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1543782/+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 1543782] Re: Complete system freeze some time after some inactivity
Probably not DPMS related, I tried disabling my monitor turning off, and my computer still froze. Not sure what to do next. ** Summary changed: - Complete system freeze some time after screensaver starts. + Complete system freeze some time after some inactivity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after some inactivity Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1543782/+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 1543782] Re: Complete system freeze some time after screensaver starts.
Not directly related to gnome-screensaver since I uninstalled it, and it still crashed. Possibly related to the power management service, but not sure. ** Also affects: ubuntu-gnome Importance: Undecided Status: New ** Changed in: gnome-screensaver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after screensaver starts. Status in Ubuntu GNOME: New Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1543782/+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 1543782] Re: Complete system freeze some time after screensaver starts.
** Attachment added: "output of journalctrl" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1543782/+attachment/4568112/+files/journal.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1543782 Title: Complete system freeze some time after screensaver starts. Status in gnome-screensaver package in Ubuntu: New Bug description: Ever since updating to 15.10 my computer has been freezing every day. Usually this happens after I've left work, and since I leave my computer on, I manually start the screensaver (ctrl+alt+L), and when I come back the next morning, the computer is completely unresponsive, even to sysrq. Gnome screensaver itself doesn't appear to be the culprit since I can turn it on, then log back into my system any time within perhaps 5 minutes. Looking at my root journalctrl output, yesterday, it appears to have crashed 30 minutes after I logged out (I was zeroing a drive with dd, and was issuing a kill -USR1 to track the progress every 30 seconds). At first I thought it might be a botched upgrade from 15.04, so I tried a clean reinstall last week, but it still freezes. There is also nothing in the logs that would indicate an error/crash. The only potentially related piece of information is that I use gnome- shell, installed via ubuntu-gnome-desktop. I'm not sure what package to file this under since I don't know how to reproduce, or how to diagnose the issue. Any debugging advice will be appreciated since this issue is really starting to annoy me. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-screensaver 3.6.1-7ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:20:44 2016 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2016-02-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1543782/+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 1487082] [NEW] Loading icon doesn't match (gtk) theme
Public bug reported: The loading spinner in the tabs no longer matches the theme as of the version 44 update. Attached is part of a screen shot that shows the spinner with the default blue theme, whereas the rest of the application uses my gtk theme. Before the last update, the spinner was a dark grey. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: chromium-browser 44.0.2403.89-0ubuntu0.15.04.1.1177 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.3 Architecture: amd64 CurrentDesktop: GNOME DRM.card0.DVI.D.1: edid-base64: AP///wAebdlWJZoAAAwVAQOANR546q7FoldKnCUSUFSna4CzAIGAgUBxTwEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4Sx5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgAL8= dpms: On modes: 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0.VGA.1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card1.DIN.1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected Date: Thu Aug 20 08:47:19 2015 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2014-08-21 (364 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Load-Avg-1min: 2.72 Load-Processes-Running-Percent: 0.8% MachineType: MSI MS-7721 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=9b43238c-d6b1-4285-ac61-d8fe87d66d35 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to vivid on 2015-04-07 (134 days ago) dmi.bios.date: 03/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V30.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E35 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 6.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV30.3:bd03/14/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0: dmi.product.name: MS-7721 dmi.product.version: 6.0 dmi.sys.vendor: MSI gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: tab-spinner.png https://bugs.launchpad.net/bugs/1487082/+attachment/4449561/+files/tab-spinner.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1487082 Title: Loading icon doesn't match (gtk) theme Status in chromium-browser package in Ubuntu: New Bug description: The loading spinner in the tabs no longer matches the theme as of the version 44 update. Attached is part of a screen shot that shows the spinner with the default blue theme, whereas the rest of the application uses my gtk theme. Before the last update, the spinner was a dark grey. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: chromium-browser 44.0.2403.89-0ubuntu0.15.04.1.1177 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.3 Architecture: amd64 CurrentDesktop: GNOME DRM.card0.DVI.D.1: edid-base64: AP///wAebdlWJZoAAAwVAQOANR546q7FoldKnCUSUFSna4CzAIGAgUBxTwEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4Sx5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgAL8= dpms: On modes: 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0.VGA.1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card1.DIN.1: edid-base64: dpms: Off modes: enabled: disabled status:
[Desktop-packages] [Bug 1453442] Re: Destination folder (null) does not exist when dragging over chromium
Can the fix be back ported so I don't have to wait until October for it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1453442 Title: Destination folder (null) does not exist when dragging over chromium Status in file-roller package in Ubuntu: Fix Released Bug description: Steps to reproduce: - Open an archive with the file-roller gui - Place the window over top of chromium - Open a nautilus window - Drag the contents of file-roller (to extract them) over to the nautilus window making sure that the dragged content passes over the chromium window. Expected Results: - Nothing should happen until I drop the contents onto the nautilus window at which point the content is extracted Actual Results: - An error message pops up: Destination folder (null) does not exist. Do you want to create it ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: file-roller 3.14.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:04:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: file-roller UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1453442/+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 1447701] Re: Backport chromium-browser 43
Yay, looks like this got pushed through! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1447701 Title: Backport chromium-browser 43 Status in chromium-browser package in Ubuntu: Confirmed Bug description: Now that Ubuntu 15.10 has had chromium upgraded to version 43 (current stable), can we have it backported to Utopic and Vivid? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1447701/+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 1447701] Re: Backport chromium-browser 43
Correction, Wily has version 42, but I see that debian jessie has version 43. Can we get version 43 across the board? ** Summary changed: - Upgrade chromium-browser to 42 + Backport chromium-browser 43 ** Description changed: - Can we get an upgrade to version 42 now that it's the stable version? + Now that Ubuntu 15.10 has had chromium upgraded to version 43 (current + stable), can we have it backported to Utopic and Vivid? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1447701 Title: Backport chromium-browser 43 Status in chromium-browser package in Ubuntu: Confirmed Bug description: Now that Ubuntu 15.10 has had chromium upgraded to version 43 (current stable), can we have it backported to Utopic and Vivid? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1447701/+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 1461278] Re: Chromium is outdated
*** This bug is a duplicate of bug 1447701 *** https://bugs.launchpad.net/bugs/1447701 ** This bug has been marked a duplicate of bug 1447701 Upgrade chromium-browser to 42 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1461278 Title: Chromium is outdated Status in chromium-browser package in Ubuntu: New Bug description: Chromium is way outdated. This is kinda annoying, especially because it has a nasty bug related to HiDPI support. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: chromium-browser 41.0.2272.76-0ubuntu1.1134 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0.DP.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.eDP.1: edid-base64: AP///wBNEAYUAAAXAQSlHRF4Bt5Qo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBVl4AoKCgKVAwIDUAJqUQAAAYEAAAEAAA/ABMUTEzM1QxSlcxNAogAKU= dpms: On modes: 2560x1440 enabled: enabled status: connected Date: Wed Jun 3 00:15:29 2015 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2015-05-06 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Load-Avg-1min: 0.25 Load-Processes-Running-Percent: 0.1% MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 pcie_aspm=force acpi_osi= vt.handoff=7 SourcePackage: chromium-browser UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. gconf-keys: /desktop/gnome/applications/browser/exec = b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command = b'/opt/google/chrome/google-chrome %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/opt/google/chrome/google-chrome %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1461278/+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 1453442] Re: Destination folder (null) does not exist when dragging over chromium
@victor, I can't replicate that with my tri-monitor setup, so it must be a different bug (with same symptoms perhaps). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1453442 Title: Destination folder (null) does not exist when dragging over chromium Status in file-roller package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Open an archive with the file-roller gui - Place the window over top of chromium - Open a nautilus window - Drag the contents of file-roller (to extract them) over to the nautilus window making sure that the dragged content passes over the chromium window. Expected Results: - Nothing should happen until I drop the contents onto the nautilus window at which point the content is extracted Actual Results: - An error message pops up: Destination folder (null) does not exist. Do you want to create it ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: file-roller 3.14.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:04:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: file-roller UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1453442/+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 1400206] Re: Chromium hangs: GPU process hung
The apport window that pops up after crashes lists this bug as a duplicate of https://bugs.launchpad.net/bugs/1402523 which does not exist. One thing I do notice that crashes it: if I hover over the tab name, the tooltip will sometimes stay and become a white rectangle, if I then try to show another tooltip on the tab name, the browser locks up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1453443] Re: Daily backup does not run daily
Yes, that seems to be the case for the buttons; there was a process running in the background. So the latter part of this report would be that it's not finishing, not notifying of errors, and doesn't provide a way to cancel/restart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1453443 Title: Daily backup does not run daily Status in duplicity package in Ubuntu: New Bug description: I have the duplicity backup scheduled to run every day, yet it has not run in 6 days. What's more, the buttons to Restore.. and Back Up Now... are disabled. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: duplicity 0.7.01-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:10:47 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: duplicity UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1453443/+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 1453442] [NEW] Destination folder (null) does not exist when dragging over chromium
Public bug reported: Steps to reproduce: - Open an archive with the file-roller gui - Place the window over top of chromium - Open a nautilus window - Drag the contents of file-roller (to extract them) over to the nautilus window making sure that the dragged content passes over the chromium window. Expected Results: - Nothing should happen until I drop the contents onto the nautilus window at which point the content is extracted Actual Results: - An error message pops up: Destination folder (null) does not exist. Do you want to create it ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: file-roller 3.14.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:04:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: file-roller UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1453442 Title: Destination folder (null) does not exist when dragging over chromium Status in file-roller package in Ubuntu: New Bug description: Steps to reproduce: - Open an archive with the file-roller gui - Place the window over top of chromium - Open a nautilus window - Drag the contents of file-roller (to extract them) over to the nautilus window making sure that the dragged content passes over the chromium window. Expected Results: - Nothing should happen until I drop the contents onto the nautilus window at which point the content is extracted Actual Results: - An error message pops up: Destination folder (null) does not exist. Do you want to create it ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: file-roller 3.14.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:04:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: file-roller UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1453442/+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 1453443] [NEW] Daily backup does not run daily
Public bug reported: I have the duplicity backup scheduled to run every day, yet it has not run in 6 days. What's more, the buttons to Restore.. and Back Up Now... are disabled. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: duplicity 0.7.01-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:10:47 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: duplicity UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1453443 Title: Daily backup does not run daily Status in duplicity package in Ubuntu: New Bug description: I have the duplicity backup scheduled to run every day, yet it has not run in 6 days. What's more, the buttons to Restore.. and Back Up Now... are disabled. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: duplicity 0.7.01-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 9 13:10:47 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (261 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: duplicity UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1453443/+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 1447701] [NEW] Upgrade chromium-browser to 42
Public bug reported: Can we get an upgrade to version 42 now that it's the stable version? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1447701 Title: Upgrade chromium-browser to 42 Status in chromium-browser package in Ubuntu: New Bug description: Can we get an upgrade to version 42 now that it's the stable version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1447701/+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 1400206] Re: Chromium hangs: GPU process hung
Possible related bugs: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220 https://code.google.com/p/chromium/issues/detail?id=293008 https://code.google.com/p/chromium/issues/detail?id=418858 https://code.google.com/p/chromium/issues/detail?id=389816 https://code.google.com/p/chromium/issues/detail?id=427909 https://code.google.com/p/chromium/issues/detail?id=400043 ** Bug watch added: code.google.com/p/chromium/issues #293008 http://code.google.com/p/chromium/issues/detail?id=293008 ** Bug watch added: code.google.com/p/chromium/issues #418858 http://code.google.com/p/chromium/issues/detail?id=418858 ** Bug watch added: code.google.com/p/chromium/issues #389816 http://code.google.com/p/chromium/issues/detail?id=389816 ** Bug watch added: code.google.com/p/chromium/issues #427909 http://code.google.com/p/chromium/issues/detail?id=427909 ** Bug watch added: code.google.com/p/chromium/issues #400043 http://code.google.com/p/chromium/issues/detail?id=400043 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1292398] Re: Second screen position isn't saved from one session to another
This issue resolved for me with Ubuntu 14.10, but I seem to be the only one for whom it did -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Won't Fix Status in Gnome Settings Daemon: New Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1400206] Re: Chromium hangs: GPU process hung
apport information ** Tags added: apport-collected ** Description changed: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] + --- + ApportVersion: 2.14.7-0ubuntu8.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 14.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2012-02-16 (1083 days ago) + InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) + Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 + Tags: utopic + Uname: Linux 3.11.0-14-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + _MarkForUpload: True + modified.conffile..etc.chromium.browser.default: + # Default settings for chromium-browser. This file is sourced by /bin/sh from + # /usr/bin/chromium-browser + . /usr/lib/pepflashplugin-installer/pepflashplayer.sh + # Options to pass to chromium-browser + CHROMIUM_FLAGS= + modified.conffile..etc.default.chromium.browser: [deleted] + mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1400206/+attachment/4312306/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty
[Desktop-packages] [Bug 1400206] HookError_chromium_browser.txt
apport information ** Attachment added: HookError_chromium_browser.txt https://bugs.launchpad.net/bugs/1400206/+attachment/4312307/+files/HookError_chromium_browser.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] Re: Chromium hangs: GPU process hung
This is one of the most irritating bugs I've come across. At the moment it's happening nearly every day on both my work and my home computers. I just added additional information from my work computer in case it's useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1400206/+attachment/4312309/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] RelatedPackagesPolicy.txt
apport information ** Attachment added: RelatedPackagesPolicy.txt https://bugs.launchpad.net/bugs/1400206/+attachment/4312310/+files/RelatedPackagesPolicy.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1400206/+attachment/4312308/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: Confirmed Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-16 (1083 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: utopic Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-04 (91 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1400206] [NEW] Chromium hangs: GPU process hung
Public bug reported: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: lspci -vvv https://bugs.launchpad.net/bugs/1400206/+attachment/4275944/+files/pci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1400206 Title: Chromium hangs: GPU process hung Status in chromium-browser package in Ubuntu: New Bug description: Starting with a recent update to either my graphics card, or to chromium, it (chromium) will seem to hang after resuming from a lock screen. By hang, I mean it seems to refuse to redraw since it still responds to mouse clicks on the close button. Here's the stderr output on console: ATTENTION: default value of option force_s3tc_enable overridden by environment. [11795:11795:1207/210031:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [11759:11806:1207/210033:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [11795:11828:1207/211957:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [12793:12794:1207/212007:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 1 ms. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [11759:11759:1207/212008:ERROR:gpu_process_transport_factory.cc(461)] Lost UI shared context. [11759:11806:1207/220155:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 7 22:21:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-21 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: chromium-browser UpgradeStatus: Upgraded to utopic on 2014-11-05 (32 days ago) modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1400206/+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 1356621] [NEW] Chromium created /use directory
Public bug reported: I think this is probably a typo in the packaging; chromium created a /use directory that I expect is supposed to be /usr $ dpkg -S /use chromium-browser: /use $ ls /use share $ ls /use/share/ icons $ ls /use/share/icons/ hicolor $ ls /use/share/icons/hicolor/ scalable $ ls /use/share/icons/hicolor/scalable/ apps $ ls /use/share/icons/hicolor/scalable/apps/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.58-0ubuntu1~ppa1~trusty1 [origin: LP-PPA-saiarcot895-chromium-beta] ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Aug 13 16:51:04 2014 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = /home/redbrick/.gvm/pkgsets/go1.2.1/global/overlay/lib: InstallationDate: Installed on 2012-02-16 (909 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to trusty on 2014-04-21 (114 days ago) chromium-default: . /usr/lib/pepflashplugin-installer/pepflashplayer.sh CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser . /usr/lib/pepflashplugin-installer/pepflashplayer.sh # Options to pass to chromium-browser CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-07-14T09:22:20.527190 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1356621 Title: Chromium created /use directory Status in “chromium-browser” package in Ubuntu: New Bug description: I think this is probably a typo in the packaging; chromium created a /use directory that I expect is supposed to be /usr $ dpkg -S /use chromium-browser: /use $ ls /use share $ ls /use/share/ icons $ ls /use/share/icons/ hicolor $ ls /use/share/icons/hicolor/ scalable $ ls /use/share/icons/hicolor/scalable/ apps $ ls /use/share/icons/hicolor/scalable/apps/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.58-0ubuntu1~ppa1~trusty1 [origin: LP-PPA-saiarcot895-chromium-beta] ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Aug 13 16:51:04 2014 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = /home/redbrick/.gvm/pkgsets/go1.2.1/global/overlay/lib: InstallationDate: Installed on 2012-02-16 (909 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to trusty on 2014-04-21 (114 days ago) chromium-default: . /usr/lib/pepflashplugin-installer/pepflashplayer.sh CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser .
[Desktop-packages] [Bug 1097125] Re: chromium-browser has min/max/close buttons at upper right
Workaround: gconftool-2 --set /apps/metacity/general/button_layout --type string close,minimize,maximize: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1097125 Title: chromium-browser has min/max/close buttons at upper right Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: In prior releases of chromium-browser, the minimize/maximize/close cluster of 3 buttons were always at the upper left as per Ubuntu standard layout. In Ubuntu 12.10, for some reason, this 3 button cluster has been moved to the upper right. It is disturbing. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 ChromiumPrefs: can't open profile /home/peterzay/.config/chromium/Default/Preferences Date: Mon Jan 7 22:45:02 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-01-04 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+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 859101] Re: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h)
The bug is still present with ubuntu 13.10: amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64 fglrx_8.970-0ubuntu1_amd64 Linux 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/859101 Title: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h) Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-experimental-12” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: attempting to install ATI proprietry drivers ProblemType: Package DistroRelease: Ubuntu 11.10 Package: fglrx 2:8.881-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 DKMSBuildLog: DKMS make.log for fglrx-8.881 for kernel 3.0.0-11-generic (i686) Sun Sep 25 19:46:44 BST 2011 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.0.0-11-generic/build/include not found or incomplete file: /lib/modules/3.0.0-11-generic/build/include/linux/version.h DKMSKernelVersion: 3.0.0-11-generic Date: Sun Sep 25 19:46:48 2011 DuplicateSignature: DKMS make.log for fglrx-8.881 for kernel 3.0.0-11-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.0.0-11-generic/build/include not found or incomplete file: /lib/modules/3.0.0-11-generic/build/include/linux/version.h InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.1) PackageVersion: 2:8.881-0ubuntu2 SourcePackage: fglrx-installer Title: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/859101/+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 1097125] Re: chromium-browser has min/max/close buttons at upper right
No, it's using chromium's title bar. See attached screenshot. ** Attachment added: chromium titlebar.png https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+attachment/3754594/+files/chromium%20titlebar.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1097125 Title: chromium-browser has min/max/close buttons at upper right Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: In prior releases of chromium-browser, the minimize/maximize/close cluster of 3 buttons were always at the upper left as per Ubuntu standard layout. In Ubuntu 12.10, for some reason, this 3 button cluster has been moved to the upper right. It is disturbing. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 ChromiumPrefs: can't open profile /home/peterzay/.config/chromium/Default/Preferences Date: Mon Jan 7 22:45:02 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-01-04 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+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 1097125] Re: chromium-browser has min/max/close buttons at upper right
@Chad, same thing, the buttons are in the top right corner. $ apt-cache policy chromium-browser chromium-browser: Installed: 28.0.1500.71-0ubuntu1.13.04.1 Candidate: 28.0.1500.71-0ubuntu1.13.04.1 Version table: *** 28.0.1500.71-0ubuntu1.13.04.1 0 500 http://archive.ubuntu.com/ubuntu/ raring-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ raring-security/universe amd64 Packages 100 /var/lib/dpkg/status 25.0.1364.160-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1097125 Title: chromium-browser has min/max/close buttons at upper right Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: In prior releases of chromium-browser, the minimize/maximize/close cluster of 3 buttons were always at the upper left as per Ubuntu standard layout. In Ubuntu 12.10, for some reason, this 3 button cluster has been moved to the upper right. It is disturbing. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 ChromiumPrefs: can't open profile /home/peterzay/.config/chromium/Default/Preferences Date: Mon Jan 7 22:45:02 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-01-04 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+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 1206183] [NEW] Deja-dup skips connecting to server unless it's already mounted
Public bug reported: I have deja-dup setup to backup to a password protected SMB share, when I set it up I told it to remember the password. Now, when I start deja-dup and ask it to do a back up, it opens the enter encrypted password dialogue, I click next, it then skips a window, and lands back on the enter encrypted password dialogue, with no errors or notifications that anything was wrong. If I manually mount the share, it works as expected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jul 29 10:25:18 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-26 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (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 deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1206183 Title: Deja-dup skips connecting to server unless it's already mounted Status in “deja-dup” package in Ubuntu: New Bug description: I have deja-dup setup to backup to a password protected SMB share, when I set it up I told it to remember the password. Now, when I start deja-dup and ask it to do a back up, it opens the enter encrypted password dialogue, I click next, it then skips a window, and lands back on the enter encrypted password dialogue, with no errors or notifications that anything was wrong. If I manually mount the share, it works as expected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jul 29 10:25:18 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-26 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1206183/+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 1186816] [NEW] Gnome-shell and X die after changing monitor resolution
Public bug reported: I switched around my monitor configuration so that I have 1 monitor on my primary video card (1920x1080), and 2 monitors (1680x1024) on my secondary video. The primary monitor's default resolution is higher than the other two monitors so when it first started the other two wouldn't display anything. I changed the resolution of all three to the maximum they could all support, but they're still all mirrored. Then I changed the screen layout so that there is no mirroring. After applying the changes, gnome- shell and X die bringing me back to the login screen. If I just mirror the monitors, all three will display. I've tried changing the layout through arandr, and gnome-control-center with the same result. Before I changed the monitor configuration I had two 1680x1024 monitors on the primary video card, and one other 1680x1024 on my secondary video card. This configuration worked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13 Uname: Linux 3.8.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 2 16:55:21 2013 DistUpgraded: 2013-04-16 00:01:25,797 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) Subsystem: Info-Tek Corp. Device [18bc:4390] Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI MSI R4850-T2D512 [1002:0502] InstallationDate: Installed on 2012-04-01 (427 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-24-generic root=UUID=83570b7b-7840-416b-9b0a-b05bf5e80b72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-16 (47 days ago) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Jun 2 16:48:21 2013 xserver.configfile: default xserver.errors: Failed to load module modesetting (module does not exist, 0) Failed to load module modesetting (module does not exist, 0) RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: gnome-control-center Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ubuntu ** Attachment added: Error Log of gnome-control-center https://bugs.launchpad.net/bugs/1186816/+attachment/3693064/+files/debug.log ** Also affects: gnome-control-center Importance: Undecided Status: 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/1186816 Title: Gnome-shell and X die after changing monitor resolution Status in GNOME Control Center: New Status in “xorg” package in Ubuntu: New Bug description: I switched around my monitor configuration so that I have 1 monitor on my primary video card (1920x1080), and 2 monitors (1680x1024) on my secondary video. The primary monitor's default resolution is higher than the other two monitors so when it first started the other two wouldn't display anything. I changed the resolution of all three to the maximum they
[Desktop-packages] [Bug 1186816] Re: Gnome-shell and X die after changing monitor resolution
If I take one of the monitors from the second video card and plug it into the primary, then everything works. ** Description changed: I switched around my monitor configuration so that I have 1 monitor on - my primary video card (1920x1080), and 2 monitors (1680x1024) on my + my primary video card (1920x1080), and 2 monitors (1920x1080) on my secondary video. The primary monitor's default resolution is higher than the other two monitors so when it first started the other two wouldn't display anything. I changed the resolution of all three to the maximum they could all support, but they're still all mirrored. Then I changed the screen layout so that there is no mirroring. After applying the changes, gnome- shell and X die bringing me back to the login screen. If I just mirror the monitors, all three will display. I've tried changing the layout through arandr, and gnome-control-center with the same result. - Before I changed the monitor configuration I had two 1680x1024 monitors + Before I changed the monitor configuration I had two 1920x1080 monitors on the primary video card, and one other 1680x1024 on my secondary video card. This configuration worked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13 Uname: Linux 3.8.0-24-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 2 16:55:21 2013 DistUpgraded: 2013-04-16 00:01:25,797 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) -Subsystem: Info-Tek Corp. Device [18bc:4390] - Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) -Subsystem: Advanced Micro Devices [AMD] nee ATI MSI R4850-T2D512 [1002:0502] + Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) + Subsystem: Info-Tek Corp. Device [18bc:4390] + Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) + Subsystem: Advanced Micro Devices [AMD] nee ATI MSI R4850-T2D512 [1002:0502] InstallationDate: Installed on 2012-04-01 (427 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-24-generic root=UUID=83570b7b-7840-416b-9b0a-b05bf5e80b72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-16 (47 days ago) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Jun 2 16:48:21 2013 xserver.configfile: default xserver.errors: - Failed to load module modesetting (module does not exist, 0) - Failed to load module modesetting (module does not exist, 0) - RADEON(G0): [XvMC] Failed to initialize extension. + Failed to load module modesetting (module does not exist, 0) + Failed to load module modesetting (module does not exist, 0) + RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Bug watch added: freedesktop.org Bugzilla #65275 https://bugs.freedesktop.org/show_bug.cgi?id=65275 -- You received this bug notification because you are a member
[Desktop-packages] [Bug 1186816] Re: Gnome-shell and X die after changing monitor resolution
Upstream bug report on xorg: https://bugs.freedesktop.org/show_bug.cgi?id=65275 -- 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/1186816 Title: Gnome-shell and X die after changing monitor resolution Status in GNOME Control Center: New Status in “xorg” package in Ubuntu: New Bug description: I switched around my monitor configuration so that I have 1 monitor on my primary video card (1920x1080), and 2 monitors (1920x1080) on my secondary video. The primary monitor's default resolution is higher than the other two monitors so when it first started the other two wouldn't display anything. I changed the resolution of all three to the maximum they could all support, but they're still all mirrored. Then I changed the screen layout so that there is no mirroring. After applying the changes, gnome-shell and X die bringing me back to the login screen. If I just mirror the monitors, all three will display. I've tried changing the layout through arandr, and gnome-control- center with the same result. Before I changed the monitor configuration I had two 1920x1080 monitors on the primary video card, and one other 1680x1024 on my secondary video card. This configuration worked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13 Uname: Linux 3.8.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 2 16:55:21 2013 DistUpgraded: 2013-04-16 00:01:25,797 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) Subsystem: Info-Tek Corp. Device [18bc:4390] Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI MSI R4850-T2D512 [1002:0502] InstallationDate: Installed on 2012-04-01 (427 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-24-generic root=UUID=83570b7b-7840-416b-9b0a-b05bf5e80b72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-16 (47 days ago) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Jun 2 16:48:21 2013 xserver.configfile: default xserver.errors: Failed to load module modesetting (module does not exist, 0) Failed to load module modesetting (module does not exist, 0) RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1186816/+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 1097125] Re: chromium-browser has min/max/close buttons at upper right
I'm not seeing this in my 12.10 install (with gnome-shell), but I am seeing it in my 13.04. Would be nice for this to be fixed. ** Tags added: raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1097125 Title: chromium-browser has min/max/close buttons at upper right Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: In prior releases of chromium-browser, the minimize/maximize/close cluster of 3 buttons were always at the upper left as per Ubuntu standard layout. In Ubuntu 12.10, for some reason, this 3 button cluster has been moved to the upper right. It is disturbing. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 ChromiumPrefs: can't open profile /home/peterzay/.config/chromium/Default/Preferences Date: Mon Jan 7 22:45:02 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-01-04 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+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 974900] Re: Menus split across multi monitors
Can we get the upstream fix backported? Pretty please. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/974900 Title: Menus split across multi monitors Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Have two monitors arranged side by side. Some applications when used maximised in the right hand monitor, display their menus split across the two monitors. Not all applications do this. gnome-terminal (with panel menus disabled) - is OK libreoffice - is BAD I don't know if this bug is unique to libreoffice or is in something like compiz. Using Unity, 12.04 latest beta --- .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,gnomecompat,snap,move,text,mousepoll,regex,compiztoolbox,grid,resize,imgpng,place,wall,animation,unitymtgrabhandles,session,expo,fade,scale,workarounds,unityshell,scaleaddon] CompositorRunning: compiz DistUpgraded: 2012-04-05 14:49:40,837 DEBUG enabling apt cron job DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical MachineType: Dell Inc. Latitude D630 Package: xorg 1:7.6+12ubuntu1 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/usr/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=84c73eda-43e4-429c-8428-0a37de7b6de5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Tags: precise ubuntu compiz-0.9 Uname: Linux 3.2.0-22-generic i686 UpgradeStatus: Upgraded to precise on 2012-04-05 (2 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy lpadmin netdev plugdev powerdev scanner tape video dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd06/20/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.4-0ubuntu1 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/974900/+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 958188] Re: SMART causes SSD to die with unhandled error code
Unfortunately, the cables were not the issue. I tried with different
cables and different machines. I returned my drive and got a replacement
of a different brand, which has lasted longer than the other two
combined. I still think the issue may have been caused by issuing a
S.M.A.R.T, but I'm unable to do any further testing. I'll change this
bug to invalid until someone else has a similar issue with OCZ Petrols.
** Changed in: gnome-disk-utility (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
SMART causes SSD to die with unhandled error code
Status in “gnome-disk-utility” package in Ubuntu:
Invalid
Bug description:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
Checking my syslog I see a lot of unhandled error code messages. If
I then do a soft reboot, the SSD is not detected in POST; I have to
hard reset to see it again.
This is my second OCZ Petrol, because the first one completely died in
more-or-less the same manner: it stopped showing in POST. So, I fear
it may be gnome-disk-utility causing this, and not two random failing
drives.
Here's an except from my syslog:
Mar 17 15:36:22 jupiter kernel: [ 1006.816119] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 17 15:36:22 jupiter kernel: [ 1006.816127] ata4.00: failed command: FLUSH
CACHE
Mar 17 15:36:22 jupiter kernel: [ 1006.816138] ata4.00: cmd
e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 17 15:36:22 jupiter kernel: [ 1006.816141] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 17 15:36:22 jupiter kernel: [ 1006.816157] ata4.00: status: { DRDY }
Mar 17 15:36:22 jupiter kernel: [ 1006.816164] ata4: hard resetting link
Mar 17 15:36:32 jupiter kernel: [ 1016.828031] ata4: softreset failed (device
not ready)
Mar 17 15:36:32 jupiter kernel: [ 1016.828041] ata4: hard resetting link
Mar 17 15:36:42 jupiter kernel: [ 1026.840101] ata4: softreset failed (device
not ready)
Mar 17 15:36:42 jupiter kernel: [ 1026.840110] ata4: hard resetting link
Mar 17 15:36:52 jupiter kernel: [ 1037.412109] ata4: link is slow to respond,
please be patient (ready=0)
Mar 17 15:37:17 jupiter kernel: [ 1061.884031] ata4: softreset failed (device
not ready)
Mar 17 15:37:17 jupiter kernel: [ 1061.884041] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 17 15:37:17 jupiter kernel: [ 1061.884046] ata4: hard resetting link
Mar 17 15:37:22 jupiter kernel: [ 1067.072117] ata4: softreset failed (device
not ready)
Mar 17 15:37:22 jupiter kernel: [ 1067.072125] ata4: reset failed, giving up
Mar 17 15:37:22 jupiter kernel: [ 1067.072130] ata4.00: disabled
Mar 17 15:37:22 jupiter kernel: [ 1067.072146] ata4: EH complete
Mar 17 15:37:22 jupiter kernel: [ 1067.072218] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072224] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072232] sd 3:0:0:0: [sdb] CDB:
Write(10): 2a 00 0b ab c0 c0 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072252] end_request: I/O error, dev
sdb, sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072260] end_request: I/O error, dev
sdb, sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072279] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072284] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072291] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 08 a7 e0 08 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072308] end_request: I/O error, dev
sdb, sector 145219592
Mar 17 15:37:22 jupiter kernel: [ 1067.072335] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072340] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072346] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 00 2a f1 d8 00 01 00 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072363] end_request: I/O error, dev
sdb, sector 2814424
Mar 17 15:37:22 jupiter kernel: [ 1067.072390] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072396] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072403] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 03 48 d2 20 00 00 20 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072420] end_request: I/O error, dev
sdb, sector 55104032
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-disk-utility 3.0.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture:
[Desktop-packages] [Bug 958188] Re: SMART causes SSD to die with unhandled error code
Ok, I tried running a SMART test via gnome-disk-utility with the
mainline kernel, and still get these errors. It took about 4 hard resets
to get my SSD to show in BIOS this morning.
Excerpt:
Mar 27 21:15:36 jupiter kernel: [ 68.832057] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 27 21:15:36 jupiter kernel: [ 68.832067] ata4.00: failed command: SMART
Mar 27 21:15:36 jupiter kernel: [ 68.832079] ata4.00: cmd
b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Mar 27 21:15:36 jupiter kernel: [ 68.832082] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 27 21:15:36 jupiter kernel: [ 68.832089] ata4.00: status: { DRDY }
Mar 27 21:15:36 jupiter kernel: [ 68.832096] ata4: hard resetting link
Mar 27 21:15:46 jupiter kernel: [ 78.844142] ata4: softreset failed (device
not ready)
Mar 27 21:15:46 jupiter kernel: [ 78.844150] ata4: hard resetting link
Mar 27 21:16:31 jupiter kernel: [ 123.900139] ata4: softreset failed (device
not ready)
Mar 27 21:16:31 jupiter kernel: [ 123.900148] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 27 21:16:36 jupiter kernel: [ 129.088127] ata4: softreset failed (device
not ready)
Mar 27 21:16:36 jupiter kernel: [ 129.088136] ata4: reset failed, giving up
Mar 27 21:16:36 jupiter kernel: [ 129.088142] ata4.00: disabled
Mar 27 21:16:36 jupiter kernel: [ 129.088188] ata4: EH complete
Mar 27 21:16:36 jupiter kernel: [ 129.088233] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088238] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088246] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 06 44 1c 40 00 00 20 00
Mar 27 21:16:36 jupiter kernel: [ 129.088262] end_request: I/O error, dev sdb,
sector 105126976
Mar 27 21:16:36 jupiter kernel: [ 129.088282] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088287] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088293] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 00 95 27 00 00 00 20 00
Mar 27 21:16:36 jupiter kernel: [ 129.088308] end_request: I/O error, dev sdb,
sector 9774848
Mar 27 21:16:36 jupiter kernel: [ 129.088324] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088331] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 27 21:16:36 jupiter kernel: [ 129.088336] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 27 21:16:36 jupiter kernel: [ 129.088344] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 04 84 c5 b0 00 00 20
Mar 27 21:16:36 jupiter kernel: [ 129.088370] sd 3:0:0:0: [sdb] Unhandled
error code
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/958188/+attachment/2955631/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
SMART causes SSD to die with unhandled error code
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug description:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
Checking my syslog I see a lot of unhandled error code messages. If
I then do a soft reboot, the SSD is not detected in POST; I have to
hard reset to see it again.
This is my second OCZ Petrol, because the first one completely died in
more-or-less the same manner: it stopped showing in POST. So, I fear
it may be gnome-disk-utility causing this, and not two random failing
drives.
Here's an except from my syslog:
Mar 17 15:36:22 jupiter kernel: [ 1006.816119] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 17 15:36:22 jupiter kernel: [ 1006.816127] ata4.00: failed command: FLUSH
CACHE
Mar 17 15:36:22 jupiter kernel: [ 1006.816138] ata4.00: cmd
e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 17 15:36:22 jupiter kernel: [ 1006.816141] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 17 15:36:22 jupiter kernel: [ 1006.816157] ata4.00: status: { DRDY }
Mar 17 15:36:22 jupiter kernel: [ 1006.816164] ata4: hard resetting link
Mar 17 15:36:32 jupiter kernel: [ 1016.828031] ata4: softreset failed (device
not ready)
Mar 17 15:36:32 jupiter kernel: [ 1016.828041] ata4: hard resetting link
Mar 17 15:36:42 jupiter kernel: [ 1026.840101] ata4: softreset failed (device
not ready)
Mar 17 15:36:42 jupiter kernel: [ 1026.840110] ata4: hard resetting link
Mar 17 15:36:52 jupiter kernel: [ 1037.412109] ata4: link is slow to respond,
please be patient (ready=0)
Mar 17 15:37:17 jupiter kernel: [ 1061.884031] ata4: softreset failed (device
not ready)
Mar 17 15:37:17 jupiter kernel: [ 1061.884041] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 17 15:37:17 jupiter kernel: [
[Desktop-packages] [Bug 958188] [NEW] SMART causes SSD to die with unhandled error code
Public bug reported:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
Checking my syslog I see a lot of unhandled error code messages. If I
then do a soft reboot, the SSD is not detected in POST; I have to hard
reset to see it again.
This is my second OCZ Petrol, because the first one completely died in
more-or-less the same manner: it stopped showing in POST. So, I fear it
may be gnome-disk-utility causing this, and not two random failing
drives.
Here's an except from my syslog:
Mar 17 15:36:22 jupiter kernel: [ 1006.816119] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 17 15:36:22 jupiter kernel: [ 1006.816127] ata4.00: failed command: FLUSH
CACHE
Mar 17 15:36:22 jupiter kernel: [ 1006.816138] ata4.00: cmd
e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 17 15:36:22 jupiter kernel: [ 1006.816141] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 17 15:36:22 jupiter kernel: [ 1006.816157] ata4.00: status: { DRDY }
Mar 17 15:36:22 jupiter kernel: [ 1006.816164] ata4: hard resetting link
Mar 17 15:36:32 jupiter kernel: [ 1016.828031] ata4: softreset failed (device
not ready)
Mar 17 15:36:32 jupiter kernel: [ 1016.828041] ata4: hard resetting link
Mar 17 15:36:42 jupiter kernel: [ 1026.840101] ata4: softreset failed (device
not ready)
Mar 17 15:36:42 jupiter kernel: [ 1026.840110] ata4: hard resetting link
Mar 17 15:36:52 jupiter kernel: [ 1037.412109] ata4: link is slow to respond,
please be patient (ready=0)
Mar 17 15:37:17 jupiter kernel: [ 1061.884031] ata4: softreset failed (device
not ready)
Mar 17 15:37:17 jupiter kernel: [ 1061.884041] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 17 15:37:17 jupiter kernel: [ 1061.884046] ata4: hard resetting link
Mar 17 15:37:22 jupiter kernel: [ 1067.072117] ata4: softreset failed (device
not ready)
Mar 17 15:37:22 jupiter kernel: [ 1067.072125] ata4: reset failed, giving up
Mar 17 15:37:22 jupiter kernel: [ 1067.072130] ata4.00: disabled
Mar 17 15:37:22 jupiter kernel: [ 1067.072146] ata4: EH complete
Mar 17 15:37:22 jupiter kernel: [ 1067.072218] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072224] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072232] sd 3:0:0:0: [sdb] CDB:
Write(10): 2a 00 0b ab c0 c0 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072252] end_request: I/O error, dev sdb,
sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072260] end_request: I/O error, dev sdb,
sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072279] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072284] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072291] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 08 a7 e0 08 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072308] end_request: I/O error, dev sdb,
sector 145219592
Mar 17 15:37:22 jupiter kernel: [ 1067.072335] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072340] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072346] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 00 2a f1 d8 00 01 00 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072363] end_request: I/O error, dev sdb,
sector 2814424
Mar 17 15:37:22 jupiter kernel: [ 1067.072390] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072396] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072403] sd 3:0:0:0: [sdb] CDB: Read(10):
28 00 03 48 d2 20 00 00 20 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072420] end_request: I/O error, dev sdb,
sector 55104032
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-disk-utility 3.0.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Mar 17 15:56:02 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oneiric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
SMART causes SSD to die with unhandled error code
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug description:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
[Desktop-packages] [Bug 958188] Re: SMART causes SSD to die with unhandled error code
** Attachment added: Full syslog
https://bugs.launchpad.net/bugs/958188/+attachment/2888626/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
SMART causes SSD to die with unhandled error code
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug description:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
Checking my syslog I see a lot of unhandled error code messages. If
I then do a soft reboot, the SSD is not detected in POST; I have to
hard reset to see it again.
This is my second OCZ Petrol, because the first one completely died in
more-or-less the same manner: it stopped showing in POST. So, I fear
it may be gnome-disk-utility causing this, and not two random failing
drives.
Here's an except from my syslog:
Mar 17 15:36:22 jupiter kernel: [ 1006.816119] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 17 15:36:22 jupiter kernel: [ 1006.816127] ata4.00: failed command: FLUSH
CACHE
Mar 17 15:36:22 jupiter kernel: [ 1006.816138] ata4.00: cmd
e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 17 15:36:22 jupiter kernel: [ 1006.816141] res
40/00:00:01:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 17 15:36:22 jupiter kernel: [ 1006.816157] ata4.00: status: { DRDY }
Mar 17 15:36:22 jupiter kernel: [ 1006.816164] ata4: hard resetting link
Mar 17 15:36:32 jupiter kernel: [ 1016.828031] ata4: softreset failed (device
not ready)
Mar 17 15:36:32 jupiter kernel: [ 1016.828041] ata4: hard resetting link
Mar 17 15:36:42 jupiter kernel: [ 1026.840101] ata4: softreset failed (device
not ready)
Mar 17 15:36:42 jupiter kernel: [ 1026.840110] ata4: hard resetting link
Mar 17 15:36:52 jupiter kernel: [ 1037.412109] ata4: link is slow to respond,
please be patient (ready=0)
Mar 17 15:37:17 jupiter kernel: [ 1061.884031] ata4: softreset failed (device
not ready)
Mar 17 15:37:17 jupiter kernel: [ 1061.884041] ata4: limiting SATA link speed
to 3.0 Gbps
Mar 17 15:37:17 jupiter kernel: [ 1061.884046] ata4: hard resetting link
Mar 17 15:37:22 jupiter kernel: [ 1067.072117] ata4: softreset failed (device
not ready)
Mar 17 15:37:22 jupiter kernel: [ 1067.072125] ata4: reset failed, giving up
Mar 17 15:37:22 jupiter kernel: [ 1067.072130] ata4.00: disabled
Mar 17 15:37:22 jupiter kernel: [ 1067.072146] ata4: EH complete
Mar 17 15:37:22 jupiter kernel: [ 1067.072218] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072224] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072232] sd 3:0:0:0: [sdb] CDB:
Write(10): 2a 00 0b ab c0 c0 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072252] end_request: I/O error, dev
sdb, sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072260] end_request: I/O error, dev
sdb, sector 195805376
Mar 17 15:37:22 jupiter kernel: [ 1067.072279] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072284] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072291] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 08 a7 e0 08 00 00 08 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072308] end_request: I/O error, dev
sdb, sector 145219592
Mar 17 15:37:22 jupiter kernel: [ 1067.072335] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072340] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072346] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 00 2a f1 d8 00 01 00 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072363] end_request: I/O error, dev
sdb, sector 2814424
Mar 17 15:37:22 jupiter kernel: [ 1067.072390] sd 3:0:0:0: [sdb] Unhandled
error code
Mar 17 15:37:22 jupiter kernel: [ 1067.072396] sd 3:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 17 15:37:22 jupiter kernel: [ 1067.072403] sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 03 48 d2 20 00 00 20 00
Mar 17 15:37:22 jupiter kernel: [ 1067.072420] end_request: I/O error, dev
sdb, sector 55104032
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-disk-utility 3.0.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Mar 17 15:56:02 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
[Desktop-packages] [Bug 955546] Re: gnome-terminal crashes with forked command not found if path is too long
Unfortunately, there isn't a crash report. I've tried to get a backtrace in gdb, but gnome-terminal forks or something so I don't know how to follow it. I've also managed to reproduce this on precise. -- 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/955546 Title: gnome-terminal crashes with forked command not found if path is too long Status in “gnome-terminal” package in Ubuntu: Incomplete Bug description: The affected package could also be the command-not-found package. There seems to be a bug with the way either gnome-terminal or command- not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path. My testcase (which may have to be fiddled with): ~$ mkdir 123456789012345678 ~$ cd 123456789012345678 ~/123456789012345678$ pwd /home/redbrick/123456789012345678 ~/123456789012345678$ a * gnome-terminal crashes * I've reproduced this on three different machines. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 14 15:55:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/955546/+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 955546] Re: gnome-terminal crashes with forked command not found if path is too long
-- 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/955546 Title: gnome-terminal crashes with forked command not found if path is too long Status in “gnome-terminal” package in Ubuntu: New Bug description: The affected package could also be the command-not-found package. There seems to be a bug with the way either gnome-terminal or command- not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path. My testcase (which may have to be fiddled with): ~$ mkdir 123456789012345678 ~$ cd 123456789012345678 ~/123456789012345678$ pwd /home/redbrick/123456789012345678 ~/123456789012345678$ a * gnome-terminal crashes * I've reproduced this on three different machines. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 14 15:55:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/955546/+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 955546] [NEW] gnome-terminal crashes with forked command not found if path is too long
Public bug reported: The affected package could also be the command-not-found package. There seems to be a bug with the way either gnome-terminal or command- not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path. My testcase (which may have to be fiddled with): ~$ mkdir 123456789012345678 ~$ cd 123456789012345678 ~/123456789012345678$ pwd /home/redbrick/123456789012345678 ~/123456789012345678$ a * gnome-terminal crashes * I've reproduced this on three different machines. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 14 15:55:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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 oneiric -- 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/955546 Title: gnome-terminal crashes with forked command not found if path is too long Status in “gnome-terminal” package in Ubuntu: New Bug description: The affected package could also be the command-not-found package. There seems to be a bug with the way either gnome-terminal or command- not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path. My testcase (which may have to be fiddled with): ~$ mkdir 123456789012345678 ~$ cd 123456789012345678 ~/123456789012345678$ pwd /home/redbrick/123456789012345678 ~/123456789012345678$ a * gnome-terminal crashes * I've reproduced this on three different machines. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Mar 14 15:55:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/955546/+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 797986] Re: rhythmbox displays in front of window, but functions as if it is behind
I can't really reproduce it on Oneiric because you can't minimize rhythmbox to tray. However, I can still reproduce it on Natty, I'm using Metacity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/797986 Title: rhythmbox displays in front of window, but functions as if it is behind Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: Binary package hint: rhythmbox This is a weird bug to describe, and reproduce. I'm not entirely sure this is a rhythmbox bug, or a metacity bug. Here's how I *think* it's reproduced: 1) start rhythmbox, have it hide to tray on minimize/close so that it's accessed through the sound menu. 2) close rhythmbox so that it's hidden 3) open a terminal 4) position the terminal so that is where rhythmbox will appear 5) change focus by clicking on the desktop 6) change focus back to the terminal by clicking on it 7) go to the sound menu and open rhythmbox Expected results: Rhythmbox should display in front of the terminal Actual results: Rhythmbox appears in front of the terminal, but behaves as if it were behind. See attached screenshot, notice the window border is missing where it overlaps the terminal. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: rhythmbox 0.13.3-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jun 15 20:03:00 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to natty on 2011-03-20 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/797986/+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
