[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
** Tags added: eoan ** Tags added: bionic -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+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 1839777] Re: PC frezzes under NO heavy workload and gnome-shell.crash is created
I'm not sure any crash file ending in "122.crash" would be related because 122 means it was probably the login screen, not your actual session. Also that crash report seems to be unusable: https://errors.ubuntu.com/oops/406f2e9c-bc5b-11e9-a5ca-fa163e6cac46 Please: 1. Run: lspci -k > pci.txt and attach the file 'pci.txt'. 2. Reproduce the freeze again, then reboot and run: journalctl -b-1 > prevboot.txt and attach the file 'prevboot.txt'. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1839777 Title: PC frezzes under NO heavy workload and gnome-shell.crash is created Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I am in any program, mostly happen in Blender since I spend most time in it, PC freezes and becomes unresponsive and I need to hold down Power button to shut it down. After booting I get send report pop up but it doesn't work it doesn't give me additional dialog window with information to finalize report. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at first (I reported to them but got ignore because of hardware) This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). If you need any more info let me know. I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. Here is whoopsie ID just in case.. https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1 I'd upload .crash but I think it has sensitive data so I won't do that if there is a way to deliver safely let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Aug 11 19:49:05 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839777/+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 1839687] Re: GDM displays black screen for a few seconds after resuming from suspend while using Nvidia proprietary drivers
** Tags added: nvidia ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1839687 Title: GDM displays black screen for a few seconds after resuming from suspend while using Nvidia proprietary drivers Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: What I expected to happen: GDM quickly appears after resuming What happened instead: A black screen appears and GDM is slow to show up After I suspend my laptop with Ubuntu 18.04.3 by closing it, GDM 3.28.3-0ubuntu18.04.4 takes several seconds to show up when I resume the computer. When the screen is black, only the cursor is visible. I'm using the Nvidia proprietary 430 drivers, but this issue already happened in version 390. If I use the Nvidia panel to switch to Intel graphics, GDM appears immediately after resuming. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 9 20:42:15 2019 InstallationDate: Installed on 2019-05-14 (87 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-05-14T20:04:13.489887 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1839687/+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 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
** Summary changed: - System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. + [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update ** Tags added: amdgpu -- 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/1839758 Title: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. Status in linux package in Ubuntu: New Bug description: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2018-03-26 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming K7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se3 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming K7 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+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 1839637] Re: Display driver missing
Please: 1. Switch out of recovery mode and boot normally so as to reproduce the bug. 2. Reboot again into recovery mode and then run: journalctl -b-1 > preboot.txt and then attach the file 'prevboot.txt' here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1839637] Re: Display driver missing
This sounds like a regression of bug 1727356. And it appears the patch for that bug was dropped in mutter version: 3.28.3+git20190124-0ubuntu18.04.1 because it was upstreamed and is in mutter version 3.28.4. And still is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1839637] Re: [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied
Oh, it's not a bug. Your machine is just stuck in recovery mode: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset ** Summary changed: - [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied + Display driver missing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1839637] Re: Display driver missing
It appears you have an Intel CPU/GPU (Core 2 Duo E4500) and the Xorg modesetting driver is failing to talk to the kernel driver properly: [63.574] (EE) modeset(0): drmSetMaster failed: Permission denied ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Display driver missing + [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1839637] Re: Display driver missing
Can you please attach a photo or other evidence explaining how the display driver is "missing"? It's meant to be missing in recovery mode, so ignore that part. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C
It's difficult because it seems only certain laptop models will be affected very often. And while no developers are affected by the bug then it's unlikely to get fixed. Because nobody with the ability to fix the bug has the hardware to reproduce the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Tags removed: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+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 1076499] Re: DVD AC-3 Audio is played in stereo in passthrough mode
Can you state which current Ubuntu versions are still affected by this bug? ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1076499 Title: DVD AC-3 Audio is played in stereo in passthrough mode Status in Totem: Unknown Status in totem package in Ubuntu: Incomplete Bug description: This is related to Bug #28177. Totem can play an pure ac3 sound file and it is recognized as Dolby Digital source by my amplifier. This is not the case with DVDs! With Totem, DVDs are always recognized by my amp as stereo. Playing the same DVD with vlc-player, Dolby Digital is recognized fine. Totem shows in properties that the DVD has "Dobly Digital (AC-3) codec. This was tested with totem 3.0.1 on Ubuntu 12.4 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1076499/+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 1837087] Re: gnome-shell/cinnamon crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1
** Summary changed: - gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. + gnome-shell/cinnamon crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. -- 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/1837087 Title: gnome-shell/cinnamon crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in cinnamon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
To check, please upload the output of the command as below: ls /lib/modules/`uname -r`/updates/dkms -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in cinnamon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087/+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 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cinnamon (Ubuntu) Status: New => Confirmed -- 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/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in cinnamon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087/+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 1838919] Re: Slow and lost keyboard and mouse events
If you're running on Wayland it might be related to this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you experience the same issue) is in
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510#note_577952
All this doesn't happen on X11, though.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1510
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
--
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/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last
few weeks and is now so bad I can hardly type an email (or this bug
report!) without having to fix many typos.
journalctl shows many different gnome errors, so it is difficult to
figure out which is the underlying cause and which are simply
collateral damage.
There are two sequences that appear first after a reboot, and the
first of these has been reported many times on ubuntu releases going
back for years:-
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be
loaded.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module
"canberra-gtk-module"
and
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG]
Registering StatusNotifierItem
:1.89/org/ayatana/NotificationItem/software_update_available
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
Is this a recent regression? I know for sure the system wasn't this
unresponsive 3 weeks ago, but I cannot be sure when it started to go
wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
fiddled around with distance and battery state until I was sure the
problem was somewhere else and started to check the system log.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 5 11:53:37 2019
InstalledPlugins:
gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1
[Desktop-packages] [Bug 1332847] Re: Switching from russian to chinese does not work
just note the default alphabet for pinyin is latin, not anything else. We want it just work right out of the box, correct? Well, in 99.9% of usecases. So user (any user, nub, advanced, etc) installs it and uses it. With currently used 'default' approach, switching to the method does not yields right layout. How many languages are there? How many of them use pure latin alphabet (and thus compatible 'default' layout)? diving latter by former you will get the percentage when it works (I suppose it will be something around 50%. an exact figure can be taken by reviewing all the languages with their respective layouts in conjunction with available input methods. Hard to do, no doubt). Using 'en' layout resolves the issue, by forcing an environment to switch to this layout, and anyone can type hanzi seamless. Thus we have uniformity. If you want to reuse dvorak layout (just for example), then you have a choice to fix it by supplying an exact layout using either available means (e.g. ibus-anthy, and such). It is for advanced users. "but it would make it harder for users who prefer some other underlying layout when using respective input method. It seems that they preferred the flexibilty which "default" offers." Could you estimate how many there is such an users? I think just a units of percents, and it seems they are a kind of 'advanced' users, who is able to make fine tuning of their software on their own. Usually (99.9%?) latin alphabet is engraved on keyboards using plain QWERTY, right? It is why "en-us", for example, is right candidate to the 'right' input method for pinyin. just IMHO)) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1332847 Title: Switching from russian to chinese does not work Status in ibus-anthy package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Confirmed Status in ibus-pinyin package in Ubuntu: Confirmed Bug description: There are three languages installed: en, ru, chinese pinyin (adjusted to be switched in this exact order). Switching en->ru works fine. Next switching ru->cn leaves the keyboard in russian thus impossible to enter chinese. Switching in reverse order en->cn works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 02:54:38 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/ibus/ibus-engine-pinyin InstallationDate: Installed on 2014-06-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1332847/+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 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right
For what it's worth I'm getting a very similar issue on Linux Mint Cinnamon after the update from 19.1 to 19.2. The error is: cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. I've found that the positions of monitors in a dual monitor setup dictates whether or not the DE crashes on startup. See this thread: https://github.com/linuxmint/cinnamon/issues/8754 Hopefully the problem is identical for you guys and a patch can fix both issues at once. ** Bug watch added: github.com/linuxmint/cinnamon/issues #8754 https://github.com/linuxmint/cinnamon/issues/8754 ** Also affects: cinnamon (Ubuntu) Importance: Undecided Status: New -- 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/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in cinnamon package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087/+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 1839782] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 1501049 *** https://bugs.launchpad.net/bugs/1501049 ** Description changed: $ LANGUAGE=C totem Click 'Channels' - Click 'MyCloudEX2Ultra' + Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 - () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 - g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 + () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 + g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1839782 Title: totem crashed with SIGABRT Status in totem package in Ubuntu: New Bug description: $ LANGUAGE=C totem Click 'Channels' Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1839782/+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 1332847] Re: Switching from russian to chinese does not work
Just to clarify: When saying that there is no "right" or "wrong" I meant the configuration of respective input method, i.e. "default" vs. some specific layout. We are of course agreed on the fact that e.g. a Russian layout is not compatible with an input method, which - as you say - expects latin letters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1332847 Title: Switching from russian to chinese does not work Status in ibus-anthy package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Confirmed Status in ibus-pinyin package in Ubuntu: Confirmed Bug description: There are three languages installed: en, ru, chinese pinyin (adjusted to be switched in this exact order). Switching en->ru works fine. Next switching ru->cn leaves the keyboard in russian thus impossible to enter chinese. Switching in reverse order en->cn works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 02:54:38 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/ibus/ibus-engine-pinyin InstallationDate: Installed on 2014-06-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1332847/+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 1332847] Re: Switching from russian to chinese does not work
@gunnarhj you are right, this is upstream issue. And you are wrong about "right" and "wrong" layouts for this input method. Pinyin implies latin letters input only. So, for example, neither of languages of ex-USSR is suited for pinyin. Maybe some/many others as well. When we switching to pinyin we expect just to start typing and get hanzi, not anything else. En us is common input method, any keyboard has it, so it seems reasonable to the method to have it as standard (right) input method. Just IMHO )) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1332847 Title: Switching from russian to chinese does not work Status in ibus-anthy package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Confirmed Status in ibus-pinyin package in Ubuntu: Confirmed Bug description: There are three languages installed: en, ru, chinese pinyin (adjusted to be switched in this exact order). Switching en->ru works fine. Next switching ru->cn leaves the keyboard in russian thus impossible to enter chinese. Switching in reverse order en->cn works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 02:54:38 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/ibus/ibus-engine-pinyin InstallationDate: Installed on 2014-06-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1332847/+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 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04
When I log in to my (regular user) account early morning, the Switch User menu item is not present. When I log out late in the evening, the Switch User menu item is present. This is reproducible day in, day out. This is the case even on days when there are no system updates or upgrades at all. -- 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/1825544 Title: Switch User menu item gone after upgrade to Ubuntu 19.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the switch user menu is gone, even though org.gnome.desktop.lockdown disable-user-switching is false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825544/+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 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+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 1839782] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 1501049 *** https://bugs.launchpad.net/bugs/1501049 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1501049, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1839782/+attachment/5282053/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282055/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282061/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282062/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282063/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282064/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1839782/+attachment/5282065/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1501049 totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1839782 Title: totem crashed with SIGABRT Status in totem package in Ubuntu: New Bug description: $ LANGUAGE=C totem Click 'Channels' Click 'MyCloudEX2Ultra' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1839782/+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 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04
Following up to my remarks from yesterday: when I logged out of my primary account, I DID see a Switch User menu option from my secondary account. When I returned to the primary account, Switch User was not present. But that was yesterday. On reboot today, Switch User has reappeared in my primary account. Perhaps a patch has fixed the problem? -- 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/1825544 Title: Switch User menu item gone after upgrade to Ubuntu 19.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the switch user menu is gone, even though org.gnome.desktop.lockdown disable-user-switching is false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825544/+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 1839777] Re: PC frezzes under NO heavy workload and gnome-shell.crash is created
** Description changed: When I am in any program, mostly happen in Blender since I spend most time in it, PC freezes and becomes unresponsive and I need to hold down Power button to shut it down. - After booting I get send report pop up but it doesn't work. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at firts (I reported to them but got ignore because of hardware) - This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). + After booting I get send report pop up but it doesn't work it doesn't give me additional dialog window with information to finalize report. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at first (I reported to them but got ignore because of hardware) + This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). If you need any more info let me know. + + I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. + Here is whoopsie ID just in case.. https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1 + I'd upload .crash but I think it has sensitive data so I won't do that if there is a way to deliver safely let me know. + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Aug 11 19:49:05 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1839777 Title: PC frezzes under NO heavy workload and gnome-shell.crash is created Status in gnome-shell package in Ubuntu: New Bug description: When I am in any program, mostly happen in Blender since I spend most time in it, PC freezes and becomes unresponsive and I need to hold down Power button to shut it down. After booting I get send report pop up but it doesn't work it doesn't give me additional dialog window with information to finalize report. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at first (I reported to them but got ignore because of hardware) This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). If you need any more info let me know. I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. Here is whoopsie ID just in case.. https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1 I'd upload .crash but I think it has sensitive data so I won't do that if there is a way to deliver safely let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Aug 11 19:49:05 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839777/+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 1839777] [NEW] PC frezzes under NO heavy workload and gnome-shell.crash is created
Public bug reported: When I am in any program, mostly happen in Blender since I spend most time in it, PC freezes and becomes unresponsive and I need to hold down Power button to shut it down. After booting I get send report pop up but it doesn't work it doesn't give me additional dialog window with information to finalize report. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at first (I reported to them but got ignore because of hardware) This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). If you need any more info let me know. I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. Here is whoopsie ID just in case.. https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1 I'd upload .crash but I think it has sensitive data so I won't do that if there is a way to deliver safely let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Aug 11 19:49:05 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1839777 Title: PC frezzes under NO heavy workload and gnome-shell.crash is created Status in gnome-shell package in Ubuntu: New Bug description: When I am in any program, mostly happen in Blender since I spend most time in it, PC freezes and becomes unresponsive and I need to hold down Power button to shut it down. After booting I get send report pop up but it doesn't work it doesn't give me additional dialog window with information to finalize report. Anyway I found _usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not blender which I thought at first (I reported to them but got ignore because of hardware) This happens when I don't have any complex object in Blender or other software (browsing etc) it just happens randomly withouth any specific steps and I am not 100% sure but I think it only happens if laptop was in sleep mode (lid closed). If you need any more info let me know. I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. Here is whoopsie ID just in case.. https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1 I'd upload .crash but I think it has sensitive data so I won't do that if there is a way to deliver safely let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sun Aug 11 19:49:05 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839777/+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 982526] Re: remmina crashed with Segmentation fault (core dumped)
Unfortunately, i removed the file before reporting the turnaround to check the theory was good. I forgot to make a backup. But you can see in the strace into the "read" line that the content of the file si not a content of a .remmina file compared to other files that start with "[remmina]\nssh_..." This track is for me enough to say that the file was corrupted (it has a binary content of \0 instead of text content). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/982526 Title: remmina crashed with Segmentation fault (core dumped) Status in remmina package in Ubuntu: Expired Bug description: When trying to connect to terminal server remmina chrases. uros@kokulator:~$ remmina Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. (remmina:22754): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' connected to 192.168.1.17:3389 Segmentation fault (core dumped) Ubuntu version: Description:Ubuntu precise (development branch) Release:12.04 uros@kokulator:~$ apt-cache policy remmina remmina: Installed: 1.0.0-1ubuntu5 Candidate: 1.0.0-1ubuntu5 Version table: *** 1.0.0-1ubuntu5 0 500 http://si.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: remmina 1.0.0-1ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 20:57:43 2012 ExecutablePath: /usr/bin/remmina InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120415) ProcCmdline: remmina ProcEnviron: SHELL=/bin/bash TERM=xterm LANG=en_GB.UTF-8 LANGUAGE=en_GB Signal: 6 SourcePackage: remmina StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: remmina crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (nautilus:4333): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' (nautilus:4333): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/982526/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Hello. Sorry for writing post by post, but there still are problems with Mousepad and 'connecting to accessibility bus' during editing any file. Here is an example: ,[ $ mousepad /usr/bin/example ] | ** (mousepad:14099): WARNING **: Couldn't connect to accessibility bus: | Failed to connect to socket /tmp/dbus-Z3dGTATnQK: Connection refused ` Note: the same WARNING message is displayed no matter if 'sudo(8)' command is being used. (However, it seems it is not a rule - if I remember correctly, there wasn't such a message earlier. I mean a couple months ago etc. But I could be wrong.) If it's about release, Mousepad and Xfce4 version informations, everything is the same as above - in my previous post. By the way: because there is not any reaction on this issue/bug, maybe it should be reported once again, but this time, choosing different 'Affects'? What do you think? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1731454] Re: Video doesn’t play in the right screen on entering full-screen mode while using two monitors
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Firefox since that time. Do you still see a problem related to the one that you reported when using a currently supported version of Firefox? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Description changed: O quando estou com 2 monitores o e ativo o modo Tela Cheia do video o video sai do monitor de origem e vai para o outro monitor secundario. + + Google translated this as: + + When I have 2 monitors and activates the Full Screen mode of the video + the video leaves the source monitor and goes to the other secondary + monitor. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: krashtime 1715 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: krashtime 1715 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Nov 10 08:15:13 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: - default via 192.168.15.1 dev wlp2s0 proto static metric 600 - 169.254.0.0/16 dev wlp2s0 scope link metric 1000 - 192.168.15.0/24 dev wlp2s0 proto kernel scope link src 192.168.15.41 metric 600 + default via 192.168.15.1 dev wlp2s0 proto static metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.15.0/24 dev wlp2s0 proto kernel scope link src 192.168.15.41 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RelatedPackageVersions: adobe-flashplugin 1:20171025.1-0ubuntu0.16.04.1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd03/17/2017:svnAcer:pnAspireVX5-591G:pvrV1.05:rvnKBL:rnWish_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.name: Aspire VX5-591G dmi.product.version: V1.05 dmi.sys.vendor: Acer ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1731454 Title: Video doesn’t play in the right screen on entering full-screen mode while using two monitors Status in firefox package in Ubuntu: Incomplete Bug description: O quando estou com 2 monitores o e ativo o modo Tela Cheia do video o video sai do monitor de origem e vai para o outro monitor secundario. Google translated this as: When I have 2 monitors and activates the Full Screen mode of the video the video leaves the source monitor and goes to the other secondary monitor. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krashtime 1715 F pulseaudio BuildID: 20171003101344 Channel:
[Desktop-packages] [Bug 1503024] Re: Firefox text windows pick the wrong language by default
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu and Firefox since that time. Does anyone still see a problem related to the one that was reported when using a currently supported version of Firefox? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Tags added: wily ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1503024 Title: Firefox text windows pick the wrong language by default Status in firefox package in Ubuntu: Incomplete Bug description: Fully up-to-date Wily, although this has been going on for a long time. Use Firefox to e.g. view Facebook. Start writing some new status and notice that *all* your English words are flagged as misspelled. Right click to bring up the Languages menu and notice that Arabic (Qatar) is the default language, not English. Locale is clearly en_US.UTF-8. Use the Language menu to choose English (United States) and the autospell works correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1503024/+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 1732374] Re: does not store the language change settings
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago. There have been many changes in Ubuntu and Firefox since that time. Do you still see a problem related to the one that you reported when using the currently supported versions of Firefox? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1732374 Title: does not store the language change settings Status in firefox package in Ubuntu: Incomplete Bug description: does not restore the language change settings ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simone 1575 F pulseaudio BuildID: 20171003101020 Channel: Unavailable CurrentDesktop: Unity Date: Wed Nov 15 09:29:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-03-29 (961 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 600 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.101 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101020 (In use) RelatedPackageVersions: adobe-flashplugin 1:20170808.1-0ubuntu0.16.04.1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Spring Peak dmi.board.vendor: Olivetti dmi.board.version: OLIBOOK S1530 dmi.chassis.type: 10 dmi.chassis.vendor: Olivetti dmi.chassis.version: OLIBOOK S1530 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0.4:bd07/11/2011:svnOlivetti:pnSpringPeak:pvrOLIBOOKS1530:rvnOlivetti:rnSpringPeak:rvrOLIBOOKS1530:cvnOlivetti:ct10:cvrOLIBOOKS1530: dmi.product.name: Spring Peak dmi.product.version: OLIBOOK S1530 dmi.sys.vendor: Olivetti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732374/+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 1332847] Re: Switching from russian to chinese does not work
I have gained some more insight on this topic lately. There is no "right" or "wrong" layout value in IBus plugins like these packages. We have reasons to assume that "default" is a deliberate decision after a trade-off between different goals. A hard coded layout would prevent issues like the one reported in this bug report, but it would make it harder for users who prefer some other underlying layout when using respective input method. It seems that they preferred the flexibilty which "default" offers. It's worth noting that the ibus-anthy setup GUI allows the user to specify the layout (the Typing Method tab). To me that appears to be the optimal solution, and it's probably a good idea to encourage the upstream developers of other input methods to do the same. But such a change won't happen in Ubuntu only. Please submit upstream issues if you want it to be considered by the upstream developers. Still keeping this bug report open for now, since this discussion may be of some interest. ** Changed in: ibus-anthy (Ubuntu) Status: New => Fix Released ** Changed in: ibus-libpinyin (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Confirmed ** Changed in: ibus-pinyin (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ibus-pinyin (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-anthy in Ubuntu. https://bugs.launchpad.net/bugs/1332847 Title: Switching from russian to chinese does not work Status in ibus-anthy package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Confirmed Status in ibus-pinyin package in Ubuntu: Confirmed Bug description: There are three languages installed: en, ru, chinese pinyin (adjusted to be switched in this exact order). Switching en->ru works fine. Next switching ru->cn leaves the keyboard in russian thus impossible to enter chinese. Switching in reverse order en->cn works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 02:54:38 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/ibus/ibus-engine-pinyin InstallationDate: Installed on 2014-06-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1332847/+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 1778069] Re: [xfce] nautilus don't open files if set as default file manager
Will the fix be released for 18.04 also? Thx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in Exo: Fix Released Status in exo package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+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 1785063] Re: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all
** Also affects: sound-2.6 Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1785063 Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound at all, through speakers or headphones jack. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natty 4286 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 2 15:07:12 2018 InstallationDate: Installed on 2017-10-12 (293 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1248 F pulseaudio natty 4286 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-04-04 (120 days ago) dmi.bios.date: 06/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02HAC.004.170626.WY.1442 dmi.board.asset.tag: No Asset Tag dmi.board.name: SM-W720NZKBBTU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8766A2S-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKBBTU:rvrSGL8766A2S-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A: dmi.product.family: SAMSUNG GALAXY dmi.product.name: Galaxy Book 12 dmi.product.version: P02HAC dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-13T14:38:49.320280 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1785063/+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 1839758] Re: System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
** Summary changed: - System lock-up with VMC page fault since HWE kernel update. + System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. -- 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/1839758 Title: System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. Status in xorg package in Ubuntu: New Bug description: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2018-03-26 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming K7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se3 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming K7 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1839758/+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 1839759] [NEW] Gdm3 asks password randomly when automatic login is enabled
Public bug reported: Ubuntu 18.04.3 up to date to latest @ 11/8/2019 with kernel: 5.0.0-23-generic #24~18.04.1-Ubuntu Gdm3 asks randomly for the user password at login, when automatic login is enabled I did not use seahorse yet, just system settings/details/users to enable auto login when filing the bug, it asked me to attach /etc/gdm3/custom.conf as it was modified but i never edited it myself. I cannot reproduce this, this happens at random on cold boots. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:25:49 2019 InstallationDate: Installed on 2019-05-18 (85 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-05-18T14:43:46.987133 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1839759 Title: Gdm3 asks password randomly when automatic login is enabled Status in gdm3 package in Ubuntu: New Bug description: Ubuntu 18.04.3 up to date to latest @ 11/8/2019 with kernel: 5.0.0-23-generic #24~18.04.1-Ubuntu Gdm3 asks randomly for the user password at login, when automatic login is enabled I did not use seahorse yet, just system settings/details/users to enable auto login when filing the bug, it asked me to attach /etc/gdm3/custom.conf as it was modified but i never edited it myself. I cannot reproduce this, this happens at random on cold boots. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:25:49 2019 InstallationDate: Installed on 2019-05-18 (85 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-05-18T14:43:46.987133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1839759/+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 1839758] [NEW] System lock-up with VMC page fault since HWE kernel update.
Public bug reported: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2018-03-26 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming K7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se3 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming K7 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze raven ridge 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/1839758 Title: System lock-up with VMC page fault since HWE kernel update. Status in xorg package in Ubuntu: New Bug description: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if
[Desktop-packages] [Bug 1307717] Re: multiple problems with new chromium-browser
This multiple issue bug report was marked incomplete over 5 years ago but did not expire due to the bug watches, three of which were added after comment #25 without explanation. Upstream bugs: #363053 was closed "WontFix" on 2014-04-14 as NPAPI plugins no longer supported. #363921 is a duplicate of #363088 #363088 was closed "Fixed" on 2014-05-01 (keyboard input ignored) #99369 was closed "WontFix" on 2011-10-11 as side tabs were experimental so removed #188 and its many duplicates refer to the usability of Chromium when a very large number of tabs are opened but this issue was not referred to when this bug report was opened. There have been no comments here for over 5 years and further to comments #24 and #25 I'm closing this as being fixed as recent releases of Chromium don't seem to be affected by the reported problems. Anyone still experiencing any of the issues noted above should open a new bug report for each issue. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1307717 Title: multiple problems with new chromium-browser Status in chromium-browser package in Ubuntu: Fix Released Bug description: Hi Chromium-browser was just updated and there are multiple problems with it. * icedtea-plugin not detected. * pepper seems to be the only API supported now. * Maximizing/normalizing the window the top right part of the window is not redrawn. * The font size in the address line is too huge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9 Uname: Linux 3.13.0-24-lowlatency i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Mon Apr 14 22:59:57 2014 Desktop-Session: DESKTOP_SESSION = kde-plasma XDG_CONFIG_DIRS = /etc/xdg/xdg-kde-plasma:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-12-24 (111 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" . /usr/lib/pepflashplugin-installer/pepflashplayer.sh gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2013-12-24T14:26:50.548847 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1307717/+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 982526] Re: remmina crashed with Segmentation fault (core dumped)
Laurent Destailleur (eldy): 1) Could you please attach the file so folks may attempt reproduce and see if in fact it is a duplicate? 2) To clarify, how did you confirm the file is corrupted versus Remmina is not handling a properly formatted file? 3) It would be helpful if you filed a new report via a terminal to review debugging logs: ubuntu-bug remmina Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/982526 Title: remmina crashed with Segmentation fault (core dumped) Status in remmina package in Ubuntu: Expired Bug description: When trying to connect to terminal server remmina chrases. uros@kokulator:~$ remmina Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin SFTP (type=Protocol) registered. Remmina plugin SSH (type=Protocol) registered. (remmina:22754): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' connected to 192.168.1.17:3389 Segmentation fault (core dumped) Ubuntu version: Description:Ubuntu precise (development branch) Release:12.04 uros@kokulator:~$ apt-cache policy remmina remmina: Installed: 1.0.0-1ubuntu5 Candidate: 1.0.0-1ubuntu5 Version table: *** 1.0.0-1ubuntu5 0 500 http://si.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: remmina 1.0.0-1ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 20:57:43 2012 ExecutablePath: /usr/bin/remmina InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120415) ProcCmdline: remmina ProcEnviron: SHELL=/bin/bash TERM=xterm LANG=en_GB.UTF-8 LANGUAGE=en_GB Signal: 6 SourcePackage: remmina StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: remmina crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (nautilus:4333): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' (nautilus:4333): Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/982526/+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 1839610] Re: If you travel BACK directly it kills visible scrolling performance
** Description changed: - Each time you travel to new location, e.g. - Home --> Documents + If you travel directly to location there you have been + with BACK command (alt left) for example then + scrolling seems to get worse. This is fixable + if you revisit recent files in a new window (ctrl n) + and close it (ctrl w). - you can improve performance if you open new window - and go to recent files (file history) and close - it (I use Ctrl W shortcut). - - Performance change is left while you - stay in the location if you travel - to a new destination you have to - again open new window and view again - recent files. + BACK? > open recent files in a new window and close it :)) ** Changed in: nautilus (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839610 Title: If you travel BACK directly it kills visible scrolling performance Status in nautilus package in Ubuntu: New Bug description: If you travel directly to location there you have been with BACK command (alt left) for example then scrolling seems to get worse. This is fixable if you revisit recent files in a new window (ctrl n) and close it (ctrl w). BACK? > open recent files in a new window and close it :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839610/+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 1839610] Re: If you travel BACK directly it kills visible scrolling performance
** Summary changed: - You can improve performance if you revisit history (recent files) + If you travel BACK directly it kills visible scrolling performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839610 Title: If you travel BACK directly it kills visible scrolling performance Status in nautilus package in Ubuntu: New Bug description: If you travel directly to location there you have been with BACK command (alt left) for example then scrolling seems to get worse. This is fixable if you revisit recent files in a new window (ctrl n) and close it (ctrl w). BACK? > open recent files in a new window and close it :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839610/+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 1076499] Re: DVD AC-3 Audio is played in stereo in passthrough mode
Issue now being tracked at: https://gitlab.gnome.org/GNOME/totem/issues/3 ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #3 https://gitlab.gnome.org/GNOME/totem/issues/3 ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #3 https://gitlab.gnome.org/GNOME/totem/issues/3 ** Changed in: totem Remote watch: GNOME Bug Tracker #693969 => gitlab.gnome.org/GNOME/totem/issues #3 ** Changed in: totem (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1076499 Title: DVD AC-3 Audio is played in stereo in passthrough mode Status in Totem: Unknown Status in totem package in Ubuntu: New Bug description: This is related to Bug #28177. Totem can play an pure ac3 sound file and it is recognized as Dolby Digital source by my amplifier. This is not the case with DVDs! With Totem, DVDs are always recognized by my amp as stereo. Playing the same DVD with vlc-player, Dolby Digital is recognized fine. Totem shows in properties that the DVD has "Dobly Digital (AC-3) codec. This was tested with totem 3.0.1 on Ubuntu 12.4 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1076499/+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 234349] Re: thunderbird opens pdf links (urls) in firefox and not directly in evince
Further to comment #10, where no information was provided, a test using Thunderbird 60.8 and Ubuntu 18.04 shows that there has been no progress on this request. So reverting status back to "New". ** Changed in: thunderbird (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/234349 Title: thunderbird opens pdf links (urls) in firefox and not directly in evince Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: Binary package hint: thunderbird I'm getting many emails with links to pdf files (such as "http://domain.com/document.pdf;). expected behavior: when clicking on the link, thunderbird should know this is pdf file and open evince (or any other pdf viewer) itself. current behavior: thunderbird opens firefox with the link location. firefox then asks me to open/save the pdf file. ProblemType: Bug Architecture: i386 Date: Fri May 23 17:55:11 2008 DistroRelease: Ubuntu 8.04 Package: mozilla-thunderbird 2.0.0.14+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: LC_TIME=en_DK PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/234349/+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 1831353] Re: can't browse pages
Bug report did not expire due to bug watch. Upstream bug may or may not be related to the problem but I'm closing this now as the reporter has not provided the information which was requested in comment #3. @Polaris, if this is still an issue or becomes an issue again then please provide the information requested in comment #3 and change the bug status to "New". ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/1831353 Title: can't browse pages Status in firefox package in Ubuntu: Invalid Bug description: Rebooting doesn't help. Using: Firefox: 67.0 64 bit OS: 16.04.6 Xubuntu Kernel 4.4.0-148-generic(x86_64) Desktop XFCE 4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 67.0+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20190517141553 Channel: Unavailable CurrentDesktop: XFCE Date: Sat Jun 1 16:26:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-12-26 (1253 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.199 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=67.0/20190517141553 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: CO96510J.86A.5869.2007.0327.0132 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DQ965GF dmi.board.vendor: Intel Corporation dmi.board.version: AAD41676-305 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCO96510J.86A.5869.2007.0327.0132:bd03/27/2007:svn:pn:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-305:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1831353/+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 1810902] Re: firefox picks unpredictable window for opening new content when using i3 as a window manager
Further to comment #8, the upstream bug was closed "VERIFIED FIXED" on 2019-02-21 with an additional report of being fixed on Ubuntu. ** Changed in: firefox (Ubuntu) Status: Incomplete => Fix Released -- 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/1810902 Title: firefox picks unpredictable window for opening new content when using i3 as a window manager Status in firefox package in Ubuntu: Fix Released Bug description: When a firefox instance is running with multiple windows, typing "firefox somepage" should open somepage in an existing window. Previously, that window was the last window accessed. Now, it is difficult to predict in which window the new tab will open. Indeed, it may open in a window in a different workspace even though the a window in the current workspace has been used more recently. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 64.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeff 4822 F pulseaudio /dev/snd/pcmC1D0p: jeff 4822 F...m pulseaudio /dev/snd/controlC1: jeff 4822 F pulseaudio BuildID: 20181207224003 Channel: Unavailable CurrentDesktop: i3 Date: Tue Jan 8 08:43:06 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-23 (1172 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.2.1 dev eth1 proto dhcp metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.87 metric 100 MostRecentCrashID: bp-a0847816-1a40-4e81-8110-dc8171180221 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003 (In use) Profile1 - LastVersion=50.0.2/20161130094234 (Out of date) Profile2 - LastVersion=56.0/20171003100843 (Out of date) Profile3 - LastVersion=64.0/20181207224003 (In use) Profile4 - LastVersion=60.0.2/20180607190419 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to bionic on 2018-06-14 (207 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog
How the heck I stop it? 'vendor preset: enabled'?!?! I reverted to apt- get remove rtkit ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in rtkit package in Ubuntu: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1547589/+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 1833617] Re: [amdgpu] screen freeze after suspend
I tested with the latest mainline kernel, 5.2.8 (also with 5.2) and the issue persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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 1547589] Re: rtkit-daemon flooding syslog
With latest update 18.4 lts I have this as well: writing 1GB per day in syslog. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in rtkit package in Ubuntu: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1547589/+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 1833617] Re: [amdgpu] screen freeze after suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Branch unlinked: lp:~mozillateam/firefox/firefox-beta.xenial -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: Fix Committed Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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
