[Desktop-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button
I had this problem last year and found a fix by asking here: https://askubuntu.com/questions/1025923/ubuntu-18-04-unity-cant-login- to-my-ubuntu-sso-account-from-unity-control-cen But when I tried logging in on a new installation today, it worked without enabling CSD. Maybe it got fixed? I'm using 18.04.2 now BTW -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1811596 Title: Ubuntu Single Sign-On GUI not showing login button Status in gnome-online-accounts package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Invalid Bug description: System Settings->Online Accounts->Ubuntu Single Sign-On I can enter my email address and password abd select "I have an Ubuntu Single Sign-On account". But there is no "Save" or "Login" or any other button. I can only close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1811596/+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 1780552] Re: PulseAudio not running
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1780552 Title: PulseAudio not running Status in pulseaudio package in Ubuntu: Expired Bug description: Can't turn on the audio in control Panel!! No Sound Symbol indicates in status bar!! Fix the bug soon. i using without sound since may.I am looking for a update to fix.But i Still looking to get any update from your side.I send bug report before a week.No Replays from you. Please replay me soon I'M looking for some to fix the Bug! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 20:49:19 2018 InstallationDate: Installed on 2018-02-11 (146 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PNFDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1780552/+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 1801494] Re: dock missing
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 Version table: *** 0.9.1ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 4) dock is there 5) dock is not there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1820920] Re: bug in intel graphic driver
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1820920 Title: bug in intel graphic driver Status in xorg-server package in Ubuntu: Expired Bug description: bug in intel graphic driver ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 19 16:51:35 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1028:0667] InstallationDate: Installed on 2018-04-22 (331 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 0c45:64ad Microdia Bus 001 Device 003: ID 062a:5918 Creative Labs Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3531 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a38e26f8-92a9-4bbc-8c10-74d0345513b0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00FTTX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/06/2014:svnDellInc.:pnInspiron3531:pvrA01:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA01: dmi.product.family: 00 dmi.product.name: Inspiron 3531 dmi.product.version: A01 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820920/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Yes, and it looks like you need to be a list member first. you could register this list from: https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
So is the next step that I should post this to pulseaudio- disc...@lists.freedesktop.org? Do I need to be a list member to post there? -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1821533] Re: drm fails to accept edid version 2.4
JJJ, that worked, but now my audio does not work, any idea why? -- 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/1821533 Title: drm fails to accept edid version 2.4 Status in linux-hwe package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb install (also 18.10, also 19.04 daily) leads to black screen. Adding "nomodeset" to kernel boot parameter gives 800x600 video only and permits installing OS to disk. Applying updates and hardware enablement packages does not solve problem: the system will still only boot with nomodeset kernel option, and X is limited to using fbdev module at 800x600 resolution. The "modesetting" driver appears to be loaded and then unloaded during X startup. Trying to force intel module from xserver-xorg-video-intel by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not help. The PCI id for the graphics device appears to be 3ea0 and the place where that might be relevant is the i915 module. This problem occurs with every other Linux release I have tried including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest. The one open source OS that I have found where it might be fixed is DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have verified that the patch referenced in that bug report does make DragonFlyBSD boot past the video problem which I think is the same problem I experience with every Linux OS I have tried including Ubuntu. guest@guest-ZenBook-UX431FA:~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev" ii linux-generic-hwe-18.044.18.0.16.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-18.044.18.0.16.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-18.04 4.18.0.16.66 amd64Generic Linux kernel image ii linux-signed-generic-hwe-18.04 4.18.0.16.66 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 amd64X.Org X server -- fbdev display driver Expected result: Video at 1920x1080 Actual result: Video limited to 800x600 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 10:36:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FA 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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A 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 N/A version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Any news here? :( If helps, I've also upgraded from Xenial long time ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 577859] Re: printer disappears
*** This bug is a duplicate of bug 554172 *** https://bugs.launchpad.net/bugs/554172 Unbelievable: After years with Ubuntu-12.04 to 16.04, followed by Linux Mint up to 19.3 (Ubuntu 18.04), I switched to a fresh new install of Lubuntu-19.04 a week ago... and have this strange printer disappear problem for the first time ever! Today is May 18th, 2019 - that is eight years(!!!) after the last entry in this list. How can that be? What's wrong? -- My printing system for the last 12-15 years based on cups with the following setup: * 1 network laser printer * 3 "symbolic" printers which are a copy of the former, to set defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and "labelprinter" (use of manual feed) # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O Besides the different settings in /etc/cups/printers.conf, the DeviceURI is the same for all four while the UUID differs: UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:756313d5-4548-327f-666b-9f2edf2c8942 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:c4abcfb1-c1f2-34fd-4e8f-514209e3e5e9 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print Any help / hint / solution is highly appreciated - TIA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/577859 Title: printer disappears Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups some days ago I've done a fresh install of ubuntu 10.04. It's now the second time that when I try to print a document the printer has disappeared. In the box where one normally selects the printer there's only the option 'Custom...' Workaround: reinstallation of the cups package. After reinstallation the deskjet printer can be selected again. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.3-1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun May 9 16:35:56 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Lpstat: device for Deskjet-6500: hp:/usb/Deskjet_6500?serial=MY47F2P1FH040N MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Deskjet-6500: HP Deskjet 6500 hpijs, 3.10.2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=b80b8efa-19f2-4c3b-b161-caa4fcce9aff ro quiet splash ProcEnviron: LANG=nl_BE.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 11/27/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-X/GBL dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0105:bd11/27/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/GBL:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/577859/+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 1714504] Re: App indicator is not always displayed
Will there be an update for Bionic? My duplicate bug was against Bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Bug description: I've 2 apps that should be displayed in the indicator: - hp systray (from the package hplip-gui) - synology cloud client (download from synology) Sometimes the indicators are displayed and sometimes not. The extension is loaded and show no error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 14:57:16 2017 Dependencies: InstallationDate: Installed on 2013-09-03 (1458 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+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 1829621] [NEW] No sound after suspend
Public bug reported: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: 19.04 suspend-resume -- 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/1829621 Title: No sound after suspend Status in pulseaudio package in Ubuntu: New Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId
[Desktop-packages] [Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Correction: I have to push the Enter key to dismiss the screen, not any other key. -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+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 1829533] Re: Doubled desktop icons
As you will see from the attached screenshot, there are standard folder icons on the left. Those are the duplicates. They do not respond when clicked and cannot be dragged or auto-arranged. The ones that do work mostly have customized folder images. For example, there is: -- a standard folder "Chernobyl" that is a duplicate (doesn't work) -- a customized folder depicting an atom (clicks when opened) After I put the screenshot on the desktop, 2 icons appeared -- an "active" one, plus a duplicate which looks the same but also won't respond when clicked. You attention to this is very appreciated! ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1829533/+attachment/5264683/+files/Screenshot%20from%202019-05-18%2011-03-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1829533 Title: Doubled desktop icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 09:27:05 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 [17aa:21cf] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4243AV5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243AV5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243AV5 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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-extension-desktop-icons/+bug/1829533/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
So, 4 weeks later, after my previous comments, and now running stably: Upgraded to 5.0.0-15 today via command line with 'do-release-upgrade'. The triggers looping error still happens but this gets mopped up by dpkg --configure -a which the upgrade script autoruns for you. The 'system error detected' pop-up was still there but I was able to cure this via: https://gitlab.freedesktop.org/spice/linux/vd_agent/commit/098268a33c7c8008ccec9050aea8f0763f1c06d5 '/var/run' is a symlink but errors still happen; just edit out the '/var' prefix for the PIDfile entry in /lib/systemd/system/spice- vdagent.service. I think this above is connected to the problems with virtual box too. Also edit the files /usr/lib/tmpfiles.d/spice-vdagentd.conf & speech- despatcher.conf while you are there. See 'cat /var/log/syslog' and you will see similar errors main spice one that's detailed. VirtualBox itself upgraded without problem, as I was using the ubuntu packages this time. I just needed to editions, from file > prefs, to get get the machines to load up. Don't think this was of significance, but who knows,so I probably should mention another couple of fixes I did before the upgrade, based on syslog entries: This one here for OID file not found errors: https://askubuntu.com/questions/1102926/colord-errors-in-var-log-syslog- in-18-10 The other was commenting out 'max-height' and 'max-width' from gtk- widgets.css in /usr/share/themes/Ambiant-MATE/gtk-3.0. Annoying error that I have been meaning to sort out for a while now ... I have tested this all day. Run it through its paces. Still a few little grumbles showing in the syslog but nothing serious I tend to think. I am guessing things trying to launch before AppArmor will let them, that's all. Seems good. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version:
[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
FWIW, I ran into this after updating to 19.04 from 18.04. Audio working fine with HDMI (yay) but not with back panel audio (boo) unless I ran aplay as root, e.g. sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav ps showed timidity running. 'sudo apt remove timidity; sudo killall timidity' resolved the problem. -- 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/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1662094] Re: [needs-packaging] mozjs38, Mozilla's SpiderMonkey JavaScript engine
** Package changed: ubuntu => mozjs52 (Ubuntu) ** Changed in: mozjs52 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs52 in Ubuntu. https://bugs.launchpad.net/bugs/1662094 Title: [needs-packaging] mozjs38, Mozilla's SpiderMonkey JavaScript engine Status in mozjs52 package in Ubuntu: Fix Released Bug description: GNOME Shell and several GNOME apps are written in JavaScript and use Mozilla's SpiderMonkey JavaScript engine via gjs. GNOME 3.22 uses mozjs24. It looks like GNOME 3.24 will use mozjs38 (skipping mozjs31). Without this update, we can't update gnome-shell to 3.24. This switch is important because the SpiderMonkey releases correspond with Firefox releases which include security updates. The current mozjs24 corresponds with 24.2 released December 2013. The current Firefox ESR is 45.7 but the latest Spidermonkey release is 45.0.2 from April 2016: https://developer.mozilla.org/en- US/docs/Mozilla/Projects/SpiderMonkey/Releases/45 This will add a 3rd version of mozjs to Ubuntu 17.04 but the goal is to drop mozjs24 in 17.10. The ancient original mozjs package in particular is used by couchdb which has found it difficult to use more recent mozjs versions. $ reverse-depends src:mozjs * couchdb-bin (for libmozjs185-1.0) * gxine (for libmozjs185-1.0) * libproxy1-plugin-mozjs(for libmozjs185-1.0) * oolite(for libmozjs185-1.0) $ reverse-depends src:mozjs24 Reverse-Depends === * cinnamon (for libmozjs-24-0v5) * edbrowse (for libmozjs-24-0v5) * gnome-shell (for libmozjs-24-0v5) * libcjs-dev(for libmozjs-24-dev) * libcjs0 (for libmozjs-24-0v5) * libgjs-dev(for libmozjs-24-dev) * libgjs0e (for libmozjs-24-0v5) $ reverse-depends src:gjs Reverse-Recommends == * python-pocket-lint(for gjs) Reverse-Depends === * gnome-characters (for gjs) * gnome-documents (for gjs) * gnome-maps(for gjs) * gnome-shell (for libgjs0e) * gnome-shell (for gjs) * gnome-sound-recorder (for gjs) * gnome-sushi (for libgjs0e) * gnome-weather (for gjs) * ostree-tests (for gjs) * polari(for gjs) * ubuntu-budgie-desktop (for gjs) * ubuntu-gnome-desktop (for gjs) * unity-webapps-dev (for gjs) mozjs38 will be maintained in Debian possibly by the mozjs24 maintainer once GNOME 3.24 is packaged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs52/+bug/1662094/+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 1662094] [NEW] [needs-packaging] mozjs38, Mozilla's SpiderMonkey JavaScript engine
You have been subscribed to a public bug: GNOME Shell and several GNOME apps are written in JavaScript and use Mozilla's SpiderMonkey JavaScript engine via gjs. GNOME 3.22 uses mozjs24. It looks like GNOME 3.24 will use mozjs38 (skipping mozjs31). Without this update, we can't update gnome-shell to 3.24. This switch is important because the SpiderMonkey releases correspond with Firefox releases which include security updates. The current mozjs24 corresponds with 24.2 released December 2013. The current Firefox ESR is 45.7 but the latest Spidermonkey release is 45.0.2 from April 2016: https://developer.mozilla.org/en- US/docs/Mozilla/Projects/SpiderMonkey/Releases/45 This will add a 3rd version of mozjs to Ubuntu 17.04 but the goal is to drop mozjs24 in 17.10. The ancient original mozjs package in particular is used by couchdb which has found it difficult to use more recent mozjs versions. $ reverse-depends src:mozjs * couchdb-bin (for libmozjs185-1.0) * gxine (for libmozjs185-1.0) * libproxy1-plugin-mozjs(for libmozjs185-1.0) * oolite(for libmozjs185-1.0) $ reverse-depends src:mozjs24 Reverse-Depends === * cinnamon (for libmozjs-24-0v5) * edbrowse (for libmozjs-24-0v5) * gnome-shell (for libmozjs-24-0v5) * libcjs-dev(for libmozjs-24-dev) * libcjs0 (for libmozjs-24-0v5) * libgjs-dev(for libmozjs-24-dev) * libgjs0e (for libmozjs-24-0v5) $ reverse-depends src:gjs Reverse-Recommends == * python-pocket-lint(for gjs) Reverse-Depends === * gnome-characters (for gjs) * gnome-documents (for gjs) * gnome-maps(for gjs) * gnome-shell (for libgjs0e) * gnome-shell (for gjs) * gnome-sound-recorder (for gjs) * gnome-sushi (for libgjs0e) * gnome-weather (for gjs) * ostree-tests (for gjs) * polari(for gjs) * ubuntu-budgie-desktop (for gjs) * ubuntu-gnome-desktop (for gjs) * unity-webapps-dev (for gjs) mozjs38 will be maintained in Debian possibly by the mozjs24 maintainer once GNOME 3.24 is packaged. ** Affects: mozjs52 (Ubuntu) Importance: Wishlist Status: Fix Released ** Tags: needs-packaging upgrade-software-version -- [needs-packaging] mozjs38, Mozilla's SpiderMonkey JavaScript engine https://bugs.launchpad.net/bugs/1662094 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs52 in Ubuntu. -- 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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Reproducing screenshot of the reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264682/+files/2019-05-18%2022-22-44%20%E7%9A%84%E8%9E%A2%E5%B9%95%E6%93%B7%E5%9C%96.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
Note that regular video clips downloaded from Youtube also reproduce this bug: https://www.youtube.com/watch?v=feOq6MWeUXA -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Mediainfo output of the reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264681/+files/simplescreenrecorder-2019-05-18_21.41.21.mkv.mediainfo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264680/+files/simplescreenrecorder-2019-05-18_21.41.21.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] [NEW] Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
Public bug reported: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1808874] Re: nvidia-detector doesn't seem to detect nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1808874 Title: nvidia-detector doesn't seem to detect nvidia Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: bdmurray@flash:~$ grep nvidia /proc/modules nvidia_uvm 757760 0 - Live 0x (POE) nvidia_drm 40960 1 - Live 0x (POE) nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE) nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE) drm_kms_helper 172032 1 nvidia_drm, Live 0x drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x bdmurray@flash:~$ nvidia-detector none bdmurray@flash:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1808874/+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 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Here is the screen capture with the background settings. ** Attachment added: "Screen Capture.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+attachment/5264674/+files/Screen%20Capture.png -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+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 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled
Sorry, but I am not sure I could tell the difference so I will try and describe it as best I can. There is no place to enter a password, but I also have my system set to automatically log in, so I'm not sure if it would ask me for a password if it was displayed. I do have to press a key to get past the screen. I have attached a picture of the screen. I was not able to do a screen capture as it would not let me with the screen displayed, so I used my phone's camera. I will also attached a screen capture showing my settings for choice of background and lock screen in the next comment as I can only attach one file per comment. Hopefully this will clarify things. ** Attachment added: "Lock Screen.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+attachment/5264673/+files/Lock%20Screen.jpg -- 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/1827751 Title: Lock screen displayed after screen blanking even when lock screen disabled Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+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 1812392] Re: Hplip does not recognize HP color laserjet PRO MFP m181fw
Ubuntu 18.04.2 LTS with kernel 4.18.0-20-generic all up to date @18/5/2019 HP color laserjet PRO MFP m181fw is now getting recognized after 'adding printer' in the systemsettings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1812392 Title: Hplip does not recognize HP color laserjet PRO MFP m181fw Status in hplip package in Ubuntu: New Bug description: Ubuntu 18.04.1 LTS all up to date to latest @ 18/1/2018 Hplip 3.17.10+repack0-5 from default 18.04 does not recognize my Hp laserprinter i had to install HPLIP 3.18.12 manually to get it working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 [modified: usr/lib/cups/filter/hpps usr/lib/cups/filter/pstotiff] ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: W [18/Jan/2019:06:15:55 +0100] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Er is al een object geëxporteerd voor de interface org.freedesktop.ColorManager.Profile op /org/freedesktop/ColorManager/profiles/HP_ColorLaserJet_MFP_M178_M181_Gray__ W [18/Jan/2019:06:15:55 +0100] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Er is al een object geëxporteerd voor de interface org.freedesktop.ColorManager.Profile op /org/freedesktop/ColorManager/profiles/HP_ColorLaserJet_MFP_M178_M181_RGB__ W [18/Jan/2019:06:15:55 +0100] CreateDevice failed: org.freedesktop.ColorManager.Device.Internal:failed to register object: Er is al een object geëxporteerd voor de interface org.freedesktop.ColorManager.Device op /org/freedesktop/ColorManager/devices/cups_HP_ColorLaserJet_MFP_M178_M181 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:06:32 2019 InstallationDate: Installed on 2018-07-15 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-ColorLaserJet-MFP-M178-M181: usb://HP/ColorLaserJet%20MFP%20M178-M181?serial=VNC3P35598 device for HP_ColorLaserJet_MFP_M178-M181: hp:/usb/HP_ColorLaserJet_MFP_M178-M181?serial=VNC3P35598 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i7BNH Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-ColorLaserJet-MFP-M178-M181.ppd', '/etc/cups/ppd/HP_ColorLaserJet_MFP_M178-M181.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-ColorLaserJet-MFP-M178-M181.ppd: Permission denied grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M178-M181.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=228e3cdd-cf57-4070-a5f3-e3201fbc403f ro SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0067.2018.0814.1500 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-310 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0067.2018.0814.1500:bd08/14/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-311:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-310:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-311 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1812392/+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 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
Workaround in #19 working for me so far on Ubuntu 19.04. Have done a reboot test and a powerup test so far. Something I noticed earlier when the machine was stuck is that the machine was able to get to the point where I could ssh to it after the GUI hadn't started. The command below did bring up the GUI for me: $ sudo systemctl restart gdm3 or even $ /etc/init.d/gdm3 restart Not a better workaround, but may save from rebooting while you make the change for #19. $ cat /etc/issue.net Ubuntu 19.04 $ uname -a Linux ubuntu-am 5.0.0-15-generic #16-Ubuntu SMP Mon May 6 17:41:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Here is my syslog, I do notice some activity from 'meta_kms_resources_init', mentioned in #19, in there.. Thanks for all you do! ** Attachment added: "syslog.1 from gdm3 crashing machine" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5264671/+files/syslog_ubuntu1904.txt -- 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/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in mutter source package in Eoan: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/483 formerly https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+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 1829605] [NEW] Asus N53SV laptop's Internal bluetooth is not working
Public bug reported: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1829605 Title: Asus N53SV laptop's Internal bluetooth is not working Status in gnome-bluetooth package in Ubuntu: New Bug description: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1829605/+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 1828649] Re: Wayland session freezes
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1828649 Title: Wayland session freezes Status in gnome-shell package in Ubuntu: New Bug description: When I switch to wayland the gnome desktop locks up before I see my desktop. It doesn't lock up when I have my laptop closed and only one display connected. When I connect up the second display, it locks up every time. I tried deleting my monitors.xml file.. that doesn't make any difference. I was able to get it to work by connecting one display via DisplayPort. When I connect the second display, via active HDMI to DisplayPort on dock, it doesn't work if I select Wayland. This wire configuration works fine with Xorg. Additionally, when I lift my laptop screen, one of my monitors goes out and re-enabling it causes another to go off. Linux kernel is not smart enough to drive the 3 displays. I am able to drive two monitors and have my laptop screen open in Windows just fine. Of importance is that my DisplayPort to HDMI adaptor is ACTIVE. If I was to use a PASSIVE adaptor, I cannot drive two external displays and the laptop display. With my laptop screen closed, I was able to drive both displays in Wayland just fine in 18.10 so this is a regression. The GNU/Linux kernel has always (as far as I know) been lacking in smarts to drive all three displays. This work system is has Intel 4000 Integrated video (Lenovo ThinkPad laptop). Main screen is 2560x1600 via DisplayPort to laptop. Secondary screen is 1920x1200 via DisplayPort to laptop dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 10 16:55:27 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2019-03-25 (46 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.sku: LENOVO_MT_3435 dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1828649/+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 1829533] Re: Doubled desktop icons
Thank you for your bug report, could you make a screenshot showing the issue? ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1829533 Title: Doubled desktop icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 09:27:05 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 [17aa:21cf] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4243AV5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243AV5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243AV5 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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-extension-desktop-icons/+bug/1829533/+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 1389336] Re: Use geoclue-2.0
geoclue and ubuntu-geoip are being removed in eoan now ** Changed in: ubuntu-geoip (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Won't Fix Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in ubuntu-geoip package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1829599] [NEW] Does not report error about setting an unsupported resample method
Public bug reported: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method=soxr- hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1829599 Title: Does not report error about setting an unsupported resample method Status in pulseaudio package in Ubuntu: New Bug description: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method =soxr-hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829599/+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 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle Status in gnome-terminal package in Ubuntu: Confirmed Bug description: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+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
