[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Hey there. This bug affects the pre-installed default email client of Ubuntu, there's a fix available upstream now since a few weeks and the next major Ubuntu release is scheduled four months in the future. Can you please release the bugfix for the current release(s), prettyplease? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
There has been no update to the 40.x branch at https://salsa.debian.org/gnome-team/mutter/-/commits/upstream/40.x/ a month since this was fixed and I had hoped that a Debian/Ubuntu team member would notice it via this bug report. Here's hoping for a fix in the 21.04 and 21.10 packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
A fix has been merged upstream two months ago, see https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4184 and https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2027 The fix was released with version 40.6, but Debian and Ubuntu haven't updated the upstream package in their repository, yet. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4184 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4184 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+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 571588] Re: Ubuntu chat theme uses ugly avatar scaling
This bug may be closed by now. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adium-theme-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/571588 Title: Ubuntu chat theme uses ugly avatar scaling Status in adium-theme-ubuntu package in Ubuntu: New Bug description: Binary package hint: empathy The "Ubuntu" chat style for empathy in Lucid shows comic-style chat balloons with resized user avatar images. With a better scaling algorithm, the avatar images would look a lot nicer than they do now See screenshot and compare full size avatar in user info window with scaled avatar in chat window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adium-theme-ubuntu/+bug/571588/+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 1913217] Re: [nvidia] Screen going black and not responding to input
Had a bit of time today to play around with other kernel versions. The "update" that was done was just a patch (5.8.0-40 -> 5.8.0-41). I've tried reverting to the first and also installed the 5.4 kernel you suggested but both did have the same issue. Looks like the system is mostly okay as long as I do not open too many applications/windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1913217 Title: [nvidia] Screen going black and not responding to input Status in linux-signed-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1913217/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1913217] Re: [nvidia] Screen going black and not responding to input
So basically you are saying I should submit a bug report to the nvidia module developers? Would have been happy to not use it but my laptop (MacbookPro 6,2) freezes up for long periods when using the nouveau driver for which the solution was to be using the nvidia driver... Had the impression the system lock up started following an update which included kernel packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1913217 Title: [nvidia] Screen going black and not responding to input Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1913217/+subscriptions -- Mailing list: https://launchpad.net/~de
[Desktop-packages] [Bug 1913217] Re: [nvidia] Screen going black and not responding to input
So basically you are saying I should submit a bug report to the nvidia module developers? Would have been happy to not use it but my laptop (MacbookPro 6,2) freezes up for long periods when using the nouveau driver for which the solution was to be using the nvidia driver... Had the impression the system lock up started following an update which included kernel packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1913217 Title: [nvidia] Screen going black and not responding to input Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1913217/+subscriptions -- Mailing list: https://launchpad.net/~de
[Desktop-packages] [Bug 1913217] Re: Screen going black and not responding to input
Hi Daniel, Thanks for the response, attaching the file. The installation is pretty new and has no additional GNOME extensions. Also submitted a new crash report today: https://errors.ubuntu.com/oops/ed647ea2-60cb-11eb-8e09-fa163e6cac46 By the way: found out today I can still access the system externally through ssh after a freeze. Let me know if there is anything else I can do to help pinpoint the issue. Cheers, Hanno ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913217/+attachment/5457469/+files/prevboot.txt -- 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/1913217 Title: Screen going black and not responding to input Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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
[Desktop-packages] [Bug 1913217] [NEW] Xorg freeze
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 freeze 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/1913217 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus
[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
To further clarify the impact of different hardware on bug occurrence:
The difference in Mariusz' hardware (Dell vs. Toshiba) leads to
different kernel names ("3-4" on Dell vs. "2-1.2" on Toshiba). So
"device validation" only happened on his Toshiba (thereby updating iface
to the wrong value of 8), but not on Dell. Similarly, I had a problem on
RPi 3 (kernel_name = "1-1.3") but no problem on an x86_64 VM
(kernel_name = "1-1"). My hardware and VM both ran on Ubuntu 20.04 LTS.
This is the commit that fixed a segfault in the C dispatcher but
introduced the problem for Mariusz and me:
https://git.launchpad.net/ubuntu/+source/usb-
modeswitch/commit/?id=4ef455d6d34fa465945db2b18f5dcabc604a9888
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926
Title:
usb_modeswitch does not switch modems (remain visible as mass storage)
Status in usb-modeswitch package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu focal fossa development branch the usb_modeswitch
does not seem to work any more on a Toshiba laptop.
Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from
the terminal.
I have a strong feeling that it may either be related to Gnome or hardware.
On another Dell laptop with Kubuntu focal fossa development, both modems
connect automatically.
/var/log/usb_modeswitch.log ends with:
Warning: SCSI attribute "ref" not readable.
Check class of first interface ...
Device is in istall mode.
No access to interface 8. Exit
Up until and including the "ref" not readable is exactly the same as on
Kubuntu @ Dell.
Yet on Kubuntu I get plenty of successful config logs after that and on
Ubuntu @ Toshiba I don't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+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 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
I am likely experiencing the same issue, yet on other hardware: Ubuntu
20.04 with a ZTE MF100 modem but only on Raspberry Pi. The good news: I
have triaged the issue.
The bug is in "usb_modeswitch_dispatcher.c", a C rewrite of the upstream
Tcl script. The C dispatcher receives the modem's kernel_name. If it
contains the characters dot ('.') and dash ('-') but no colon (':'), the
device is marked for some extended "interface validation" (see lines
343ff of "usb_modeswitch_dispatcher.c"). A bit further down at lines
388ff, the "iface" is initialized to 0, but the interface validation
updates it to 8. The value 8 stems from an atoi() invocation on the
contents of "bInterfaceClass". For this updated iface value, the C
dispatcher tries to find the corresponding (sub) interface directory and
this fails because my modem does not have 8 sub devices. Until here,
18.04 and 20.04 behavior is identical. However, the following new code
was introduced in 20.04 right after the directory lookup attempt is
made:
--8<--
if (ifdir == NULL) {
modeswitch_log(" No access to interface %d. Exit\n", iface);
return 1;
}
--8<--
This is causing the early exit for Mariusz and me. If I remove this
code, the rest of the C dispatcher works fine (even with a wrong iface
value of 8 - this is the same behavior as it was on 18.04). In a
scenario where no interface validation takes place (e.g. because of a
colon in the kernel_name or the absence of a dot - such as Ubuntu 20.04
on x86_64 VM), the iface value of 0 remains unchanged and the interface
directory is looked up successfully.
I have tried to match the C dispatcher code with the upstream Tcl
script. The Tcl script initializes iface to 0 and eventually updates it
to "1.0" when doing the interface validation branch.
Another thing that I noticed is that the C dispatcher erroneously uses
atoi() on the contents of bInterfaceClass. The content is a hexadecimal
string such as "00", "08" or "ff" while atoi() expects a decimal string.
If bInterfaceClass contains "ff", atoi() would return 0.
I have solved this problem by replacing "usb_modeswitch_dispatcher" with the
upstream Tcl script, pointing its interpreter to jimsh and installing jimsh. I
think it would be a wise choice to ditch the C dispatcher, use the upstream Tcl
script and make the package depend on jimsh. Reasons:
- The C dispatcher does not implement the same functionality as the Tcl script
in 2.5.2.
- Implementing changes from the Tcl script in 2.6.0 would be even more painful.
- The usb_modeswitch author provides flavors that eliminate the Tcl dependency.
- I fail to see how the "binary size" argument still applies in 2020 to
machines that are capable of running Ubuntu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926
Title:
usb_modeswitch does not switch modems (remain visible as mass storage)
Status in usb-modeswitch package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu focal fossa development branch the usb_modeswitch
does not seem to work any more on a Toshiba laptop.
Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from
the terminal.
I have a strong feeling that it may either be related to Gnome or hardware.
On another Dell laptop with Kubuntu focal fossa development, both modems
connect automatically.
/var/log/usb_modeswitch.log ends with:
Warning: SCSI attribute "ref" not readable.
Check class of first interface ...
Device is in istall mode.
No access to interface 8. Exit
Up until and including the "ref" not readable is exactly the same as on
Kubuntu @ Dell.
Yet on Kubuntu I get plenty of successful config logs after that and on
Ubuntu @ Toshiba I don't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
This does not only affect the NVIDIA modules, but seems to affect all kernel modules built on the system itself. (Meaning all DKMS-built modules and for example VMWare Workstation/Player modules) -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD 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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+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 1594176] Re: Download arrow animation leaves garbage on the address bar
Same here. Running firefox package 47.0+build3-0ubuntu0.16.04.1 on
XUbuntu desktop with Intel(R) HD Graphics 2000.
** Attachment added: "Screenshot of download arrow"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1594176/+attachment/4700696/+files/firefox-arrow.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1594176
Title:
Download arrow animation leaves garbage on the address bar
Status in firefox package in Ubuntu:
Confirmed
Bug description:
When a download finishes, the download arrow button displays an
animation (blue arrow grows and fades). Since a recent update, the
animation leaves garbage on the address bar (see attached picture).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 47.0+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gpothier 2870 F pulseaudio
/dev/snd/controlC0: gpothier 2870 F pulseaudio
BuildID: 20160606113944
Channel: Unavailable
CurrentDesktop: GNOME
Date: Sun Jun 19 17:14:00 2016
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2015-01-23 (513 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
MostRecentCrashID: bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
rhythmbox-mozilla 3.3-1ubuntu7
gnome-shell 3.18.5-0ubuntu0.1
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
bp-aba8367f-3da0-4f1c-9342-b377f2151224
UpgradeStatus: Upgraded to xenial on 2016-03-21 (90 days ago)
dmi.bios.date: 03/25/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN35WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias:
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1594176/+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 747627] Re: Sony VAIO VGN-SR51MF/S does not wake up from sleep
Oh, good news: Googling around, this fixed the issue for me: http://ubuntuforums.org/showthread.php?t=1980249 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/747627 Title: Sony VAIO VGN-SR51MF/S does not wake up from sleep Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Binary package hint: xserver-xorg-video-ati I'm using Kubuntu 11.04 beta, but this bug was already present in previous versions of (K)Ubuntu. My laptop is a Sony VAIO VGN-SR51MF/S. The video card is an ATI Radeon Mobility HD4570. glxinfo says the opengl renderer string is "OpenGL renderer string: Gallium 0.4 on AMD RV710" When I switch my laptop on, the screen stays black and the harddisk activity led keeps burning - not flickering, but continuously burning. No useful activity seems to be happening. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: kwin DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Fri Apr 1 22:24:07 2011 DistUpgraded: Log time: 2011-03-20 17:03:20.838900 DistroCodename: natty DistroVariant: kubuntu GraphicsCard: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9033] MachineType: Sony Corporation VGN-SR51MF_S ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=da81fb40-de8a-4d52-a359-76d6185050a9 ro splash quiet vt.handoff=7 Renderer: Unknown SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to natty on 2011-03-20 (12 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R4090Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4090Y1:bd08/05/2009:svnSonyCorporation:pnVGN-SR51MF_S:pvrC6025431:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR51MF_S dmi.product.version: C6025431 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.4git20110322-0ubuntu5 version.libdrm2: libdrm2 2.4.23-1ubuntu5 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/747627/+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 747627] Re: Sony VAIO VGN-SR51MF/S does not wake up from sleep
I can confirm that this still happens with Ubuntu 13.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/747627 Title: Sony VAIO VGN-SR51MF/S does not wake up from sleep Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Binary package hint: xserver-xorg-video-ati I'm using Kubuntu 11.04 beta, but this bug was already present in previous versions of (K)Ubuntu. My laptop is a Sony VAIO VGN-SR51MF/S. The video card is an ATI Radeon Mobility HD4570. glxinfo says the opengl renderer string is "OpenGL renderer string: Gallium 0.4 on AMD RV710" When I switch my laptop on, the screen stays black and the harddisk activity led keeps burning - not flickering, but continuously burning. No useful activity seems to be happening. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: kwin DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Fri Apr 1 22:24:07 2011 DistUpgraded: Log time: 2011-03-20 17:03:20.838900 DistroCodename: natty DistroVariant: kubuntu GraphicsCard: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9033] MachineType: Sony Corporation VGN-SR51MF_S ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=da81fb40-de8a-4d52-a359-76d6185050a9 ro splash quiet vt.handoff=7 Renderer: Unknown SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to natty on 2011-03-20 (12 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R4090Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4090Y1:bd08/05/2009:svnSonyCorporation:pnVGN-SR51MF_S:pvrC6025431:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR51MF_S dmi.product.version: C6025431 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.4git20110322-0ubuntu5 version.libdrm2: libdrm2 2.4.23-1ubuntu5 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/747627/+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 747627] Re: Sony VAIO VGN-SR51MF/S does not wake up from sleep
(on the same machine type) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/747627 Title: Sony VAIO VGN-SR51MF/S does not wake up from sleep Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Binary package hint: xserver-xorg-video-ati I'm using Kubuntu 11.04 beta, but this bug was already present in previous versions of (K)Ubuntu. My laptop is a Sony VAIO VGN-SR51MF/S. The video card is an ATI Radeon Mobility HD4570. glxinfo says the opengl renderer string is "OpenGL renderer string: Gallium 0.4 on AMD RV710" When I switch my laptop on, the screen stays black and the harddisk activity led keeps burning - not flickering, but continuously burning. No useful activity seems to be happening. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: kwin DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Fri Apr 1 22:24:07 2011 DistUpgraded: Log time: 2011-03-20 17:03:20.838900 DistroCodename: natty DistroVariant: kubuntu GraphicsCard: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9033] MachineType: Sony Corporation VGN-SR51MF_S ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=da81fb40-de8a-4d52-a359-76d6185050a9 ro splash quiet vt.handoff=7 Renderer: Unknown SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to natty on 2011-03-20 (12 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R4090Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4090Y1:bd08/05/2009:svnSonyCorporation:pnVGN-SR51MF_S:pvrC6025431:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR51MF_S dmi.product.version: C6025431 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.4git20110322-0ubuntu5 version.libdrm2: libdrm2 2.4.23-1ubuntu5 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/747627/+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 202850] Re: Rhythmbox doesn't warn if hfsplus isn't installed
This is still true for Precise Pangolin. Wiped an iPod Classic on a Mac, then connected it to an Ubuntu box with Rhythmbox. Trying to save tracks to it would result in crashing Rhythmbox. No warning, no explanation, just crashes. Yes, this indeed is a bug. ** Changed in: rhythmbox (Ubuntu) Status: Invalid => Confirmed -- 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/202850 Title: Rhythmbox doesn't warn if hfsplus isn't installed Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Binary package hint: rhythmbox I read in the ubuntuusers.de-wiki that you could only write on the iPod-filesystem if hfsplus is installed. Rhythmbox doesn't warn you at all if you try to write on your iPod without hfsplus installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/202850/+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
