[Desktop-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
usb_modeswitch did once upon a time check that a driver bound to the dongles interface(s) and if not then it did a modeprobe of the option serial driver. If it still didn't get option to bind then it added the dongles usb id to option's new_id and if the driver bound then it asked the user to report the usb id to usb kernel developers so that it could be properly added to the driver. There were too often conflicts between usb_modeswitch's driver loading and the kernels driver loading so it was decided after discussions with among others one of the modemmanager's developers to completely remove from usb_modeswitch any check for driver binding and forcing of driver binding. In short: usb_modeswitch is a userland switching utility which should leave the task of loading drivers to the kernel and not interfere with that. The driver checking/loading function was removed almost 3 years ago: "Version 2.4.0, 2016/06/12 ATTENTION: All ad-hoc driver binding code (using new_id driver attribute) removed - was a potential source of side effects and should now be obsoleted by good kernel support for modems" It seems that canonical doesn't agree and has re-introduced the driver checking/loading in their own implementation of later usb_modeswitch version. Regarding switching of E3531 with usb id 12d1:1f01 I can say that it is done with the linux switch message given by Huawei. They intend this device to become 12d1:14dc with a direct ethernet interface and no serial interfaces. Huawei has different switch messages for Windows, Mac, linux, and since a few years back also for Android. Early Huawei Android builds did only have support for ppp serial dial-up so the Android switch message brought up serial interfaces instead of net interfaces. usb_modeswitch is also used in Android and has the Android switch message included from version 2.5.1. usb_modeswitch can globally use the Android message by setting "HuaweiAltModeGlobal" in usb_modeswitch.conf or individually per modem by setting "HuaweiAltMode" in the modem config file. usb_modeswitch will continue to use the linux switch message for all Huawei modems, it is up to the end user to either select the right modem for his requirement (which often is serial ports for SMS operation) or to drop a new modem config file into /etc/usb_modeswitch.d which will override the one provided in /usr/share/usb_modeswitch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Triaged Status in usb-modeswitch package in Ubuntu: New Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A
[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1820561] [NEW] color picker window is not movable
Public bug reported: >From the highlight color button on the toolbar, you Left click on custom color. That opens a window called "Pick a color". If you click on the top bar of the window, it won't let you drag the window to the side so you can see what colors you highlighted in your document. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1820561 Title: color picker window is not movable Status in libreoffice package in Ubuntu: New Bug description: From the highlight color button on the toolbar, you Left click on custom color. That opens a window called "Pick a color". If you click on the top bar of the window, it won't let you drag the window to the side so you can see what colors you highlighted in your document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820561/+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 1820560] [NEW] color picker hex# field only takes 5 out of 6 chars
Public bug reported: >From the highlight color button on the toolbar, you Left click on custom color. That opens a window called "Pick a color". If you select the hex number field (which was filled with "ff"), and you type in 6 characters, it only takes the first 5 characters because it has still left the last "f". It ignores your last character entered, no matter what character you enter, and it leaves the f in the place of the 6th character. So then you have to take another step to select the "f" and delete it, or to put the cursor at the end of the line, backspace over the f, and enter whatever was supposed to be the 6th character. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1820560 Title: color picker hex# field only takes 5 out of 6 chars Status in libreoffice package in Ubuntu: New Bug description: From the highlight color button on the toolbar, you Left click on custom color. That opens a window called "Pick a color". If you select the hex number field (which was filled with "ff"), and you type in 6 characters, it only takes the first 5 characters because it has still left the last "f". It ignores your last character entered, no matter what character you enter, and it leaves the f in the place of the 6th character. So then you have to take another step to select the "f" and delete it, or to put the cursor at the end of the line, backspace over the f, and enter whatever was supposed to be the 6th character. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820560/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
What also happens is if you move a window the busy cursor halts. But this is just temporary, opening a new window causes it to start up again. So only way to really stop is too log out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+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 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
It's "2.5.2+repack0-2ubuntu1". ** Also affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Triaged Status in usb-modeswitch package in Ubuntu: New Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T22AV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family:
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
Any info on when's that going to be released? Can't find it. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1665554] Re: Rhythmbox GUI is flickering and not usable
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1665554 Title: Rhythmbox GUI is flickering and not usable Status in rhythmbox package in Ubuntu: Expired Bug description: When starting up rhythmbox the gui is somewhat distorted and not usable. The buttons and lists are shown randomly, and flickering while the mouse is moving. Once rhythmbox is started, the whole session is going nuts, even for other windows. :~/$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 :~/$ apt-cache policy rhythmbox rhythmbox: Installiert: 3.3-1ubuntu7 Installationskandidat: 3.3-1ubuntu7 Versionstabelle: *** 3.3-1ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rhythmbox 3.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 17 07:49:53 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (300 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1665554/+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 1775909] Re: Anytime when i start the Programm. It Closed and Crashed
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1775909 Title: Anytime when i start the Programm. It Closed and Crashed Status in rhythmbox package in Ubuntu: Expired Bug description: I have my Music on a Debian Server with a Samba share. In Unbuntu 16.04 was all good. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 8 19:04:21 2018 InstallationDate: Installed on 2018-04-27 (42 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1775909/+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 1811924] Re: package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/share/libreoffice/help/es/swriter.tree' before install
[Expired for libreoffice-l10n (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice-l10n (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1811924 Title: package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/share/libreoffice/help/es/swriter.tree' before installing new version: Input/output error Status in libreoffice-l10n package in Ubuntu: Expired Bug description: trying to run sudo apt upgrade and this happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libreoffice-help-es 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 Date: Wed Jan 16 05:15:07 2019 ErrorMessage: unable to make backup link of './usr/share/libreoffice/help/es/swriter.tree' before installing new version: Input/output error LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: libreoffice-l10n Title: package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/share/libreoffice/help/es/swriter.tree' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1811924/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Thanks for fixing this Alberto -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
Reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1075 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+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 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
Ah, yes I can reproduce it now. You have to open the text file by clicking on it, and not after opening gedit. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820542/+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 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
Using the supplied instructions I can't reproduce the bug. Any more hints? ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820542/+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 1820500] Re: gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag()
Looks similar to bug 1820556. ** Summary changed: - Agnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() + gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() + gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::TypeScript::Monitor() from js::jit::DoTypeMonitorFallback() -- 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/1820500 Title: gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::TypeScript::Monitor() from js::jit::DoTypeMonitorFallback() Status in gnome-shell package in Ubuntu: New Bug description: o arrastar os arquivos na área de trabalho não foram movidos e ficaram congelados na tela. Travou o computador e depois voltou ao normal. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 07:31:02 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 () at /lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820500/+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 1820556] Re: /usr/bin/gnome-shell:11:js::PrimitiveTypeFlag:js::TypeSet::hasType:js::HasTrackedPropertyType:js::AddTypePropertyId:js::AddTypePropertyId
Looks similar to bug 1820500. ** Summary changed: - /usr/bin/gnome-shell:11:js::PrimitiveTypeFlag:js::TypeSet::hasType:js::HasTrackedPropertyType:js::AddTypePropertyId:js::AddTypePropertyId + gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag from js::TypeSet::hasType from js::HasTrackedPropertyType from js::AddTypePropertyId from js::AddTypePropertyId ** Summary changed: - gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag from js::TypeSet::hasType from js::HasTrackedPropertyType from js::AddTypePropertyId from js::AddTypePropertyId + gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::HasTrackedPropertyType() from js::AddTypePropertyId() from js::AddTypePropertyId() -- 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/1820556 Title: gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::HasTrackedPropertyType() from js::AddTypePropertyId() from js::AddTypePropertyId() Status in gnome-shell 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.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/456e79f19058d9510c30dd6f41d00f2822174432 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/gnome-shell/+bug/1820556/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
Please try live booting Ubuntu 19.04 and tell us if it has the same bug: http://cdimages.ubuntu.com/daily-live/current/ If the bug is still present in 19.04 then please report it to the GNOME developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: osk ** Tags added: cosmic ** 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/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in gnome-shell package in Ubuntu: Incomplete Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820523/+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 1820490] Re: i find them while xdiagnose
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1820490 Title: i find them while xdiagnose Status in Ubuntu: Incomplete Bug description: these bugs must be cleans and further bugs should be reported ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 17 09:20:02 2019 DistUpgraded: 2019-03-15 15:41:59,975 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-02-26 (18 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=35f08810-0153-46db-9a01-b9159f8cb46e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (1 days ago) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0FKWR5 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 15 10:45:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820490/+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 1820556] [NEW] gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::HasTrackedPropertyType() from js::AddTypePropertyId() from js::A
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/456e79f19058d9510c30dd6f41d00f2822174432 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- 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/1820556 Title: gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag() from js::TypeSet::hasType() from js::HasTrackedPropertyType() from js::AddTypePropertyId() from js::AddTypePropertyId() Status in gnome-shell 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.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/456e79f19058d9510c30dd6f41d00f2822174432 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/gnome-shell/+bug/1820556/+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 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** Tags added: multimonitor -- 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/1820423 Title: monitors.xml is not parsed or applied correctly after reboot or shutdown Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally) ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown, then--problems until HDMI cable is unseated and rebooted again. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+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 1820355] Re: Firefox icon is blank in the launcher
** Summary changed: - Firefox icon missing + Firefox icon is blank in the launcher ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (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/1820355 Title: Firefox icon is blank in the launcher Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have firefox bookmarked in the gnome-shell dash. When starting the shell in disco, the firefox logo is missing and the launcher is a small but clickable blank area. If I use gnome-tweaks to change icon theme, the logo reappears for the rest of the session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 14:22:32 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (170 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820355/+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 1820371] Re: PCI/internal sound card not detected
The kernel is reporting zero supported sound cards: !!Soundcards recognised by ALSA !!- --- no soundcards --- ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1820371 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Incomplete Bug description: no sound in dell inspirion soundcard unknown ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Mar 16 06:55:24 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-03-15 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 04XH5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820371/+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 1820323] Re: xorg crash
Also, to help us find crashes from other people that are the same as this one, please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1820323 Title: xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+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 1820554] Re: /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:meta_gpu_kms_flip_crtc:retry_page_flips:g_main_dispatch
*** This bug is a duplicate of bug 1820331 *** https://bugs.launchpad.net/bugs/1820331 ** This bug has been marked a duplicate of bug 1820331 gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" -- 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/1820554 Title: /usr/bin/gnome- shell:6:g_assertion_message:g_assertion_message_expr:meta_gpu_kms_flip_crtc:retry_page_flips:g_main_dispatch Status in gnome-shell 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.32.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 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/gnome-shell/+bug/1820554/+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 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
Tracking in: https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 ** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" ** Description changed: + https://gitlab.gnome.org/GNOME/mutter/issues/506 + https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 + + --- + In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of package updates has stopped Apport from letting me report it until now, but the problem persists. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 11:22:20 2019 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1120 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell 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/libmutter-4.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd mock plugdev sambashare sbuild sudo wireshark separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" Status in Mutter: New Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/506 https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 --- In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of package updates has stopped Apport from letting me report it until now, but the problem persists. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 11:22:20 2019 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1120 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell 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/libmutter-4.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd mock plugdev sambashare sbuild sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+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 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1820423 Title: monitors.xml is not parsed or applied correctly after reboot or shutdown Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally) ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown, then--problems until HDMI cable is unseated and rebooted again. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423/+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 1820323] Re: xorg crash
Also, to help us find crashes from other people are the same as this one, please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1820323 Title: xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+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 1820554] [NEW] /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:meta_gpu_kms_flip_crtc:retry_page_flips:g_main_dispatch
*** This bug is a duplicate of bug 1820331 *** https://bugs.launchpad.net/bugs/1820331 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- 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/1820554 Title: /usr/bin/gnome- shell:6:g_assertion_message:g_assertion_message_expr:meta_gpu_kms_flip_crtc:retry_page_flips:g_main_dispatch Status in gnome-shell 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.32.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 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/gnome-shell/+bug/1820554/+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 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
*** This bug is a duplicate of bug 1820314 *** https://bugs.launchpad.net/bugs/1820314 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820314, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820314 [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq:timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock 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: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+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 1820303] Re: Ubuntu 18.04 LTS
Can you select the session you want on the login screen by clicking on the cog/gear icon? ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1820303 Title: Ubuntu 18.04 LTS Status in gdm3 package in Ubuntu: Incomplete Bug description: Failure to display prior desktop login GUI (Cinnamon). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 15 11:46:27 2019 DistUpgraded: 2019-03-15 10:30:23,145 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 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7] InstallationDate: Installed on 2019-03-11 (4 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK COMPUTER INC. X55U ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago) dmi.bios.date: 08/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55U.423 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55U dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X55U dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 15 11:19:59 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820303/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I hit this bug on Fedora 28 when using a third-party mesa build. Here's the ~/.drirc I used to fix this: This also fixed the timecode in Totem showing strange, rainbow colors, caused by the same thing. Repeat the application section as required for each program affected. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1820230] Re: spotify (snap) starts in fullscreen without windows decorations
Thanks. It looks like gnome-shell is generally doing the right thing. It notices an app is trying to place itself over the full screen and accepts that as a old-style fullscreen request. Nothing unusual there. Gnome Shell is behaving correctly for a window manager. The only problem here is that there's no way to escape (restore and resize) such automatic fullscreening in gnome-shell. But also I think that's normal. I'm not aware of any window managers that do offer that. So I don't think it's reasonable to ask for a gnome-shell enhancement to work around this problem. It's Spotify's fault for firstly suggesting it wants to be fullscreen and then not remembering that it requested fullscreen. ** Changed in: gnome-shell (Ubuntu) Status: New => Opinion -- 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/1820230 Title: spotify (snap) starts in fullscreen without windows decorations Status in gnome-shell package in Ubuntu: Opinion Bug description: Ubuntu Disco up to date spotify 1.1.0.237.g378f6f25-11 session: Ubuntu on Xorg 1 display screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch When spotify is closed in fullscreen mode, on next start it starts like a fullscreen app without any window decoration. There is then no way to control the app. window. The following message is displayed in the logs mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: Treating resize request of legacy application 0x421 as a fullscreen request Test Case: 1. Start Spotify 2. Switch to fullscreen (arrows on the bottom right corner) 3. Close Spotify with ALT+F4 4. Open Spotify again Actual Result The apps launches in fullscreen without any windows control and no way to switch to normal mode. Workaround click on the arrow to switch to fullscreen then again to switch to normal mode. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 15 10:38:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1704 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820230/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
** Tags added: disco ** Package changed: xorg (Ubuntu) => xorg-server (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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg-server package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1819943/+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 1819193] Re: Document search does not work
** Also affects: gnome-documents (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/1819193
Title:
Document search does not work
Status in gnome-documents package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
New
Bug description:
1. Description: Ubuntu 18.04.2 LTS
2. 3.28.3-0ubuntu0.18.04.4
3. I expect to be able to search document by content from the gnome shell
("Type to search..."). The option is enabled from settings.
4. Nothing happens. No documents are retrieved.
I get the following error message in logs repeatedly:
"Wrong number of result metas returned by search provider
org.gnome.Documents.desktop: expected 5 but got 0"
gnome-documents also gives this:
"JS ERROR: GLib.Error g-invoke-error-quark: Could not locate
gd_filename_strip_extension: (null)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-documents/+bug/1819193/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
fessmage, You don't have the fix installed. The fix is in version: 3.28.3+git20190124-0ubuntu18.04.1 (per comment #37) but is not released yet. You can download the .debs to try the fix from: https://launchpad.net/ubuntu/+source/gnome- shell/3.28.3+git20190124-0ubuntu18.04.1/+build/16422548 -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.
Can you please try some newer kernels? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1793595 Title: [radeon] Shell freezes, mostly when running chrome or editing text files. Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Freezes randomly, mostly when running chrome or editing text files. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 20 16:35:29 2018 DistUpgraded: 2018-08-28 16:25:11,641 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 ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] [1002:682c] (prog-if 00 [VGA controller]) Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e] InstallationDate: Installed on 2018-06-04 (108 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Sep 20 16:27:01 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8 inputDell KB216 Wired Keyboard KEYBOARD, id 9 inputDell KB216 Wired Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+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 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.
I just noticed you said "Cannot access the system remotely as well.", which suggests a kernel problem. Looking at your original kernel log you have: [ 15.680794] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac failed [ 15.712514] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac failed ... [ 22.768100] radeon_dp_aux_transfer_native: 242 callbacks suppressed ... [ 33.988147] radeon_dp_aux_transfer_native: 326 callbacks suppressed and in your most recent system log you have this error repeating again: Dec 03 09:44:34 avi kernel: [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac failed Dec 03 09:44:34 avi kernel: [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac failed While those messages might be harmless, they may also hint at a fault in the kernel graphics driver. -- 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/1793595 Title: [radeon] Shell freezes, mostly when running chrome or editing text files. Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Freezes randomly, mostly when running chrome or editing text files. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 20 16:35:29 2018 DistUpgraded: 2018-08-28 16:25:11,641 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 ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] [1002:682c] (prog-if 00 [VGA controller]) Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e] InstallationDate: Installed on 2018-06-04 (108 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Sep 20 16:27:01 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8 inputDell KB216 Wired Keyboard KEYBOARD, id 9 inputDell KB216 Wired Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
I forgot to mention that multi-monitors still won't work properly in Wayland sessions. You'll only get the speed of the slowest monitor. But a fix for that is coming eventually: https://gitlab.gnome.org/GNOME/mutter/merge_requests/73 If you experience the problem in Xorg then that's a new problem. But if true then we could reword bug 1730460 to include that, and discuss it there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Status in mutter source package in Disco: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+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 1774957] Re: Network icons in status menu disappearing
Marco, You are missing the fix for this bug. See comment #23. -- 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/1774957 Title: Network icons in status menu disappearing Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Status in gnome-shell source package in Disco: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 --- Ever since the update to Ubuntu 18.04 I'm having issues with the status menu at the top right of the screen. Normally you'd have a wired network connection icon displayed at the top without opening the menu. In my case it is not displayed half of the time. In the menu list no icon nor label is displayed for the wired connection menu item. When talking about half of the time it means that I can randomly make it display again when removing the USB network adapter and reconnecting it e.g. This does not work reliably though. When connecting to a VPN, normally you'd get an additional icon at the top. This is not the case any more, nor does the switch behind an activated VPN turns change to an active state. The result is that you can activate a VPN using the switch, but you can verify that it is activated, nor can you de-active the VPN through the menu. This does change in settings though. Wireless settings are no longer displayed in the menu at all. So no way to activate it or connect to a specific network. I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as network-manager-gnome, to no avail. Attached you'll find a screenshot illustrating the issue. You'll see two icons missing to the left of the volume icon, as well as the wireless menu missing completely and no icon and text label for the wired connection menu item. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 4 10:47:05 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (604 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
Remember this bug is closed for Gnome Shell per comment #126. But I understand that maybe some people are still experiencing similar problems. It appears to me one such similar problem that wouldn't have been fixed here is with laptop display switching where the set of connected displays changes (unlike a desktop). If you experience such problems with laptop display switching then please open a new bug by running: ubuntu-bug gnome-shell -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Fix Released Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 201391] Re: Headset volume control doesn't change headset volume
It's been over 9 years since this bug was closed. So if you'd like to discuss any problems you're still having today then it would be better to open a new bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/201391 Title: Headset volume control doesn't change headset volume Status in pulseaudio package in Ubuntu: Fix Released Bug description: I use Kubuntu Hardy and have a Plantronics USB headset that has its own volume and mute controls. When using its volume controls, they affect the master volume only and have no effect on the headset volume. I can only alter the headset volume by going into kmix and selecting the appropriate device and altering its PCM volume. The master volume setting should affect the headset volume too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/201391/+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 1820368] Re: x
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1820368 Title: x Status in Ubuntu: Incomplete Bug description: xx ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 16 04:31:02 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2017-05-23 (661 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4291BD2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291BD2 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: BB70354824 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4291BD2:pvrThinkPadX220:rvnLENOVO:rn4291BD2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291BD2 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 18:41:18 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 723 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820368/+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 1817924] Re: apps launched from gnome shell do not get input focus
** Changed in: gnome-shell Status: Unknown => 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/1817924 Title: apps launched from gnome shell do not get input focus Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
[58.994] Require OpenGL version 2.1 or later. [58.994] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. ok then, looks like -intel needs to be added back to xserver-xorg-video- all Recommends... sigh ** Package changed: xserver-xorg-video-intel (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Incomplete => Triaged -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1820543] [NEW] libreoffice snap can not see mounted volume
Public bug reported: I have a encrypted luks volume which is under lvm management. I mount it manually from a script. It's mounted to /opt1 the libreoffice snap does not see this mounted directory; it is not part of the filesystem known to the snap. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1820543 Title: libreoffice snap can not see mounted volume Status in libreoffice package in Ubuntu: New Bug description: I have a encrypted luks volume which is under lvm management. I mount it manually from a script. It's mounted to /opt1 the libreoffice snap does not see this mounted directory; it is not part of the filesystem known to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820543/+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 1820523] Re: OSK Enter and backspace keys don't work
** Package changed: gnome-settings-daemon (Ubuntu) => gdm3 (Ubuntu) ** Summary changed: - OSK Enter and backspace keys don't work + OSK Enter and backspace keys don't work in some text fields ** Description changed: - The enter and backspace keys on the Ubuntu On-screen keyboard don't - work. They don't work on Chromium and the apps menu, but work in gedit. + The enter and backspace keys on the Ubuntu On-screen keyboard don't work + in some instances. They don't work on Chromium and the apps menu, but + work in gedit. Ubuntu 18.10 ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work - in some instances. They don't work on Chromium and the apps menu, but + in some instances. They don't work in Chromium and the apps menu, but work in gedit. Ubuntu 18.10 ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work in some instances. They don't work in Chromium and the apps menu, but work in gedit. + The problem occurs in a laptop. I tested it on a desktop and it works + fine. + Ubuntu 18.10 ** Summary changed: - OSK Enter and backspace keys don't work in some text fields + OSK Enter and backspace keys don't work when typing in Greek ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work - in some instances. They don't work in Chromium and the apps menu, but - work in gedit. - - The problem occurs in a laptop. I tested it on a desktop and it works - fine. + when typing in Greek. Ubuntu 18.10 ** Summary changed: - OSK Enter and backspace keys don't work when typing in Greek + OSK Enter, space and backspace keys don't work when typing in Greek ** Description changed: - The enter and backspace keys on the Ubuntu On-screen keyboard don't work - when typing in Greek. + The enter, space and backspace keys on the Ubuntu On-screen keyboard + don't work when typing in Greek. Ubuntu 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in gdm3 package in Ubuntu: New Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820523/+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 1820542] [NEW] In a wayland session opening text file in gedit causes busy cursor
Public bug reported: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco regression reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in wayland package in Ubuntu: New Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version:
[Desktop-packages] [Bug 1811105]
Fixed, thanks! -- 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/1811105 Title: Browser hangs when 'open with' dialog opens. Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.04.1 LTS x86_64 with GNOME 3.28.3. 2) Firefox: Installed: 64.0+build3-0ubuntu0.18.04.1 3) Dialog box 'open as' to respond to click events in elements and whole browser not get inoperable. 4) Dialog box 'open as' hangs, gets inoperable to click commands (close, cancel, ok, save file) when trying to open some attacked file. My browser started to hang when the dialog 'open as' appears. It's very useful since it quickly opens an attached file from gmail or browsing pdf/doc files. When the dialog opens, both the dialog and the browser window get extremely slow and i have to click several times for the dialog to close. No other button responds and sometimes the crash dialog asks if i want to force quit or wait. I'm having this problem for two weeks now and got so annoyed that sadly had to switch back to chrome. This is a very nice feature that doesn't work on said browser. I already uninstalled/installed, cleaned data and installed a nightly build without success. I suspect it's something related to window manager or nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 64.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 3261 F pulseaudio BuildID: 20181207224003 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Jan 9 13:28:59 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 dhcp IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-11-14 (785 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-08-21 (140 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 234 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K45A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K45A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1811105/+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 1811105]
The release note at https://www.mozilla.org/en- US/firefox/66.0beta/releasenotes/ got mangled. It's displaying like this: Fixed an performance issue some Linux users experienced with the Downloads panel ([bug 1517101][1]). [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1517101 -- 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/1811105 Title: Browser hangs when 'open with' dialog opens. Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.04.1 LTS x86_64 with GNOME 3.28.3. 2) Firefox: Installed: 64.0+build3-0ubuntu0.18.04.1 3) Dialog box 'open as' to respond to click events in elements and whole browser not get inoperable. 4) Dialog box 'open as' hangs, gets inoperable to click commands (close, cancel, ok, save file) when trying to open some attacked file. My browser started to hang when the dialog 'open as' appears. It's very useful since it quickly opens an attached file from gmail or browsing pdf/doc files. When the dialog opens, both the dialog and the browser window get extremely slow and i have to click several times for the dialog to close. No other button responds and sometimes the crash dialog asks if i want to force quit or wait. I'm having this problem for two weeks now and got so annoyed that sadly had to switch back to chrome. This is a very nice feature that doesn't work on said browser. I already uninstalled/installed, cleaned data and installed a nightly build without success. I suspect it's something related to window manager or nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 64.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 3261 F pulseaudio BuildID: 20181207224003 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Jan 9 13:28:59 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 dhcp IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-11-14 (785 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-08-21 (140 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 234 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K45A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K45A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1811105/+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 1817924] Re: apps launched from gnome shell do not get input focus
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1749 https://gitlab.gnome.org/GNOME/gtk/issues/1749 ** Changed in: gnome-shell Status: Fix Released => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1043 => gitlab.gnome.org/GNOME/gtk/issues #1749 -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+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 1817924] Re: apps launched from gnome shell do not get input focus
** Changed in: gnome-shell Status: New => Fix Released -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+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 1820524] [NEW] Sync zziplib 0.13.62-3.2 (main) from Debian unstable (main)
Public bug reported: Please sync zziplib 0.13.62-3.2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: invalid mem access in zzip_disk_fread - debian/patches/CVE-2018-6381.patch: check sizes in zzip/memdisk.c. - CVE-2018-6381 * SECURITY UPDATE: alignment and bus errors in __zzip_fetch_disk_trailer - debian/patches/CVE-2018-6484.patch: check sizes in zzip/zip.c. - CVE-2018-6484 - CVE-2018-6541 - CVE-2018-6869 * SECURITY UPDATE: bus error in zzip_disk_findfirst - debian/patches/CVE-2018-6540.patch: check endbuf in zzip/mmapped.c. - CVE-2018-6540 * SECURITY UPDATE: invalid memory dereference - debian/patches/CVE-2018-7725.patch: check zlib space in zzip/memdisk.c, zzip/mmapped.c. - CVE-2018-7725 * SECURITY UPDATE: bus error in __zzip_parse_root_directory - debian/patches/CVE-2018-7726-1.patch: check rootseek and rootsize in zzip/zip.c. - debian/patches/CVE-2018-7726-2.patch: check rootseek in zzip/zip.c. - debian/patches/CVE-2018-7726-3.patch: check zz_rootsize in zzip/zip.c. - CVE-2018-7726 All CVE fixes are now in Debian, plus one new one (for CVE-2018-16548) that we don't currently have. Changelog entries since current disco version 0.13.62-3.1ubuntu1: zziplib (0.13.62-3.2) unstable; urgency=medium * Non-maintainer upload. * Invalid memory access in zzip_disk_fread (CVE-2018-6381) (Closes: #889096) * Reject the ZIP file and report it as corrupt if the size of the central directory and/or the offset of start of central directory point beyond the end of the ZIP file (CVE-2018-6484, CVE-2018-6541, CVE-2018-6869) (Closes: #889089) * bus error in zzip_disk_findfirst function in zzip/mmapped.c (CVE-2018-6540) (Closes: #923659) * out of bound read in mmapped.c:zzip_disk_fread() causes crash (CVE-2018-7725) (Closes: #913165) * Bus error in zip.c:__zzip_parse_root_directory() cause crash via crafted zip file (CVE-2018-7726) (Closes: #913165) * Memory leak triggered in the function __zzip_parse_root_directory in zip.c (CVE-2018-16548) (Closes: #910335) -- Salvatore Bonaccorso Mon, 04 Mar 2019 22:43:14 +0100 ** Affects: zziplib (Ubuntu) Importance: Wishlist Status: New ** Changed in: zziplib (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zziplib in Ubuntu. https://bugs.launchpad.net/bugs/1820524 Title: Sync zziplib 0.13.62-3.2 (main) from Debian unstable (main) Status in zziplib package in Ubuntu: New Bug description: Please sync zziplib 0.13.62-3.2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: invalid mem access in zzip_disk_fread - debian/patches/CVE-2018-6381.patch: check sizes in zzip/memdisk.c. - CVE-2018-6381 * SECURITY UPDATE: alignment and bus errors in __zzip_fetch_disk_trailer - debian/patches/CVE-2018-6484.patch: check sizes in zzip/zip.c. - CVE-2018-6484 - CVE-2018-6541 - CVE-2018-6869 * SECURITY UPDATE: bus error in zzip_disk_findfirst - debian/patches/CVE-2018-6540.patch: check endbuf in zzip/mmapped.c. - CVE-2018-6540 * SECURITY UPDATE: invalid memory dereference - debian/patches/CVE-2018-7725.patch: check zlib space in zzip/memdisk.c, zzip/mmapped.c. - CVE-2018-7725 * SECURITY UPDATE: bus error in __zzip_parse_root_directory - debian/patches/CVE-2018-7726-1.patch: check rootseek and rootsize in zzip/zip.c. - debian/patches/CVE-2018-7726-2.patch: check rootseek in zzip/zip.c. - debian/patches/CVE-2018-7726-3.patch: check zz_rootsize in zzip/zip.c. - CVE-2018-7726 All CVE fixes are now in Debian, plus one new one (for CVE-2018-16548) that we don't currently have. Changelog entries since current disco version 0.13.62-3.1ubuntu1: zziplib (0.13.62-3.2) unstable; urgency=medium * Non-maintainer upload. * Invalid memory access in zzip_disk_fread (CVE-2018-6381) (Closes: #889096) * Reject the ZIP file and report it as corrupt if the size of the central directory and/or the offset of start of central directory point beyond the end of the ZIP file (CVE-2018-6484, CVE-2018-6541, CVE-2018-6869) (Closes: #889089) * bus error in zzip_disk_findfirst function in zzip/mmapped.c (CVE-2018-6540) (Closes: #923659) * out of bound read in mmapped.c:zzip_disk_fread() causes crash (CVE-2018-7725) (Closes: #913165) * Bus error in zip.c:__zzip_parse_root_directory() cause crash via crafted zip file (CVE-2018-7726) (Closes: #913165) * Memory leak triggered in the function __zzip_parse_root_directory in zip.c (CVE-2018-16548) (Closes: #910335) -- Salvatore Bonaccorso Mon, 04 Mar 2019 22:43:14 +0100 To manage
[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial
I install 66.0 rc3 version from the beta channel of Mozilla in the opt folder and it run without issue -- 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/1819013 Title: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial Status in firefox package in Ubuntu: Confirmed Bug description: $ firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) Couldn't load XPCOM. $ ldd /usr/lib/firefox/libxul.so | head -1 /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 65.0.1+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic ppc64le AddonCompatCheckDisabled: False AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 7 10:00 seq crw-rw 1 root audio 116, 33 Mar 7 10:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20190215002040 Channel: Unavailable Date: Thu Mar 7 10:02:49 2019 ForcedLayersAccel: False InstallationDate: Installed on 2018-01-11 (419 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el (20170801) IpRoute: default via 10.128.60.1 dev enP2p1s0f0 10.128.60.0/25 dev enP2p1s0f0 proto kernel scope link src 10.128.60.99 NoProfiles: True PciMultimedia: ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239 ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition379411841110016 -2 ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu SMP Wed Jul 18 08:50:43 UTC 2018 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 16 cpu_coreson: Number of cores online = 16 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1819013/+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 1820523] [NEW] OSK Enter and backspace keys don't work
Public bug reported: The enter and backspace keys on the Ubuntu On-screen keyboard don't work. They don't work on Chromium and the apps menu, but work in gedit. Ubuntu 18.10 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1820523 Title: OSK Enter and backspace keys don't work Status in gnome-settings-daemon package in Ubuntu: New Bug description: The enter and backspace keys on the Ubuntu On-screen keyboard don't work. They don't work on Chromium and the apps menu, but work in gedit. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1820523/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
Same happens now here in ubuntu 18.04.2 LTS. When the system locks, I'm logged out and all applications (programs) stop. This behaviour came after a reboot, so maybe any updated module may be the culprit. It seems that the gnome shell crashes. See attached syslog. ** Attachment added: "Screenshot from 2019-03-17 17-32-07.png" https://bugs.launchpad.net/gnome-shell/+bug/1721428/+attachment/5247073/+files/Screenshot%20from%202019-03-17%2017-32-07.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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
Re: [Desktop-packages] [Bug 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
thx for reply but It was a message in the bottle because its time that I cannot resolve this prolem I cannot watch to some lessons I need Xubuntu 18.04 ALC662 ASROCK FM2A75M-DGS audio not workingAudio Problem wie folgend › Multimedia › Ubuntu verwenden › Forum › ubuntuusers.deI would appreciate any further help than ubuntu audio troubleshooting | | | | Audio Problem wie folgend › Multimedia › Ubuntu verwenden › Forum › ubun... | | | | | | | Xubuntu 18.04 ALC662 ASROCK FM2A75M-DGS audio not working I cannot hear any sound out of My mb asrock fm2a75m-dgs all sound port look unplugged even if music speaker 2 wa... | | | Il domenica 17 marzo 2019, 11:35:45 CET, Alex Murray ha scritto: Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq: timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock 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: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+subscriptions -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Desktop-packages] [Bug 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1793595 Title: [radeon] Shell freezes, mostly when running chrome or editing text files. Status in gnome-shell package in Ubuntu: Confirmed Bug description: Freezes randomly, mostly when running chrome or editing text files. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 20 16:35:29 2018 DistUpgraded: 2018-08-28 16:25:11,641 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 ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] [1002:682c] (prog-if 00 [VGA controller]) Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e] InstallationDate: Installed on 2018-06-04 (108 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Sep 20 16:27:01 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8 inputDell KB216 Wired Keyboard KEYBOARD, id 9 inputDell KB216 Wired Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
> I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my 144hz display. However, if I disable my second display (it only supports 60hz), I my main gets 144hz as expected. Is that with both dislays attached to an nvidia graphics card ? If so, then what version of the nvidia driver, and linux kernel (dmesg | grep -i nvidia && uname -a). Another interesting thing (for multi-monitor users) is to see if the same thing happens with both of the monitors connected off of the intel integrated graphics (motherboard ports) instead. (Should that be an option, for these testing / debugging purposes). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Status in mutter source package in Disco: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+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 1820514] [NEW] Saving a web page from Tom's Hardware forums fails
Public bug reported: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 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 2018-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1820514 Title: Saving a web page from Tom's Hardware forums fails Status in firefox package in Ubuntu: New Bug description: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 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
[Desktop-packages] [Bug 1820510] Re: Build errors against recent valac
Wrong package, apologies. ** Project changed: unity-api => libunity ** Also affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1820510 Title: Build errors against recent valac Status in libunity: New Status in libunity package in Ubuntu: New Bug description: I'd like to build Geary with support for Unity indicators in the Geary Flatpak package, but it's failing to build against recent valac: mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala --version Vala 0.44.0 mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make make all-recursive make[1]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig' Making all in data make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' ITMRG com.canonical.Unity.Lenses.gschema.xml GEN com.canonical.Unity.Lenses.gschema.valid make[2]: Leaving directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' Making all in protocol make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol' GEN libunity_protocol_private_la_vala.stamp Command-line option `--thread` is deprecated and will be ignored protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is not applicable to constants private static const string SCOPES_DIR = "unity/scopes"; ^^ protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP = "Scope"; ^^^ protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is not applicable to constants private static const string DESKTOP_GROUP = "Desktop Entry"; ^ protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP_GROUP = "Scope Group"; ^ protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_NAME = "com.canonical.Unity.Lens.Music.PreviewPlayer"; protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_PATH = "/com/canonical/Unity/Lens/Music/PreviewPlayer"; protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async ActivationReplyRaw activate ( ^ protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable search ( ^^^ protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters are not supported in async methods out HashTable out_hints, protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async string open_channel ( ^ protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void close_channel ( protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable push_results ( ^ protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void set_view_type (uint view_type) throws IOError; unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' does not exist in the context of `Unity.Protocol.ScopeProxyRemote.open_channel' return channel_id; ^^ Compilation failed: 2 error(s), 12 warning(s) make[2]: *** [Makefile:958: libunity_protocol_private_la_vala.stamp] Error 1 make[2]: Leaving directory
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my 144hz display. However, if I disable my second display (it only supports 60hz), I my main gets 144hz as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Status in mutter source package in Disco: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+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 1820509] [NEW] Avoid use-after-free in _XimProtoSetIMValues()
Public bug reported: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
The above log files were from the Xubuntu system after installing the intel driver. The log file from live iso (using GRML) is now attached. The details are as under:- [58.915] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [58.916] Build Operating System: Linux 4.4.0-142-generic x86_64 Ubuntu [58.916] Current Operating System: Linux xubuntu 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:27:25 UTC 2019 x86_64 [58.916] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed boot=casper iso-scan/filename=/boot/grml/xdisco-desktop-amd64.iso quiet splash --- [58.916] Build Date: 08 March 2019 08:31:56AM [58.916] xorg-server 2:1.20.4-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [58.916] Current version of pixman: 0.36.0 [58.916]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [58.916] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [58.917] (==) Log file: "/home/xubuntu/.local/share/xorg/Xorg.0.log", Time: Sun Mar 17 10:36:27 2019 [58.917] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [58.917] (==) No Layout section. Using the first Screen section. [58.917] (==) No screen section available. Using defaults. [58.917] (**) |-->Screen "Default Screen Section" (0) [58.917] (**) | |-->Monitor "" [58.918] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [58.918] (==) Automatically adding devices [58.918] (==) Automatically enabling devices [58.918] (==) Automatically adding GPU devices [58.918] (==) Automatically binding GPU devices [58.918] (==) Max clients allowed: 256, resource mask: 0x1f [58.918] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [58.918]Entry deleted from font path. [58.918] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [58.918]Entry deleted from font path. [58.918] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [58.918]Entry deleted from font path. [58.918] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [58.918]Entry deleted from font path. [58.918] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [58.918]Entry deleted from font path. [58.918] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [58.918] (==) ModulePath set to "/usr/lib/xorg/modules" [58.918] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [58.918] (II) Loader magic: 0x55652386e020 [58.918] (II) Module ABI versions: [58.918]X.Org ANSI C Emulation: 0.4 [58.918]X.Org Video Driver: 24.0 [58.918]X.Org XInput driver : 24.1 [58.918]X.Org Server Extension : 10.0 [58.919] (++) using VT number 2 [58.922] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31 [58.923] (II) xfree86: Adding drm device (/dev/dri/card0) [58.923] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [58.927] (--) PCI:*(0@0:2:0) 8086:29c2:105b:0ded rev 16, Mem @ 0xfdf0/524288, 0xd000/268435456, 0xfda0/1048576, I/O @ 0xff00/8, BIOS @ 0x/131072 [58.927] (II) LoadModule: "glx" [58.928] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [58.929] (II) Module glx: vendor="X.Org Foundation" [58.929]compiled for 1.20.4, module version = 1.0.0 [58.929]ABI class: X.Org Server Extension, version 10.0 [58.929] (==) Matched intel as autoconfigured driver 0 [58.929] (==) Matched modesetting as autoconfigured driver 1 [58.929] (==) Matched fbdev as autoconfigured driver 2 [58.929] (==) Matched vesa as autoconfigured driver 3 [58.929] (==) Assigned the driver to the xf86ConfigLayout [58.929] (II) LoadModule: "intel" [58.929] (WW) Warning, couldn't open module intel [58.929] (EE) Failed to load module "intel" (module does not exist, 0) [58.929] (II) LoadModule: "modesetting" [58.929] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [58.930] (II) Module modesetting: vendor="X.Org Foundation" [58.930]compiled for 1.20.4, module version = 1.20.4 [58.930]Module class: X.Org Video Driver [58.930]ABI class: X.Org Video Driver, version 24.0 [58.930] (II) LoadModule: "fbdev" [58.930] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [58.930] (II) Module fbdev: vendor="X.Org Foundation" [58.930]compiled for 1.20.1, module version = 0.5.0 [58.930]Module
[Desktop-packages] [Bug 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq:timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock 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: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+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 1767650] Re: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat
This affects HP/Compaq 8510p too. This model too was sold with "3D DriveGuard", and the screen orientation is: flat: nothing changes, keeps whatever is already in use lift the laptop tilt slightly up (screen-mount is higher than mouse-pad: up-side down !! This is very annoying Keyboard all the way up, like a painting, normal orientation: up side down !! Keyboard all the way up, like a painting, upside down: screen turns the normal way. This is how you recover the screen orientation Put laptop on the sides, screens turns as expected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1767650 Title: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: HP Elitebook Folio 9470m. This system is not a tablet or convertible, and does not have a touchscreen. If the laptop is sitting flat during boot, the display orientation is normal. If the laptop is not sitting flat during boot, or if it is moved out of flat, the display rotates and the orientation it rotates to is inverted upside-down. This happens at the login screen as well as after login. This laptop should really never have the screen rotate in the first place, as it's not a tablet or convertible, but in the event that rotation is happening it shouldn't be upside-down. I have locked the rotation in gnome shell and in the login screen using the rotation lock button in the respective system menus. It would be nice if there was a system-wide setting & this didn't need to be done on a per-user basis. This gsettings command will also lock the gnome-shell rotation: gsettings set org.gnome.settings-daemon.peripherals.touchscreen orientation-lock true However the above key doesn't affect the login screen, which has its own separate rotation button in its own version of the system menu. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:17:35 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1767650/+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 1767650] Re: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat
Ubuntu 18.04.2 LTS, x86 (newest version available for this arch) iio-sensor-proxy: 2.4-2 ** Tags added: x86 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1767650 Title: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: HP Elitebook Folio 9470m. This system is not a tablet or convertible, and does not have a touchscreen. If the laptop is sitting flat during boot, the display orientation is normal. If the laptop is not sitting flat during boot, or if it is moved out of flat, the display rotates and the orientation it rotates to is inverted upside-down. This happens at the login screen as well as after login. This laptop should really never have the screen rotate in the first place, as it's not a tablet or convertible, but in the event that rotation is happening it shouldn't be upside-down. I have locked the rotation in gnome shell and in the login screen using the rotation lock button in the respective system menus. It would be nice if there was a system-wide setting & this didn't need to be done on a per-user basis. This gsettings command will also lock the gnome-shell rotation: gsettings set org.gnome.settings-daemon.peripherals.touchscreen orientation-lock true However the above key doesn't affect the login screen, which has its own separate rotation button in its own version of the system menu. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:17:35 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1767650/+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 1726232] Re: Ubuntu 17.10 login screen appearing upside down
Problem continues into 18.04.2 #1767650 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726232 Title: Ubuntu 17.10 login screen appearing upside down Status in iio-sensor-proxy package in Ubuntu: Expired Bug description: Ever since I upgraded my laptop from 17.04 to 17.10, my login screen has been upside down, and I can find no way to correct it. I can successfully login. When I first logged in, my desktop was upside down as well. I was able to correct that by typing "xrandr --output eDP-1-1 --rotate normal" and that setting has stuck, but it has had no effect on my login screen. This laptop does not have an orientation sensor, no screen rotation is intended. This is a MSI GS60 6QE laptop, with a GeForce GTX 970M GPU, nVidia driver 384.90 installed. I apologize if there is a simple setting that I have overlooked, but I scoured Google for hours with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1726232/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I have with the multifunction printer Samsung CLX-3185N and Simple Scan
the following problem:
After starting Simple Scan, I can scan the 1st page; every other page no
longer. Error message: "Scan failed Scan failed to start."
What have I done so far:
Linux unified driver uld_V1.00.39_01.17.tar.gz downloaded from Samsung
through HP website and unpacked in my download directory.
Then the command
sudo ~ / downloads / uld / install.sh
called and installed the driver. There were no error messages.
Since the scanner was not recognized at the beginning, I created the
following links.
sudo ln -sfv /usr/lib/sane/libsane-smfp.so* / usr / lib / x86_64-linux-
gnu / sane
Now the scanner is found with sane-find-scanner and scanimage -L; but
that above Problem occurs now.
I tested the following before calling Simple-Scan:
haraldbraun @ Fulda: ~ $ lsusb | grep -e samsung
Bus 001 Device 005: ID 04e8: 343d Samsung Electronics Co., Ltd
haraldbraun @ Fulda: ~ $ sudo sane-find-scanner
Found USB scanner (vendor = 0x04e8 [Samsung Electronics Co., Ltd.], product =
0x343d [CLX-3180 Series]) at libusb: 001: 005
haraldbraun @ Fulda: ~ $ scanimage -L
device `smfp: usb; 04e8; 343d; Z52IBAIB600104R 'is a Samsung CLX-3180 series on
USB scanner
haraldbraun @ Fulda: ~ $ ls -al / dev / bus / usb / 001/005
crw-rw-r - + 1 root lp 189, 4 Mar 17 08:00 / dev / bus / usb / 001/005
haraldbraun @ Fulda: ~ $ groups
Harald Brown Lp Sudo Backup Lpadmin Scanner Saned Public
haraldbraun @ Fulda: /etc/udev/rules.d$ ls -l
a total of 68
-rwxr-xr -x 1 root root 5666 Mar 16 17:56 39-smfp_samsung.rules
-rw-r - r-- 1 root root 58549 Feb 18 11:28 70-snap.core.rules
In 39-smfp_samsung.rules ist der Multifunktionsdrucker wie folgt
aufgeführt (Datei-Auszug):
# This file is a part of Unified Linux Driver
# Rules to allow low level USB device access for smfpautoconf
#
# For new distributions,
# Permissions and group are set according to common libsane rules
#
ACTION!="add", GOTO="smfp_label_end"
# Check device type
ENV{DEVTYPE}=="usb_device", GOTO="smfp_create_usb_dev"
# Check SUBSYSTEM (should be either "usb" or "usb_device")
SUBSYSTEM=="usb", GOTO="smfp_create_usb_dev"
SUBSYSTEM=="usb_device", GOTO="smfp_create_usb_dev"
GOTO="smfp_label_end"
LABEL="smfp_create_usb_dev"
# Check Vendor ID
ATTR{idVendor}!="04e8", GOTO="smfp_label_end"
ATTRS{idProduct}=="3425", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="341c", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="342a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343d", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3456", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="345a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3427", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3428", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343b", ENV{libsane_matched}="yes"
<==
ATTRS{idProduct}=="3455", ENV{libsane_matched}="yes"
.
.
.
ENV{libsane_matched}=="yes", OWNER="root", MODE="664", GROUP="lp"
LABEL="smfp_label_end"
Then I have the command in the terminal:
sudo tail -f / var / log / syslog
entered, Simple-Scan started.
The first start attempt of Simple-Scan fails.
The second start attempt succeeds; I then did the following activities:
- 1st picture scanned in (successfully)
- scanned the following image (failure, with o.a.
- Simple scan ends without saving
- tail finished.
The syslog excerpt is listed below:
haraldbraun@Fulda:~$ sudo tail -f /var/log/syslog
[sudo] Passwort für haraldbraun:
Mar 17 09:50:17 Fulda kernel: [11120.507310] usb 1-12: new high-speed USB
device number 6 using xhci_hcd
Mar 17 09:50:18 Fulda kernel: [11120.656159] usb 1-12: New USB device found,
idVendor=04e8, idProduct=343d
Mar 17 09:50:18 Fulda kernel: [11120.656165] usb 1-12: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Mar 17 09:50:18 Fulda kernel: [11120.656169] usb 1-12: Product: CLX-3180 Series
Mar 17 09:50:18 Fulda kernel: [11120.656173] usb 1-12: Manufacturer: Samsung
Electronics Co., Ltd.
Mar 17 09:50:18 Fulda kernel: [11120.656176] usb 1-12: SerialNumber:
Z52IBAIB600104R
Mar 17 09:50:18 Fulda kernel: [11120.657637] usblp 1-12:1.1: usblp1: USB
Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04E8 pid 0x343D
Mar 17 09:50:18 Fulda upowerd[1235]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.1
Mar 17 09:50:18 Fulda upowerd[1235]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12
Mar 17 09:50:19 Fulda colord-sane[9174]: io/hpmud/pp.c 627: unable to read
device-id ret=-1
Mar 17 09:50:54 Fulda upowerd[1235]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
Mar 17 09:50:54 Fulda upowerd[1235]: unhandled action 'unbind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
Mar 17 09:50:54 Fulda upowerd[1235]: unhandled action 'unbind' on
[Desktop-packages] [Bug 1820497] [NEW] The "synPS/2 Synaptics TouchPad" is visible xinput, but the touchpad no longer works after booting up my "lenovo ideapad yoga 11s" after not using the laptop for
Public bug reported: My lenovo ideapad yoga 11s touchpad is not working I followed the instuctions on https://wiki.ubuntu.com/DebuggingTouchpadDetection to debug the touchpad to no avail. this is not a major issue as I have a usb mouse I can use, but any fix or information leading the touchpad working again would be appreciated. Anyway, below are copied of the files that were generated from following the debugging instuctions on the site above. _ cat /proc/bus/input/devices _ I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse1 event6 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=101400800100c03 430 0 2 B: MSC=10 I: Bus=0003 Vendor=03eb Product=8814 Version=0111 N: Name="Atmel Atmel maXTouch Digitizer" P: Phys=usb-:00:1a.0-1.4/input0 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:03EB:8814.0003/input/input9 U: Uniq= H: Handlers=mouse2 event8 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=04f2 Product=b35e Version=2607 N: Name="Lenovo EasyCamera" P: Phys=usb-:00:1d.0-1.8/button S: Sysfs=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/input/input11 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=1bcf Product=0007 Version=0110 N: Name="USB Optical Mouse" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:1BCF:0007.0005/input/input15 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=1f B: KEY=7 0 0 0 0 B: REL=143 B: ABS=100 B: MSC=10 _ sudo evtest /dev/input/event6 _ Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1 Input device name: "SynPS/2 Synaptics TouchPad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 328 (BTN_TOOL_QUINTTAP) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event code 335 (BTN_TOOL_QUADTAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 1242 Max 5702 Resolution 51 Event code 1 (ABS_Y) Value 0
[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
The current 'xorg.0.log' as well as the 'xorg.0.log.old' is attached. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1819943/+attachment/5246944/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1819943/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
Wasn't able to attach 'xorg.0.log.old', the same is also attached. ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1819943/+attachment/5246945/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1819943/+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 1820430] Re: failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-amd64.iso
that's weird, the image build should've failed instead like it did for ubuntu anyway, the image should be fine now after this xorg (1:7.7+19ubuntu11) disco; urgency=medium * Drop mesa-vulkan-drivers from xserver-xorg Recommends, until vulkan- loader is in main. -- Timo Aaltonen Sat, 16 Mar 2019 00:16:43 +0200 ** Package changed: xorg (Ubuntu) => xubuntu-meta (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/1820430 Title: failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop- amd64.iso Status in xubuntu-meta package in Ubuntu: New Bug description: install proceeded normally (manual partitioning) on reboot failed to start X session .. rebooted to grub selection screen chose rescue mode .. from the choices menu ran some checks then did updates install .. all of the xorg-server files were installed automaticly .. then selected the "boot resume " (not sure on wording) which then allowed normal login to proceed (lightdm) into xfce/xubuntu evironment.. seems the xorg packages were not installed initially .. this appears to be a recent "change" as earlier images did install these files normally.. early march?, but February and earlier for sure.. this is a older machine lenovo SL500 with Intel GM45 Express Chipset video .. This machine runs dicso fine normally .. has been running disco since first CD install images were available .. daily updates from proposed .. but has only run xorg-server .. not sure if chipset is wayland capable.. Description: Ubuntu Disco Dingo (development branch) Release: 19.04 march 16, 2019 daily iso tested earlier feb 8 and 15 iso's were ok ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Mar 16 17:42:14 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-16 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=119a6b43-9936-4b5d-ab5b-814f531ed9b7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1820430/+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
