[Desktop-packages] [Bug 1959079] [NEW] The UI crashes after suspend
Public bug reported: All was working OK until I installed nvidia cuda drivers. Afterwards on lid open the system crashes. On lid close it exhausted the battery too fast. Now I have them deleted and have reverted to nouveau drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jan 26 10:37:23 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] MachineType: LENOVO 82D4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1c371a7d-438b-4e79-8a3b-218cba05e945 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: EGCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Creator 5 15IMH05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrEGCN25WW:bd04/28/2020:br1.25:efr1.25:svnLENOVO:pn82D4:pvrIdeaPadCreator515IMH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadCreator515IMH05:skuLENOVO_MT_82D4_BU_idea_FM_IdeaPadCreator515IMH05: dmi.product.family: IdeaPad Creator 5 15IMH05 dmi.product.name: 82D4 dmi.product.sku: LENOVO_MT_82D4_BU_idea_FM_IdeaPad Creator 5 15IMH05 dmi.product.version: IdeaPad Creator 5 15IMH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1959079 Title: The UI crashes after suspend Status in xorg package in Ubuntu: New Bug description: All was working OK until I installed nvidia cuda drivers. Afterwards on lid open the system crashes. On lid close it exhausted the battery too fast. Now I have them deleted and have reverted to nouveau drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jan 26 10:37:23 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] MachineType: LENOVO 82D4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1c371a7d-438b-4e79-8a3b-218cba05e945 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: EGCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Creator 5 15IMH05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrEGCN25WW:bd04/28/2020:br1.25:efr1.25:svnLENOVO:pn82D4:pvrIdeaPadCreator515IMH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadCreator515IMH05:skuLENOVO_MT_82D4_BU_idea_FM_IdeaPadCreator515IMH05:
[Desktop-packages] [Bug 1909616] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1909616/+attachment/5448114/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1909616 Title: Same user appears to be logged multiple times Status in gnome-session package in Ubuntu: New Bug description: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2015-06-17 (2023 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-session 3.36.0-2ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1909616/+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 1909616] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1909616/+attachment/5448116/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1909616 Title: Same user appears to be logged multiple times Status in gnome-session package in Ubuntu: New Bug description: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2015-06-17 (2023 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-session 3.36.0-2ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1909616/+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 1909616] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1909616/+attachment/5448115/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1909616 Title: Same user appears to be logged multiple times Status in gnome-session package in Ubuntu: New Bug description: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2015-06-17 (2023 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-session 3.36.0-2ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1909616/+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 1909616] Re: Same user appears to be logged multiple times
I personally haven't logged multiple times. Also this is reproducible immediately after login. Is there a way to check if some program is doing this? Also I think its worth mentioning that I changed my password (in attempt to prevent this) and it continued to do it. ** Tags added: apport-collected focal ** Description changed: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2015-06-17 (2023 days ago) + InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-session 3.36.0-2ubuntu1 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 + Tags: focal + Uname: Linux 5.4.0-58-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1909616 Title: Same user appears to be logged multiple times Status in gnome-session package in Ubuntu: New Bug description: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2015-06-17 (2023 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-session 3.36.0-2ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1909616/+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 1903468] [NEW] Endless "Cache Refresh" on Software Update settings change
Public bug reported: After reapplying the some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears > lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-11-09 01-56-54.png" https://bugs.launchpad.net/bugs/1903468/+attachment/5432426/+files/Screenshot%20from%202020-11-09%2001-56-54.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: New Bug description: After reapplying the some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+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 1754702] Re: Delay before you can type after switching input source
The issue persist after changing it with tweak. I'm using Shift + Alt for years. But after language switch it always takes 1-2 seconds. No screen freezing or anything. Just the language takes time to change. As mentioned above, very annoying if you have to change languages frequently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1754702 Title: Delay before you can type after switching input source Status in gnome-shell package in Ubuntu: Confirmed Bug description: In ubuntu 18.04 I installed different keyboard languages: spanish latin american, japanese, japanese-ibus. To change the input method you press the selected key, and an indicator menu appears on-screen to indicate which language is selected next. The menu disapears after 2~3 seconds and during which time typing is blocked. If you type while the language input method menu is displayed, the menu will not disapear and stay as long as you type. The language input menu should not block typing, and the disapearance of the menu should not be delayed by typing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+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 1694454] Re: Can't open gnome terminal
Awesome observation Chris, Now that you mention it, I also have other DE installed. But the issue appears without login into any of them beforehand. I've noticed that sometimes when I login into other DE -> logout -> and login again to gnome the apps works normally. Not sure which one I have a few. -- 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/1694454 Title: Can't open gnome terminal Status in gnome-terminal package in Ubuntu: Invalid Bug description: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1694454/+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 1694454] Re: Can't open gnome terminal
Yes, same goes for totem as well. Double clicking on video/audio files shows totem loading for a few seconds and closing without error. When I open totem from MATE Terminal and simply drop the video in its window, works fine. -- 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/1694454 Title: Can't open gnome terminal Status in gnome-terminal package in Ubuntu: Invalid Bug description: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1694454/+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 1694454] Re: Can't open gnome terminal
I managed to start the gnome-terminal via this command: "dbus-launch gnome-terminal" It outputs this error tho: "WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." I also managed to start it with: "sudo gnome-terminal" without any errors. Before that I tried "locale-gen" and "sudo localectl set-locale LANG="en_US.UTF-8"" as mentioned in similar forum posts but they don't seem to help in this case. -- 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/1694454 Title: Can't open gnome terminal Status in gnome-terminal package in Ubuntu: New Bug description: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1694454/+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 1694457] [NEW] Unable to Open Files With Totem After Upgrade to 17.04
Public bug reported: I can't open .mkv and .mp3 files with Totem. This behavior appeared after upgrade to 17.04. After I double click a file a loading indication in the title bar appears. After a few seconds it simply disappears and the player is not showing. If I start a Terminal and type "totem " the file is opened normally. >> lsb_release -rd Description:Ubuntu 17.04 Release:17.04 >> apt-cache policy totem totem: Installed: 3.24.0-0ubuntu1 Candidate: 3.24.0-0ubuntu1 Version table: *** 3.24.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.4-1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:33:05 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1694457 Title: Unable to Open Files With Totem After Upgrade to 17.04 Status in gstreamer1.0 package in Ubuntu: New Bug description: I can't open .mkv and .mp3 files with Totem. This behavior appeared after upgrade to 17.04. After I double click a file a loading indication in the title bar appears. After a few seconds it simply disappears and the player is not showing. If I start a Terminal and type "totem " the file is opened normally. >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy totem totem: Installed: 3.24.0-0ubuntu1 Candidate: 3.24.0-0ubuntu1 Version table: *** 3.24.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.4-1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:33:05 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1694457/+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 1694454] [NEW] Can't open gnome terminal
Public bug reported: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description:Ubuntu 17.04 Release:17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- 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/1694454 Title: Can't open gnome terminal Status in gnome-terminal package in Ubuntu: New Bug description: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1694454/+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 1510821] Re: Ubuntu Freezes With No Obvious Reason
Thank you Christopher for the response. I've updated the bios to 2202 but unfortunately the pc continues to block me out. The output of the given command "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date" is: 2202 09/15/2010 The behavior is the same. The mouse stops responding, the keyboard is active for about 2-3 seconds after that, then it also does not respond. The screen is not changing at all. If I have music playing (something I can observe is working behind) it continues to play for a while though. I am out of ideas about this bug. ** Changed in: xorg (Ubuntu) Status: Incomplete => 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/1510821 Title: Ubuntu Freezes With No Obvious Reason Status in xorg package in Ubuntu: New Bug description: I am dev and I know how this sounds but at a certain periods ubuntu freezes entirely. The only exit is the power button. I dont know what could be helpful information in this case so I will write everything I noticed so far (sry for the spam). This used to happen a lot while building with Android Studio but lately it freezes even when the studio is closed. The last time it happened after I closed(or tried to) Chrome tab while updating ubuntu. This behavior started a few weeks ago. I haven't updated to 15.10 at the time so I did. But it still continued to block. I thought it might be from the video driver so I switched from nvidia-340 to nouveau with no success. I cant find anything helpful in kern.log if its needed I can attach the log just before the freeze. What I find strange is in the syslog. At the time of the freeze it is filled with NULs. See attached image syslog.png. The time of the freeze was around 8:57. At this point the mouse cursor was active but there was nothing that reacted to my desperate clicks or keyboard shortcuts. After awhile the mouse stops as well and there is nothing I can do but the power button. Is there some other log that could be helpful or anything else I can do? Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Oct 28 09:36:12 2015 DistUpgraded: 2015-10-27 13:34:15,610 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.2, 3.19.0-31-generic, x86_64: installed vboxhost, 5.0.2, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82e6] InstallationDate: Installed on 2015-06-17 (132 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=db78bb87-80bc-4175-935a-18f69d5c471d ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (0 days ago) dmi.bios.date: 05/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd05/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Oct 28 10:00:45 2015
[Desktop-packages] [Bug 1510821] [NEW] Ubuntu Freezes With No Obvious Reason
Public bug reported: I am dev and I know how this sounds but at a certain periods ubuntu freezes entirely. The only exit is the power button. I dont know what could be helpful information in this case so I will write everything I noticed so far (sry for the spam). This used to happen a lot while building with Android Studio but lately it freezes even when the studio is closed. The last time it happened after I closed(or tried to) Chrome tab while updating ubuntu. This behavior started a few weeks ago. I haven't updated to 15.10 at the time so I did. But it still continued to block. I thought it might be from the video driver so I switched from nvidia-340 to nouveau with no success. I cant find anything helpful in kern.log if its needed I can attach the log just before the freeze. What I find strange is in the syslog. At the time of the freeze it is filled with NULs. See attached image syslog.png. The time of the freeze was around 8:57. At this point the mouse cursor was active but there was nothing that reacted to my desperate clicks or keyboard shortcuts. After awhile the mouse stops as well and there is nothing I can do but the power button. Is there some other log that could be helpful or anything else I can do? Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Oct 28 09:36:12 2015 DistUpgraded: 2015-10-27 13:34:15,610 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.2, 3.19.0-31-generic, x86_64: installed vboxhost, 5.0.2, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82e6] InstallationDate: Installed on 2015-06-17 (132 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=db78bb87-80bc-4175-935a-18f69d5c471d ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (0 days ago) dmi.bios.date: 05/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd05/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Oct 28 10:00:45 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB OPTICAL MOUSE MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily ** Attachment added: "Syslog just before the freeze" https://bugs.launchpad.net/bugs/1510821/+attachment/4507300/+files/syslog.png -- 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/1510821 Title: Ubuntu Freezes With No Obvious Reason Status in xorg package in Ubuntu: New Bug
