[Desktop-packages] [Bug 1794283] Re: nautilus throws error during copying file
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1794283 Title: nautilus throws error during copying file Status in nautilus package in Ubuntu: Expired Bug description: When copying a file from a remote samba resource I get an error "Error when copying ", more information: "Error during file splitting: input/output error". The problem occurs only in the Nautilus file manager, copying by the terminal or by another file manager works properly without error. I use Ubuntu 18, packages associated with nautilus: libnautilus-extension1a:amd64 1:3.26.3-0ubuntu4 nautilus 1:3.26.3-0ubuntu4 amd64 nautilus-data 1:3.26.3-0ubuntu4 all nautilus-extension-gnome-terminal 3.28.2-1ubuntu1~18.04.1 amd64 nautilus-sendto 3.8.6-2 amd64 nautilus-share 0.7.3-2ubuntu3 amd64 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 13:22:22 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'203' b'org.gnome.nautilus.window-state' b'geometry' b"'864x501+2419+288'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-09-03 (21 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794283/+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 1821169] Re: Jumpy touchpad input on Dell XPS 9370 when upgrading to 19.04 from 18.04
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1821169 Title: Jumpy touchpad input on Dell XPS 9370 when upgrading to 19.04 from 18.04 Status in libinput package in Ubuntu: Expired Bug description: Quite hard to get meaningful errors / logs, but I'll try to explain the best I can. I'm running on a Dell XPS 9370 (the developer edition). I was running 18.04 on Wayland and have updated to 19.04 using the `do-release-upgrade` executable to 18.10 and then `do-release-upgrade -d`. Still running on Wayland (although, as far as I can see, the issue is also on X), the pointer / touchpad has become very jumpy and has an odd acceleration profile. I had set the acceleration profile to "FLAT" on 18.04 and have tried to re-set that, but it doesn't seem to have changed anything. When I move long distances, the pointer seems to suddenly x2 in speed (rather than linear acceleration that I'd be used to), making it difficult to accurately point. The worst experience seems to be small adjustments, for example highlighting text. The cursor feels like it randomly jumps, some time it's fine, sometimes it jumps quite significant screen distance for a tiny movement of my finger and other times it is fine. I'm more than happy to provide logs, videos etc. Thanks all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1821169/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
shut down windos and rebooted Ubuntu. No Sound As SU ran echo 1 > parameters/dump_coef Speaker sound works for about 10 seconds. The following is the report from alsa-info !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Tue May 21 03:41:46 UTC 2019 !!Linux Distribution !!-- Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 19.04" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=disco !!DMI Information !!--- Manufacturer: ASUSTeK COMPUTER INC. Product Name: GL703VD Product Version: 1.0 Firmware Version: GL703VD.308 Board Vendor: ASUSTeK COMPUTER INC. Board Name:GL703VD !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/ATK4002:00/status 15 /sys/bus/acpi/devices/ELAN1200:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT33D0:00/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXPOWER:14/status 1 /sys/bus/acpi/devices/LNXPOWER:15/status 1 /sys/bus/acpi/devices/LNXPOWER:16/status 1 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C02:06/status 15 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:01/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0E:00/status 11 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:69/status 15 /sys/bus/acpi/devices/device:79/status 11 !!Kernel Information !!-- Kernel release:5.0.0-15-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.0.0-15-generic Library version:1.1.8 Utilities version: 1.1.8 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf42 irq 133 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) Subsystem: 1043:1bc0 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m:
[Desktop-packages] [Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
After the sound quit I ran Alsa-info and got the following: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Tue May 21 03:48:17 UTC 2019 !!Linux Distribution !!-- Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 19.04" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=disco !!DMI Information !!--- Manufacturer: ASUSTeK COMPUTER INC. Product Name: GL703VD Product Version: 1.0 Firmware Version: GL703VD.308 Board Vendor: ASUSTeK COMPUTER INC. Board Name:GL703VD !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/ATK4002:00/status 15 /sys/bus/acpi/devices/ELAN1200:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT33D0:00/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXPOWER:14/status 1 /sys/bus/acpi/devices/LNXPOWER:15/status 1 /sys/bus/acpi/devices/LNXPOWER:16/status 1 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C02:06/status 15 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:01/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0E:00/status 11 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:69/status 15 /sys/bus/acpi/devices/device:79/status 11 !!Kernel Information !!-- Kernel release:5.0.0-15-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.0.0-15-generic Library version:1.1.8 Utilities version: 1.1.8 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf42 irq 133 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) Subsystem: 1043:1bc0 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2
[Desktop-packages] [Bug 1829651] Re: Caps Lock indicator on screen
** Changed in: gnome-shell (Ubuntu) Importance: Low => Wishlist -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
In theory, adding model=auto (comment #3) doesn't affect your sound driver since even without model=auto, the audio driver doesn't apply any fixup models to your machine. Please do a test: cd /sys/module/snd_hda_codec sudo su echo 1 > parameters/dump_coef Then test your speaker, when the speaker can output sound, please run alsa-info.sh and upload the log After the speaker can't output sound anymore, please run alsa-info.sh again, and upload the log. -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
Update: The patches have been merged to drm-tip: https://cgit.freedesktop.org/drm- tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Confirmed Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 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 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+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 1829801] Re: problem with login to user account. Keeps going back to login window
Please be sure to only report one problem per bug. We will make this bug about the first problem you report only. ** Summary changed: - misc. problems + problem with login to user account. Keeps going back to login window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: [amdgpu] Problem with login to user account. Keeps going back to login window Status in Ubuntu: Incomplete Bug description: a) problem with login to user account. Keeps going back to login window b) screen freeze after suspension. amdgup needs update 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 16:20:30 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-05-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=c4e1f2e7-71de-4e41-a62f-dd9e5e3a5f98 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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/+bug/1829801/+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 1829806] Re: I don't Know
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829806 Title: I don't Know Status in Ubuntu: Incomplete Bug description: Don't have details about the issue! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon May 20 22:03:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (54 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.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: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1829806/+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 1829801] Re: problem with login to user account. Keeps going back to login window
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: amdgpu ** Summary changed: - problem with login to user account. Keeps going back to login window + [amdgpu] Problem with login to user account. Keeps going back to login window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: [amdgpu] Problem with login to user account. Keeps going back to login window Status in Ubuntu: Incomplete Bug description: a) problem with login to user account. Keeps going back to login window b) screen freeze after suspension. amdgup needs update 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 16:20:30 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-05-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=c4e1f2e7-71de-4e41-a62f-dd9e5e3a5f98 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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/+bug/1829801/+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 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Yes those messages themselves are safe, but I think they may suggest the kernel got stuck for a while (somewhere, anywhere). And that would correlate with this bug. If there were any other kernel log messages around that time then please paste them here. -- 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/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" -
[Desktop-packages] [Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
Thanks, but we will need more data points. We need to know at least one kernel version which does not have the bug (if a version exists). And then we need to know the earliest version where the bug was introduced. -- 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: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete 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 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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
I can't see any reason for the dock going permanently missing in that log. It might be a good idea if anyone experiencing this problem opens a new bug with all the required attachments, by running: ubuntu-bug gnome-shell which will do it automatically. -- 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: Incomplete 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 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Someone probably needs to find a relevant upstream Xorg bug link to see where/if it is being discussed there. This is not the place where Xorg developers discuss such things. -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 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-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Tags added: disco eoan -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
Another reboot from Ubuntu back to Ubuntu and the Headset is still silent, BUT now the speaker sound works. Connecting and disconnecting the headset now has no effect on speaker sound except to mute when the headset is plugged in. I apologize for scattershot troubleshooting. -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
Correction. The sound through the speakers only lasts for about 10 seconds. When I plug the headset in there still no sound in the headset, but when I unplug the headset the sound through the speakers resumes but then quits after about 10 seconds. -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
In accordance with this: https://docs.slackware.com/howtos:hardware :audio_and_snd-hda-intel#how_to_find_the_right_options I ran this: sudo echo "options snd-hda-intel model=auto" > /etc/modprobe.d/snd-hda-intel.conf and rebooted. That resulted in both the speakers and headphones working. But in gnome-control-center the sound test gave no sound on either. I have a dual boot system with windows 10 and I heard that there may be issues when quitting windows and loading Ubuntu. So I rebooted into windows and then rebooted back into Ubuntu. The speakers still worked, but the headset no longer works. I then rebooted ubuntu again with no change. Speakers work headset doesn't and the gnome-control-center doesn't' make any sound on either. -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1829806] [NEW] I don't Know
Public bug reported: Don't have details about the issue! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon May 20 22:03:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (54 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.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: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829806 Title: I don't Know Status in xorg package in Ubuntu: New Bug description: Don't have details about the issue! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon May 20 22:03:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (54 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.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: 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
[Desktop-packages] [Bug 1829801] [NEW] misc. problems
Public bug reported: a) problem with login to user account. Keeps going back to login window b) screen freeze after suspension. amdgup needs update 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 16:20:30 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-05-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=c4e1f2e7-71de-4e41-a62f-dd9e5e3a5f98 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: misc. problems Status in xorg package in Ubuntu: New Bug description: a) problem with login to user account. Keeps going back to login window b) screen freeze after suspension. amdgup needs update 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 16:20:30 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-05-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=c4e1f2e7-71de-4e41-a62f-dd9e5e3a5f98 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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
[Desktop-packages] [Bug 1801757] Re: all app indicators disappear
Same here in Ubuntu 18.04. Monitor manager and other gnome extensions are disappearing from the top panel. Alt-F2 r, like other said, helps to get them back. Extensions are still running though when the bug appears. I noticed this behavior some time ago, maybe 3-4 months ago, after an upgrade but yet it is regular. When I lock/unlock the screen the bug happens but maybe in other situations too. -- 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/1801757 Title: all app indicators disappear Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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-extension-appindicator/+bug/1801757/+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 1829655] Re: web pages are not loading and showing up with error "server not found" when connected to wifi
Hello, it looked like you had some problems connecting to wifi -- and perhaps other hardware problems as well. I hope this helps: [ 2164.414923] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2164.541523] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2164.546685] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2164.549965] wlp1s0: authenticated [ 2164.556084] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2164.560253] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2164.562377] wlp1s0: associated [ 2297.562542] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 2297.562554] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 2297.562564] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 2297.562572] pcieport :00:1c.0:[ 0] Receiver Error (First) [ 2379.359481] ACPI Error: Cannot release Mutex [PATM], not acquired (20180531/exmutex-359) [ 2379.359506] No Local Variables are initialized for Method [_Q66] [ 2379.359511] No Arguments are initialized for method [_Q66] [ 2379.359516] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_AML_MUTEX_NOT_ACQUIRED (20180531/psparse-516) [ 2479.371981] wlp1s0: deauthenticating from 5c:99:60:97:1a:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2479.507812] wlp1s0: authenticate with 26:0d:65:1e:76:1d [ 2479.512234] wlp1s0: send auth to 26:0d:65:1e:76:1d (try 1/3) [ 2479.517885] wlp1s0: authenticated [ 2479.520215] wlp1s0: associate with 26:0d:65:1e:76:1d (try 1/3) [ 2479.533060] wlp1s0: RX AssocResp from 26:0d:65:1e:76:1d (capab=0x431 status=0 aid=1) [ 2479.536553] wlp1s0: associated [ 2522.681743] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2522.809107] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2522.813864] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2522.817755] wlp1s0: authenticated [ 2522.820144] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2522.824192] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2522.826018] wlp1s0: associated [ 2717.880069] wlp1s0: deauthenticating from 5c:99:60:97:1a:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2717.908924] wlp1s0: authenticate with 26:0d:65:1e:76:1d [ 2717.912723] wlp1s0: send auth to 26:0d:65:1e:76:1d (try 1/3) [ 2717.916517] wlp1s0: authenticated [ 2717.920089] wlp1s0: associate with 26:0d:65:1e:76:1d (try 1/3) [ 2717.926439] wlp1s0: RX AssocResp from 26:0d:65:1e:76:1d (capab=0x431 status=0 aid=1) [ 2717.931564] wlp1s0: associated [ 2767.989594] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2772.205542] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2772.209731] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2772.220085] wlp1s0: authenticated [ 2772.224303] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2772.228441] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2772.230047] wlp1s0: associated [ 2875.097215] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 2875.097226] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 2875.097237] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 2875.097244] pcieport :00:1c.0:[ 0] Receiver Error (First) Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1829655 Title: web pages are not loading and showing up with error "server not found" when connected to wifi Status in firefox package in Ubuntu: New Bug description: web pages not responding even when wifi is connected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 66.0.5+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s481 1362 F pulseaudio BuildID: 20190508084343 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 19 23:23:36 2019 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-05-19 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.43.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0
[Desktop-packages] [Bug 1829655] Re: web pages are not loading and showing up with error "server not found" when connected to wifi
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1829655 Title: web pages are not loading and showing up with error "server not found" when connected to wifi Status in firefox package in Ubuntu: New Bug description: web pages not responding even when wifi is connected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 66.0.5+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s481 1362 F pulseaudio BuildID: 20190508084343 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 19 23:23:36 2019 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-05-19 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.43.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.43.0/24 dev wlp1s0 proto kernel scope link src 192.168.43.90 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.5/20190508084343 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 05269N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd01/17/2019:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn05269N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1829655/+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 1829650] Re: OpenGl
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829650 Title: OpenGl Status in xorg package in Ubuntu: New Bug description: So I was messing around in the Libre Office settings and enabled Open GL (Hoping for GL acceleration) . Once I restarted Libre office, It would load, but a window would appear briefly and close. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 19 12:40:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu 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:21f3] MachineType: LENOVO 2349IP5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=66ca1202-c6da-48c1-be0e-f4b431fb8924 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349IP5 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET91WW(2.51):bd01/09/2013:svnLENOVO:pn2349IP5:pvrThinkPadT430:rvnLENOVO:rn2349IP5:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349IP5 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun May 19 02:45:50 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829650/+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 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
** Changed in: mesa Status: Unknown => New -- 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/1753677 Title: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display Status in Mesa: New Status in mesa-demos package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: es2gears_wayland sticks to 119 FPS on a 59.95Hz display $ es2gears_wayland EGL_VERSION = 1.4 (DRI2) vertex shader info: fragment shader info: info: 597 frames in 5.0 seconds = 119.138 FPS 600 frames in 5.0 seconds = 119.880 FPS 598 frames in 5.0 seconds = 119.481 FPS 600 frames in 5.0 seconds = 119.952 FPS 600 frames in 5.0 seconds = 119.880 FPS 600 frames in 5.0 seconds = 119.880 FPS 596 frames in 5.0 seconds = 119.105 FPS $ es2gears_x11 EGL_VERSION = 1.4 (DRI2) vertex shader info: fragment shader info: info: 315 frames in 5.0 seconds = 62.837 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 301 frames in 5.0 seconds = 60.008 FPS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-utils-extra 8.4.0-1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Mar 6 16:39:18 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller [8086:041a] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller [17aa:30a1] InstallationDate: Installed on 2017-12-12 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=f9fe7460-9c41-4d4a-8376-e5ceb57bbec8 ro quiet splash vt.handoff=1 SourcePackage: mesa-demos UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1753677/+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 1829785] Re: Evince: ∞ not found
** Changed in: evince Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in Evince: Fix Released Status in evince package in Ubuntu: Triaged Bug description: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+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 1322784] Re: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug
** Changed in: gcc-4.8 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1322784 Title: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in gcc-4.8 package in Ubuntu: Invalid Bug description: The most common Firefox crash on Linux in Mozilla's crash-stats system is crashes in the function flag_qsort. These crashes occur: * only on x86 architecture * only on Ubuntu packages (and not on Mozilla's builds) * on precise and saucy and trusty (based on kernel versions reported with the crashes) and appear to be due to a compiler bug in the compiler used to generate Ubuntu's builds. (It could be a common compiler bug triggered by different compiler options or a compiler bug specific to Ubuntu's gcc.) The analysis that leads to the conclusion that this is a compiler bug is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 . In particular, the compiler is miscompiling an access to an element of an array of unsigned short as a 32-bit read, and when the unsigned short in question is the last one in the allocation and that allocation is aligned so that the byte following has a different 0x10 bit, this can lead to crashes. The most recent (whenever you follow the link) 7 days of crash reports are available at: https://crash- stats.mozilla.com/report/list?signature=flag_qsort=Firefox_type=contains_unit=weeks To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1322784/+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 568272] Re: unclear string for translators: country
Bug report refers to the bbc plug-in which no longer exists Closing as report is no longer valid ** Changed in: totem (Ubuntu) Status: Triaged => Invalid -- 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/568272 Title: unclear string for translators: country Status in totem package in Ubuntu: Invalid Bug description: Binary package hint: totem Country, found here: Located in ../src/plugins/bbc/genres.py:98 Judging from the strings around it I think this refers to the music style. It would help translators if a comment was added that indicated that this is indeed about the music style. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/568272/+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 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
In comment 28, the freeze happened just before taking the log, yet the last log entry was from ~1 minute earlier, so it doesn't look like there were any relevant log entries. However just now I had a freeze, and there are some messages in dmesg: [10980.231902] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [11986.082217] perf: interrupt took too long (3142 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 [16384.901113] perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 Also in journalctl -b0: May 20 22:30:09 daniel-XPS-13-9380 kernel: perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 The previous journalctl message is from a few minutes prior. Searching for the error message suggests that perhaps these messages aren't any major cause for concern though. -- 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/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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:
[Desktop-packages] [Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
It's committed in the disco packaging repository, but not uploaded. I planned on bundling that change with other changes in an SRU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+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 1829785] Re: Evince: ∞ not found
Sebastien, though the Russians the same symbol in mathematics for the infinity, the infinity symbol ∞ itself is not Cyrillic. Have you tested their solution, whatever it may be, simply to make sure that that's the same issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+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
OK, I've attached the requested info from my system. It goes back 4 days, so it should include the period when it stopped working. Unfortunately I can't tell you exactly when that was - having the dock autohide means it's pretty much hidden until I need it. ** Attachment added: "currentjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+attachment/5265130/+files/currentjournal.txt -- 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: Incomplete 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 977228] Re: gnome-screenshot forgets "last-save-directory"
also on 18.04.02 LTS, also other people mentioned in comments https://askubuntu.com/questions/114429/default-save-directory-for-gnome- screenshot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/977228 Title: gnome-screenshot forgets "last-save-directory" Status in Gnome Screenshot: Won't Fix Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: Ubuntu 12.04, Beta 2 1) press [PrintScreen] to do a screenshot 2) gnome-screenshot proposes to save it in "$HOME/pictures" 3) change location to "$HOME/videos" or similiar and close gnome-screenshot 4) press [PrintScreen] again and take another screenshot 6) tool wants to save picture in "$HOME/pictures" again 5) expected behaviour: proposes to save pic in "$HOME/videos" BTW: Setting a fixed path in dconf-editor entry "last-save-directory" doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.4.0-0ubuntu1 Uname: Linux 3.3.1-030301-generic i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Mon Apr 9 15:37:26 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2011-11-24 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/977228/+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 1829651] Re: Caps Lock indicator on screen
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps Lock indicator also should be "on screen" looks like other indicators. not on top bar or anywhere else. for example when Caps Lock is on bright white A logo in the box, and when Caps Lock is off gray crossed A looks like the volume mute indicator in the box. you can add settings like to do it permanent on screen when Caps Lock is ON and temporary when it is OFF or both can be visible permanent on screen. those can be optional in my suggestion. as a suggestion maybe you can put Num Lock and Scroll Lock indicators as well. thank you all in advance for your hard works and contributions to make Ubuntu the best. ** Attachment added: "Volume mute indicator" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265129/+files/Screenshot%20from%202019-05-20%2023-32-51.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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1829651] Re: Caps Lock indicator on screen
Hi. i am expecting a Caps Lock indicator by default (without need of usage any 3rd party app which are not working proper tested few) like the screenshot of Volume indicator as an example i attached. thanks. ** Attachment added: "example - Volume indicator on screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265128/+files/Screenshot%20from%202019-05-20%2023-32-46.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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1829699] Re: Switches are gone from the VPN menu
Could you add your journalctl log to the bug? 3.32.1 is also in disco-proposed so it would be good to also test if the problem exist there/is really with gnome-shell ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1829699 Title: Switches are gone from the VPN menu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu Desktop Eoan up to date There is no more switch in the system menu for the VPN entries. Although the VPN can still be turned on/off by clicking on the menu entry (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 20 06:48:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1769 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (421 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829699/+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 1829785] Re: Evince: ∞ not found
The issue has been reported upstream in https://gitlab.gnome.org/GNOME/evince/issues/1116 ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1116 https://gitlab.gnome.org/GNOME/evince/issues/1116 ** Changed in: evince (Ubuntu) Status: New => Triaged ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1116 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+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 1829651] Re: Caps Lock indicator on screen
Could you give details on what sort of indicator you expect? One in the top panel? One in password/text widgets? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1731417] Re: Installed network printer removed automatically when turned off
This bug was fixed in the package cups-filters - 1.23.0-1 --- cups-filters (1.23.0-1) experimental; urgency=medium * New upstream version 1.23.0 - cups-browsed: When removing a local queue on shutdown or when DNS-SD reports the printer as disappeared check whether the local queue got overwritten by an external process as sometimes the shutdown or disappearing event comes too close for cups-browsed receiving a printer-modified notification from CUPS before (LP: #1731417) -- Didier Raboud Fri, 17 May 2019 10:01:20 +0200 ** Changed in: cups-filters (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Fix Released Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+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
it expired because no-one added the info requested in comment #18 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete -- 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: Incomplete 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 1822403] Re: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed.
Closing then, it would be interesting to know if that can be trigger again with some config (and which one) or if that was some sort of corruption ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1822403 Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. Status in ibus-libpinyin package in Ubuntu: Invalid Bug description: Every time I use Win key + space to switch input methods, I will see the crash on my system. I am currently on Ubuntu 19.04 (Beta) and it was working fine on Ubuntu 18.10 which was the system I have upgraded from. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: ibus-libpinyin 1.11.0-1 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 AssertionMessage: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 19:59:24 2019 ExecutablePath: /usr/lib/ibus/ibus-engine-libpinyin InstallationDate: Installed on 2018-10-16 (165 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/ibus/ibus-engine-libpinyin --ibus Signal: 6 SourcePackage: ibus-libpinyin StacktraceTop: __assert_fail_base (fmt=0x7f3b02880588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=0x7f3b02c6d720 "bool pinyin::copy_bdb(DB*, DB*)") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 pinyin_init () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 ?? () Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. UpgradeStatus: Upgraded to disco on 2019-03-23 (6 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1822403/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: New Status in network-manager source package in Bionic: New Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1768166] Re: Random crashes
** Description changed:
+ [Impact]
+
+ ibus-libpinyin has proved to crash far too often. One or more files in
+ ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
+ directory allows the user to keep using ibus-libpinyin.
+
+ In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
+ present, and the number of crashes has been reduced significantly:
+
+ https://errors.ubuntu.com/?package=ibus-libpinyin=month
+
+ Upstream ChangeLog ibus-libpinyin:
+ --
+ version 1.11.0
+ * fixes keypad decimal
+ * fixes emoji candidates
+ * support configurable opencc config
+
+ version 1.10.92
+ * fixes Enter handling
+
+ version 1.10.91
+ * support ime.register_trigger in lua extension
+ * support predicted candidates
+ * support emoji input
+
+ version 1.10.0
+ * bug fixes
+
+ version 1.9.91
+ * migrate to use GSettings
+ * fixes lyx short cut issue
+
+ version 1.9.3
+ * translate input method name in ibus menu
+
+ Upstream ChangeLog libpinyin:
+ -
+ version 2.2.2
+ * minor fixes
+
+ version 2.2.1
+ * fixes predicted candidates
+
+ version 2.2.0
+ * bug fixes
+
+ The proposal is to backport the disco versions of those packages to
+ bionic and cosmic in an attempt to prevent crashes. Proposed uploads are
+ available in this PPA:
+
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
+
+ [Test Case]
+
+ * Install from {bionic,cosmic}-proposed:
+ - libpinyin13
+ - libpinyin-data
+ - ibus-libpinyin
+
+ * Use "Intelligent Pinyin" for typing and confirm that no new issues
+ show up when doing so.
+
+ (This is apparently not a confirmation that the upload really fixes the
+ bug. Time will tell.)
+
+ [Regression Potential]
+
+ The changes are mostly bug fixes, so the regression risk should be
+ limited. Also consider that the starting point is a rather unstable
+ functionality.
+
+ [Original description]
+
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the Ubuntu
Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
In Progress
Status in libpinyin source package in Bionic:
In Progress
Status in ibus-libpinyin source package in Cosmic:
In Progress
Status in libpinyin source package in Cosmic:
In Progress
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. Time will tell.)
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least
[Desktop-packages] [Bug 1829785] Re: Evince: ∞ not found
** Changed in: evince (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in evince package in Ubuntu: New Bug description: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1829785/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Looks like that the new version of network-manager is not working correctly with the systemd-resolved of Bionic. ** Tags added: regression-update ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: New Status in network-manager source package in Bionic: New Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
I'm on 19.04 and I seem to be able to reproduce this at least once a day while I leave my screen locked overnight. Am willing to provide logs and core dumps if possible. Just let me know how/what you need to capture. Each morning when I log back in, the screen will sit and freeze for a minute or so while gnome shell crashes and restarts, but at least it keeps my windows and workspaces open / in place. A bit after that is when apport gives me the dialog. -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+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 1829785] [NEW] Evince: ∞ not found
Public bug reported: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Document to view" https://bugs.launchpad.net/bugs/1829785/+attachment/5265120/+files/q.pdf ** Description changed: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: - 1) Open the attached document in Evince + 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field - 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). On the contrary, I expect the symbol to be found (the pane shows page 1 and the context). + 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in evince package in Ubuntu: New Bug description: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1829785/+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 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Is there any update on this? -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 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-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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] Re: [HP Laptop 14-ma0xxx] No sound after suspend
It also affects kernel version 5.0.0-16 (installed from disco-proposed) -- 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: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete 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 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1826757] Re: libreoffice in 19.04 not responding on ODT, working on ODS
I attach an example of a document that takes 20 secs to load, followed by a cp/paste into a new document that loads very quickly. ** Attachment added: "LoadingSlowly_onewordonly.odt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757/+attachment/5265117/+files/LoadingSlowly_onewordonly.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1826757 Title: libreoffice in 19.04 not responding on ODT, working on ODS Status in libreoffice package in Ubuntu: Incomplete Bug description: Libreoffice 6.2.2.2 20(Build:2) hangs on 19.04 with "Loading document.." on ODTs, but not on ODSs. I had no issues on 18.10. EXPECTED: ODT file opens WHAT HAPPENS INSTEAD: * blank LibreOffice 6.2 window opens with brief message "Loading document.." * when closing the window by clicking on the X a selection box with "force quit" appear. If I click on this right away the mouse freezes. After liberating the mouse with CTRl-ALT-DEL I can click again on force quit and kill the window. * The problem occurs even when the hidden lock file has been removed. TROUBLESHOOTING * Purging libreoffice, reboot, reinstall does not help. * At first occurrence of the issue, and starting from terminal I got "failed to read path from javaldx", was advised to install java* * https://askubuntu.com/questions/1138438/libreoffice-file-locking-issues-in-19-04-no-problems-in-18-10 WORKAROUND Remove /home/myname/.config/libreoffice. But this only works for a short while, and removing the directory must repeated over and over again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-core 1:6.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 19:26:29 2019 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2019-04-19 (9 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757/+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 1826757] Re: libreoffice in 19.04 not responding on ODT, working on ODS
** Attachment added: "CpPasted_Now loading FAST_LoadingSlowly_onewordonly_.odt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757/+attachment/5265118/+files/CpPasted_Now%20loading%20FAST_LoadingSlowly_onewordonly_.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1826757 Title: libreoffice in 19.04 not responding on ODT, working on ODS Status in libreoffice package in Ubuntu: Incomplete Bug description: Libreoffice 6.2.2.2 20(Build:2) hangs on 19.04 with "Loading document.." on ODTs, but not on ODSs. I had no issues on 18.10. EXPECTED: ODT file opens WHAT HAPPENS INSTEAD: * blank LibreOffice 6.2 window opens with brief message "Loading document.." * when closing the window by clicking on the X a selection box with "force quit" appear. If I click on this right away the mouse freezes. After liberating the mouse with CTRl-ALT-DEL I can click again on force quit and kill the window. * The problem occurs even when the hidden lock file has been removed. TROUBLESHOOTING * Purging libreoffice, reboot, reinstall does not help. * At first occurrence of the issue, and starting from terminal I got "failed to read path from javaldx", was advised to install java* * https://askubuntu.com/questions/1138438/libreoffice-file-locking-issues-in-19-04-no-problems-in-18-10 WORKAROUND Remove /home/myname/.config/libreoffice. But this only works for a short while, and removing the directory must repeated over and over again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-core 1:6.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 19:26:29 2019 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2019-04-19 (9 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757/+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 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_na
No crash has been recorded for 3.32.1-2ubuntu1 and SRU'ed version for this, so marking as verified ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813716 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: [ Impact ] GNOME Shell crashes on restart or when ending the session [ Test Case ] Under X11, try to reload the shell multiple times using - Alt+F2: write 'r', press 'enter'. - Or quit it writing in the run dialog 'debugexit'. Repeat multiple times, no crash caused by x11 calls should happen. [ Regression potential ] Nothing known, window actors might not be painted on reload. --- Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1813716/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
I have a similar setup and am experiencing the same thing since the update. Thanks for narrowing it down to network-manager! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: New Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1826933] Re: gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_mana
No crash has been recorded by e.u.c in versions mayor than 3.32.1-2ubuntu1, so marking as verified. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826933 Title: gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_manager_rebuild_logical_monitors_derived Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: [ Impact ] Gnome shell crashes in meta_monitor_mode_get_resolution This seems to happen when starting gnome-shell with no display on (headless). [ Test case ] - Start gnome-shell in a desktop (i.e. one with no embedded display) setup with all the monitors off - Gnome shell should start properly, without crashing - Anyway monitor results in https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12 to check if errors goes down [ Regression potential ] Scale isn't properly computed for monitors with higher DPI --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826933/+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
I can get the dock back with alt-f2-r to restart the gnome shell, so I have a workaround for now. But this is obviously an issue. -- 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: Confirmed 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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
@vanvugt Thank you for your answer. I tried the kernel versions 5.0.0-13 and 4.3.0-04 as well. For the first one, the same problem occured (sound only after a fresh boot) and the second one couldn't be installed correctly because of missing libraries (a boot was possible, but e.g. the mouse pointer was not moving). I have already tried to reconfigure pulseaudio, to force alsa-audio to reload (it does reload but doesn't change anything). Here is my output of aplay: $ aplay -L default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, ALC236 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers hdmi:CARD=PCH,DEV=0 HDA Intel PCH, HDMI 0 HDMI Audio Output hdmi:CARD=PCH,DEV=1 HDA Intel PCH, HDMI 1 HDMI Audio Output hdmi:CARD=PCH,DEV=2 HDA Intel PCH, HDMI 2 HDMI Audio Output hdmi:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 3 HDMI Audio Output hdmi:CARD=PCH,DEV=4 HDA Intel PCH, HDMI 4 HDMI Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct sample mixing device dmix:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample mixing device dmix:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct sample mixing device dmix:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct sample mixing device dmix:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct sample mixing device dmix:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample snooping device dsnoop:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct sample snooping device dsnoop:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct sample snooping device dsnoop:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct sample snooping device dsnoop:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct hardware device without any conversions hw:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct hardware device without any conversions hw:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct hardware device without any conversions hw:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct hardware device without any conversions hw:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Hardware device with all software conversions plughw:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Hardware device with all software conversions plughw:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Hardware device with all software conversions plughw:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Hardware device with all software conversions plughw:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output -- 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: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete 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
[Desktop-packages] [Bug 1801494] Re: dock missing
This bug hasn't been addressed and is obviously still an issue. Why was it allowed to expire? I have a relatively clean 18.04 install, and it's happening to me too. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Expired => Confirmed -- 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: Confirmed 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 1000534] Re: Gnome-Screenshot is not using the last saved folder to preselect
*** This bug is a duplicate of bug 977228 *** https://bugs.launchpad.net/bugs/977228 more people confirm in comments/solutions https://askubuntu.com/questions/114429/default-save-directory-for-gnome- screenshot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1000534 Title: Gnome-Screenshot is not using the last saved folder to preselect Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: after you save one screenshot in another folder, then close the application and take a screenshot it is not preselecting that folder, and you end up having to navigating it to again eventhough the last saved folder is recorded in dconf settings it is not being used this wasn't the case in Ubuntu 10.10 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Thu May 17 13:15:32 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-03-31 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1000534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()
Will test om thursday Den mån 20 maj 2019 16:30Łukasz Zemczak <1821...@bugs.launchpad.net> skrev: > Hello Per-Inge, or anyone else affected, > > Accepted nautilus into disco-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-disco to verification-done-disco. If it does not fix > the bug for you, please add a comment stating that, and change the tag > to verification-failed-disco. In either case, without details of your > testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: nautilus (Ubuntu Disco) >Status: New => Fix Committed > > ** Tags added: verification-needed verification-needed-disco > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1821435 > > Title: > nautilus crashed with SIGABRT in g_assertion_message() > > Status in Nautilus: > Fix Released > Status in nautilus package in Ubuntu: > Fix Released > Status in nautilus source package in Disco: > Fix Committed > > Bug description: > Copied a file from a server to ~/Documents and used the Star function. > Got this crash two times with different files. > > ProblemType: Crash > DistroRelease: Ubuntu 19.04 > Package: nautilus 1:3.32.0-0ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 > Uname: Linux 5.0.0-8-generic x86_64 > ApportVersion: 2.20.10-0ubuntu23 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 23 07:53:09 2019 > ExecutablePath: /usr/bin/nautilus > InstallationDate: Installed on 2018-11-24 (118 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) > ProcCmdline: /usr/bin/nautilus --gapplication-service > Signal: 6 > SourcePackage: nautilus > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >nautilus_window_slot_get_location () >?? () >g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: nautilus crashed with SIGABRT in g_assertion_message_expr() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > separator: > > usr_lib_nautilus: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/nautilus/+bug/1821435/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1821435 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Disco: Fix Committed Bug description: Copied a file from a server to ~/Documents and used the Star function. Got this crash two times with different files. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 07:53:09 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-11-24 (118 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_window_slot_get_location () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1821435/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp` `sudo apt install nvidia-driver-` (check in GUI "Additional Drivers", mine is `430`) everything works. Even the screen layout wasn't broken. Thx to Dmitrii! -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II)
[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Dell Precision 5520 freeze cuz of Nvidia confirmed. `sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it again. -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Leggiero
[Desktop-packages] [Bug 1822403] Re: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed.
I think I am using ibus-libpinyin 1.11.0-1 when I first report this issue. However, after removing the ibus cache as in my comment #6, I haven't seen the crash since then. I guess we can close this issue. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1822403 Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. Status in ibus-libpinyin package in Ubuntu: New Bug description: Every time I use Win key + space to switch input methods, I will see the crash on my system. I am currently on Ubuntu 19.04 (Beta) and it was working fine on Ubuntu 18.10 which was the system I have upgraded from. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: ibus-libpinyin 1.11.0-1 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 AssertionMessage: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 19:59:24 2019 ExecutablePath: /usr/lib/ibus/ibus-engine-libpinyin InstallationDate: Installed on 2018-10-16 (165 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/ibus/ibus-engine-libpinyin --ibus Signal: 6 SourcePackage: ibus-libpinyin StacktraceTop: __assert_fail_base (fmt=0x7f3b02880588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=0x7f3b02c6d720 "bool pinyin::copy_bdb(DB*, DB*)") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 pinyin_init () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 ?? () Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. UpgradeStatus: Upgraded to disco on 2019-03-23 (6 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1822403/+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 1245473]
I like the helpful info you supply to your articles. I’ll bookmark your blog and take a look at once more here frequently. I am somewhat sure I will be told plenty of new stuff right right here! Good luck for the following! https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/ https://www.writecdr.com/acs-rpl-report-samples/ -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1683383]
I like the helpful info you supply to your articles. I’ll bookmark your blog and take a look at once more here frequently. I am somewhat sure I will be told plenty of new stuff right right here! Good luck for the following! https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/ https://www.writecdr.com/acs-rpl-report-samples/ -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1768166] Re: Random crashes
As I stated in the Chinese Ubuntu forum, I almost always stick to only the LTS versions of Ubuntu. I made an exception wrt 18.04 LTS and moved up to 19.04 and even 19.10 because ibus-libpinyin 1.11 is not available in 18.04. However, 19.04 and 19.10 have their own problems and are not recommended at least for now. On Mon, May 20, 2019 at 4:22 AM Gunnar Hjalmarsson < 1768...@bugs.launchpad.net> wrote: > I have hesitated about upgrading, since the problem seems to have been > present also with version 1.10 according to the crash reports. > > However, in Ubuntu 19.04 ibus-libpinyin was upgraded to 1.11, and it > looks like there is a significant reduction of crashes in 19.04 compared > to 18.04 and 18.10. > > https://errors.ubuntu.com/?package=ibus-libpinyin=month > > So I'm going to do this now. > > ** Also affects: libpinyin (Ubuntu Cosmic) >Importance: Undecided >Status: New > > ** Also affects: ibus-libpinyin (Ubuntu Cosmic) >Importance: Undecided >Status: New > > ** Changed in: ibus-libpinyin (Ubuntu Cosmic) >Importance: Undecided => Medium > > ** Changed in: ibus-libpinyin (Ubuntu Cosmic) >Status: New => In Progress > > ** Changed in: ibus-libpinyin (Ubuntu Cosmic) > Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) > > ** Changed in: libpinyin (Ubuntu Cosmic) >Importance: Undecided => Medium > > ** Changed in: libpinyin (Ubuntu Cosmic) >Status: New => In Progress > > ** Changed in: libpinyin (Ubuntu Cosmic) > Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768166 > > Title: > Random crashes > > Status in ibus-libpinyin package in Ubuntu: > Fix Released > Status in libpinyin package in Ubuntu: > Fix Released > Status in ibus-libpinyin source package in Bionic: > In Progress > Status in libpinyin source package in Bionic: > In Progress > Status in ibus-libpinyin source package in Cosmic: > In Progress > Status in libpinyin source package in Cosmic: > In Progress > > Bug description: > I have experienced random ibus-libpinyin crashes in bionic. I cannot > reproduce it, but it occurred at least a few times, even after the > official bionic release. Same crashes were also reported in the > Ubuntu Chinese forum. > > Currently, the workaround is to delete the ~/.cache/ibus/libpinyin > folder. > > I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he > suggested that we update the version of ibus-libpinyin to 1.10. > > Can we give this update a trial? > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: In Progress Status in ibus-libpinyin source package in Cosmic: In Progress Status in libpinyin source package in Cosmic: In Progress Bug description: I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+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 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
Actually, I don't see an upload for bionic for fixing this bug. The task was already set to 'Fix Committed' - where is the bionic fix committed? Is it in the current bionic gnome-software already? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+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 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
Ok, so I have some trouble with the SRUs addressing this bug. Per SRU policy [1], we in generall only should only aim for fixing 'high-impact bugs'. This bug seems to be marked with an importance of Low, which normally isn't per-se good SRU material (if it was bundled with some other, high-importance changes, the story would be slightly different). That being said, the issue does seem to be quite annoying and getting it fixed can improve the overall user-experience for our LTS users. That being said, after actually checking the change, I feel it's safe enough that I think I'll be accepting this for both series - mainly for bionic, but let's also get disco as 'consistency' for people doing funny upgrades to a non-LTS series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+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 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
[1] https://wiki.ubuntu.com/StableReleaseUpdates#When ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+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 1735071] Please test proposed package
Hello Scott, or anyone else affected, Accepted gnome-software into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.6-2ubuntu4.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+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 1828735] Re: Update to 3.32.1
Hello Sebastien, or anyone else affected, Accepted nautilus into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nautilus (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828735 Title: Update to 3.32.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Disco: Fix Committed Bug description: * Impact That's a stable GNOME update, summary of the most important changes https://ftp.acc.umu.se/pub/GNOME/sources/nautilus/3.32/nautilus-3.32.1.news * Test case The update is covered by the standard GNOME MRE, nothing specific to test but we should ensure nautilus still work without regression * Regression potential There are changes are the thumbnailing code, make sure previews keep working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828735/+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 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()
Hello Per-Inge, or anyone else affected, Accepted nautilus into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nautilus (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1821435 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Disco: Fix Committed Bug description: Copied a file from a server to ~/Documents and used the Star function. Got this crash two times with different files. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 07:53:09 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-11-24 (118 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_window_slot_get_location () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1821435/+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 1768166] Re: Random crashes
I have hesitated about upgrading, since the problem seems to have been present also with version 1.10 according to the crash reports. However, in Ubuntu 19.04 ibus-libpinyin was upgraded to 1.11, and it looks like there is a significant reduction of crashes in 19.04 compared to 18.04 and 18.10. https://errors.ubuntu.com/?package=ibus-libpinyin=month So I'm going to do this now. ** Also affects: libpinyin (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ibus-libpinyin (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: ibus-libpinyin (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: ibus-libpinyin (Ubuntu Cosmic) Status: New => In Progress ** Changed in: ibus-libpinyin (Ubuntu Cosmic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: libpinyin (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: libpinyin (Ubuntu Cosmic) Status: New => In Progress ** Changed in: libpinyin (Ubuntu Cosmic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: In Progress Status in ibus-libpinyin source package in Cosmic: In Progress Status in libpinyin source package in Cosmic: In Progress Bug description: I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+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 1829651] Re: Caps Lock indicator on screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Confirmed Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1829651] Re: Caps Lock indicator on screen
The way I understand Mustafa's report this is about the general lack of a caps lock state indicator on (so primarily post-login, in gnome- shell). Bug #1734887 rather discusses the lack of an indicator pre-login (gdm), so is a different issue. ** This bug is no longer a duplicate of bug 1734887 No caps lock indicator on login screen -- 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/1829651 Title: Caps Lock indicator on screen Status in gnome-shell package in Ubuntu: Confirmed Bug description: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-14 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Tags: bionic Uname: Linux 4.18.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+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 1822403] Re: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed.
Thanks for your report! ibus-libpinyin on Ubuntu 19.04 was updated to version 1.11 on 2019-02-06. Have you possibly noticed an improvement since then? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1822403 Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. Status in ibus-libpinyin package in Ubuntu: New Bug description: Every time I use Win key + space to switch input methods, I will see the crash on my system. I am currently on Ubuntu 19.04 (Beta) and it was working fine on Ubuntu 18.10 which was the system I have upgraded from. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: ibus-libpinyin 1.11.0-1 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 AssertionMessage: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 19:59:24 2019 ExecutablePath: /usr/lib/ibus/ibus-engine-libpinyin InstallationDate: Installed on 2018-10-16 (165 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/ibus/ibus-engine-libpinyin --ibus Signal: 6 SourcePackage: ibus-libpinyin StacktraceTop: __assert_fail_base (fmt=0x7f3b02880588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=0x7f3b02c6d720 "bool pinyin::copy_bdb(DB*, DB*)") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 pinyin_init () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 ?? () Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. UpgradeStatus: Upgraded to disco on 2019-03-23 (6 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1822403/+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 1822403] Re: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1822403 Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. Status in ibus-libpinyin package in Ubuntu: New Bug description: Every time I use Win key + space to switch input methods, I will see the crash on my system. I am currently on Ubuntu 19.04 (Beta) and it was working fine on Ubuntu 18.10 which was the system I have upgraded from. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: ibus-libpinyin 1.11.0-1 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 AssertionMessage: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 19:59:24 2019 ExecutablePath: /usr/lib/ibus/ibus-engine-libpinyin InstallationDate: Installed on 2018-10-16 (165 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/ibus/ibus-engine-libpinyin --ibus Signal: 6 SourcePackage: ibus-libpinyin StacktraceTop: __assert_fail_base (fmt=0x7f3b02880588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f3b02c6d4fd "DB_NOTFOUND == ret", file=0x7f3b02c6d4f1 "bdb_utils.h", line=63, function=0x7f3b02c6d720 "bool pinyin::copy_bdb(DB*, DB*)") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 pinyin_init () from /usr/lib/x86_64-linux-gnu/libpinyin.so.13 ?? () Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. UpgradeStatus: Upgraded to disco on 2019-03-23 (6 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1822403/+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 1829746] [NEW] LibreOffice Impress embed video broken outside slide
Public bug reported: Summary: If you insert video in Impress slideshow and the video is bigger than slide or is partially out of slide, the libreoffice UI or "slideshow" breaks. See the video [1] This bug is related to "libreoffice-gtk3" and "gstreamer1.0-gtk3". The bug does not accrue if using "libreoffice-gtk2" or none (the default LibreOffice VCL). Tested on Ubuntu 19.04. Enabled -purposed and upgraded libreoffice to "6.1.6" So the current situation (upgrading to "6.1.6") is that video plays correctly IF the video is fully inside the slide. If the video is a bit outside the slide or video is bigger than slide, when pressing "play" button in right pane, libreoffice UI totally breaks. Only the ~1/8 of window display content other space is white. If resizing the window, the content gets even smaller. Also when running the slideshow, it's broken. I need to close impress and run it again. Can someone else confirm similar behavior? [1] https://www.youtube.com/watch?v=e6UDDSBg4m8 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1829746 Title: LibreOffice Impress embed video broken outside slide Status in libreoffice package in Ubuntu: New Bug description: Summary: If you insert video in Impress slideshow and the video is bigger than slide or is partially out of slide, the libreoffice UI or "slideshow" breaks. See the video [1] This bug is related to "libreoffice-gtk3" and "gstreamer1.0-gtk3". The bug does not accrue if using "libreoffice-gtk2" or none (the default LibreOffice VCL). Tested on Ubuntu 19.04. Enabled -purposed and upgraded libreoffice to "6.1.6" So the current situation (upgrading to "6.1.6") is that video plays correctly IF the video is fully inside the slide. If the video is a bit outside the slide or video is bigger than slide, when pressing "play" button in right pane, libreoffice UI totally breaks. Only the ~1/8 of window display content other space is white. If resizing the window, the content gets even smaller. Also when running the slideshow, it's broken. I need to close impress and run it again. Can someone else confirm similar behavior? [1] https://www.youtube.com/watch?v=e6UDDSBg4m8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1829746/+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 1734887] Re: No caps lock indicator on login screen
i am currently using Lenovo ThinkPad x230 which doesnt have physical caps lock indicator on keyboard like some other ThinkPad laptops. i noticed that on Ubuntu 18.04.2 there is no Caps Lock indicator on screen. it would be perfect if you put it default as other on screen indicators such as volume controls, microphone indicator, screen brightness indicator. thanks. -- 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/1734887 Title: No caps lock indicator on login screen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Expected results: Pressing the Caps Lock key should cause an indicator to appear on the login screen. Actual results: Pressing the Caps Lock key does not cause the login screen to change in any way. Reproducing: 1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no indicator. (gdm3 3.26.1-3ubuntu3) 2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an indicator. (gdm-3.26.2.1-1.fc27.x86_64) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 Uname: Linux 4.14.2-041402-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Nov 28 08:24:31 2017 InstallationDate: Installed on 2017-11-05 (22 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734887/+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 1826586] Re: Unable to drag Nautilus tab to new window
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1826586 Title: Unable to drag Nautilus tab to new window Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus (Files) application 3. Open new tab with any way (Ctrl+T, Ctrl+Enter for some folder - does not really matter) 4. Try to drag the opened Tab out the current window to create new window from this tab Expected results: * user is able to drag tab to new window (as in previous 18.10 - see screencast) Actual results: * user is unable to drag tab to new window Note: first seen on AskUbuntu ( https://askubuntu.com/q/1137967/66509 ) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 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: Fri Apr 26 19:11:42 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1826586/+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 1829735] Re: Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade
** Package changed: texinfo (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1829735 Title: Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade Status in apt package in Ubuntu: New Bug description: **Specs** - Asus Zenbook 14 UX433FN (NVMe PCIe SSD) - Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine. **Background** After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and subsequent update using either command prompt (sudo apt upgrade) or via the GUI that appears after first reboot (security updates etc.) **How to reproduce the bug** 1. Fresh (minimal) install of Ubuntu 18.10 2. Reboot successfully. 3. Either: 3a. Open terminal and run $ sudo apt upgrade 3b. Wait for Ubuntu to automatically show the GUI prompt asking for installation of important updates (eg. security) 4. Update successful 5. Reboot 6. Boot stuck at `Loading initial ramdisk...`, even in recovery mode. **Suspected problem** Broken package. Note that minimal installation is used. More information in the AskUbuntu Forum: https://askubuntu.com/questions/1144688/ubuntu-18-10-stuck-at-initialising-ramdisk-after-fresh-install-and-subsequent-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829735/+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 1322784] Re: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug
Upstream bug was closed "VERIFIED FIXED" on 2015-04-06 No further comments re bug here or upstream for over four years, closing as fixed. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1322784 Title: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in gcc-4.8 package in Ubuntu: Incomplete Bug description: The most common Firefox crash on Linux in Mozilla's crash-stats system is crashes in the function flag_qsort. These crashes occur: * only on x86 architecture * only on Ubuntu packages (and not on Mozilla's builds) * on precise and saucy and trusty (based on kernel versions reported with the crashes) and appear to be due to a compiler bug in the compiler used to generate Ubuntu's builds. (It could be a common compiler bug triggered by different compiler options or a compiler bug specific to Ubuntu's gcc.) The analysis that leads to the conclusion that this is a compiler bug is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 . In particular, the compiler is miscompiling an access to an element of an array of unsigned short as a 32-bit read, and when the unsigned short in question is the last one in the allocation and that allocation is aligned so that the byte following has a different 0x10 bit, this can lead to crashes. The most recent (whenever you follow the link) 7 days of crash reports are available at: https://crash- stats.mozilla.com/report/list?signature=flag_qsort=Firefox_type=contains_unit=weeks To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1322784/+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 1829735] [NEW] Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade
Public bug reported: **Specs** - Asus Zenbook 14 UX433FN (NVMe PCIe SSD) - Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine. **Background** After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and subsequent update using either command prompt (sudo apt upgrade) or via the GUI that appears after first reboot (security updates etc.) **How to reproduce the bug** 1. Fresh (minimal) install of Ubuntu 18.10 2. Reboot successfully. 3. Either: 3a. Open terminal and run $ sudo apt upgrade 3b. Wait for Ubuntu to automatically show the GUI prompt asking for installation of important updates (eg. security) 4. Update successful 5. Reboot 6. Boot stuck at `Loading initial ramdisk...`, even in recovery mode. **Suspected problem** Broken package. Note that minimal installation is used. More information in the AskUbuntu Forum: https://askubuntu.com/questions/1144688/ubuntu-18-10-stuck-at-initialising-ramdisk-after-fresh-install-and-subsequent-up ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1829735 Title: Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade Status in texinfo package in Ubuntu: New Bug description: **Specs** - Asus Zenbook 14 UX433FN (NVMe PCIe SSD) - Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine. **Background** After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and subsequent update using either command prompt (sudo apt upgrade) or via the GUI that appears after first reboot (security updates etc.) **How to reproduce the bug** 1. Fresh (minimal) install of Ubuntu 18.10 2. Reboot successfully. 3. Either: 3a. Open terminal and run $ sudo apt upgrade 3b. Wait for Ubuntu to automatically show the GUI prompt asking for installation of important updates (eg. security) 4. Update successful 5. Reboot 6. Boot stuck at `Loading initial ramdisk...`, even in recovery mode. **Suspected problem** Broken package. Note that minimal installation is used. More information in the AskUbuntu Forum: https://askubuntu.com/questions/1144688/ubuntu-18-10-stuck-at-initialising-ramdisk-after-fresh-install-and-subsequent-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1829735/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
Could anyone who still has this problem supply a list of the routes he has entered and how he has entered them and also attach the /etc/NetworkManager/system-connections file to this bug report? Thanks. ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Incomplete Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
Michael Gale, your issue is different to the OP's one. The routes the OP has entered are all CIDR notable, he even uses CIDR when entering them via command line. So please report a new bug, showing which routes you have entered and how they end up in /etc/NetworkManager/system-connections. In addition, you could report a bug upstream, suggesting to let the rutes be saved in /etc/NetworkManager/system-connections in dotted-quad notation if they cannot be represented in CIDR notation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1829366] Re: [SRU] Bugfix release 1.14.4
There is some activity upstream on the 1.14 branches, so there might be a 1.14.5, but I'm not sure: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/merge_requests/223 https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/merge_requests/198 Should this SRU wait for a 1.14.5 release? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: In Progress Status in gst-plugins-bad1.0 source package in Bionic: In Progress Status in gst-plugins-base1.0 source package in Bionic: In Progress Status in gst-plugins-good1.0 source package in Bionic: In Progress Status in gst-plugins-ugly1.0 source package in Bionic: In Progress Status in gst-python1.0 source package in Bionic: In Progress Status in gst-rtsp-server1.0 source package in Bionic: In Progress Status in gstreamer-editing-services1.0 source package in Bionic: In Progress Status in gstreamer-vaapi source package in Bionic: In Progress Status in gstreamer1.0 source package in Bionic: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+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 36812]
I like the helpful info you supply to your articles. I’ll bookmark your blog and take a look at once more here frequently. I am somewhat sure I will be told plenty of new stuff right right here! Good luck for the following! https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/ https://www.writecdr.com/acs-rpl-report-samples/ -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: Unknown Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1829718] [NEW] Network printers (cups-browsed) disappear after each CUPS update on client side
Public bug reported: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups-browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1829718 Title: Network printers (cups-browsed) disappear after each CUPS update on client side Status in cups package in Ubuntu: New Bug description: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups- browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829718/+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 1826586] Re: Unable to drag Nautilus tab to new window
Upstream marked it as duplicate of https://gitlab.gnome.org/GNOME/nautilus/issues/615 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #615 https://gitlab.gnome.org/GNOME/nautilus/issues/615 ** Changed in: nautilus Status: Fix Released => Unknown ** Changed in: nautilus Remote watch: gitlab.gnome.org/GNOME/nautilus/issues #944 => gitlab.gnome.org/GNOME/nautilus/issues #615 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1826586 Title: Unable to drag Nautilus tab to new window Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus (Files) application 3. Open new tab with any way (Ctrl+T, Ctrl+Enter for some folder - does not really matter) 4. Try to drag the opened Tab out the current window to create new window from this tab Expected results: * user is able to drag tab to new window (as in previous 18.10 - see screencast) Actual results: * user is unable to drag tab to new window Note: first seen on AskUbuntu ( https://askubuntu.com/q/1137967/66509 ) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 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: Fri Apr 26 19:11:42 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1826586/+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 1826586] Re: Unable to drag Nautilus tab to new window
** Changed in: nautilus Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1826586 Title: Unable to drag Nautilus tab to new window Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus (Files) application 3. Open new tab with any way (Ctrl+T, Ctrl+Enter for some folder - does not really matter) 4. Try to drag the opened Tab out the current window to create new window from this tab Expected results: * user is able to drag tab to new window (as in previous 18.10 - see screencast) Actual results: * user is unable to drag tab to new window Note: first seen on AskUbuntu ( https://askubuntu.com/q/1137967/66509 ) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 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: Fri Apr 26 19:11:42 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1826586/+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 1823134] Re: Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro P1000 Mobile]
** Changed in: upower (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1823134 Title: Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro P1000 Mobile] Status in gnome-shell package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Bug description: ubuntu 18.10 xorg version xorg: Instalovaná verze: 1:7.7+19ubuntu8 Kandidát: 1:7.7+19ubuntu8 Tabulka verzí: *** 1:7.7+19ubuntu8 500 500 http://cz.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status display brightness slider does nothing. Should change brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Apr 4 09:37:32 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: als, master, 4.18.0-17-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.06.03 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.35.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823134/+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 1829699] Re: Switches are gone from the VPN menu
** Tags added: rls-ee-incoming -- 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/1829699 Title: Switches are gone from the VPN menu Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu Desktop Eoan up to date There is no more switch in the system menu for the VPN entries. Although the VPN can still be turned on/off by clicking on the menu entry (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 20 06:48:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1769 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (421 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829699/+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 1829699] Re: Switches are gone from the VPN menu
I guess this is a new bug in gnome-shell 3.32.1, if it didn't exist in 3.32.0...? -- 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/1829699 Title: Switches are gone from the VPN menu Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu Desktop Eoan up to date There is no more switch in the system menu for the VPN entries. Although the VPN can still be turned on/off by clicking on the menu entry (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 20 06:48:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1769 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (421 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829699/+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 1823134] Re: Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro P1000 Mobile]
fixed in 19.4 update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1823134 Title: Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro P1000 Mobile] Status in gnome-shell package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: ubuntu 18.10 xorg version xorg: Instalovaná verze: 1:7.7+19ubuntu8 Kandidát: 1:7.7+19ubuntu8 Tabulka verzí: *** 1:7.7+19ubuntu8 500 500 http://cz.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status display brightness slider does nothing. Should change brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Apr 4 09:37:32 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: als, master, 4.18.0-17-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.06.03 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.35.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823134/+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 1828775] Re: [amdgpu] High memory consumption
Thanks. That's good news. If (while using supported graphics packages and not a PPA) you find the problem returns, like with lots of desktop icons, then please reopen this bug by changing the status back to New. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1828775 Title: [amdgpu] High memory consumption Status in gnome-shell package in Ubuntu: Invalid Bug description: High memory consumption 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: Mon May 13 09:47:53 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-10 (122 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1829710] Re: Login ui is inresponsive
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1822026, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1822026 [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829710 Title: Login ui is inresponsive Status in xorg package in Ubuntu: New Bug description: password character is typed after about 1s when key is pressed and mouse stops for about one sec when hovering over buttons (including user profile button) sometimes instead ubuntu logo is text ubuntu which fixes itself after while. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 08:57:34 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 4.18.0-20-generic, x86_64: installed als, master, 5.0.0-15-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation]) [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.06.03 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.35.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP 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/xorg/+bug/1829710/+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 1798074] Re: LIbreoffice crashes on startup
** Also affects: libreoffice (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: New Bug description: On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca] I have tried entirely removing my profile, ~/.config/libreoffice , but the same problem still exhibits. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Tue Oct 16 12:58:04 2018 InstallationDate: Installed on 2014-04-07 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798074/+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 1829710] [NEW] Login ui is inresponsive
Public bug reported: password character is typed after about 1s when key is pressed and mouse stops for about one sec when hovering over buttons (including user profile button) sometimes instead ubuntu logo is text ubuntu which fixes itself after while. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 08:57:34 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 4.18.0-20-generic, x86_64: installed als, master, 5.0.0-15-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation]) [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.06.03 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.35.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco performance ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829710 Title: Login ui is inresponsive Status in xorg package in Ubuntu: New Bug description: password character is typed after about 1s when key is pressed and mouse stops for about one sec when hovering over buttons (including user profile button) sometimes instead ubuntu logo is text ubuntu which fixes itself after while. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 08:57:34 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 4.18.0-20-generic, x86_64: installed als, master, 5.0.0-15-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation]) [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.06.03 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.35.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP 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:
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Status in mutter source package in Disco: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828775] Re: [amdgpu] High memory consumption
Greetings! I deleted everything from the desktop, I also deleted the packages installed from oibaf-ppa and the problem no longer manifested itself. -- 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/1828775 Title: [amdgpu] High memory consumption Status in gnome-shell package in Ubuntu: Incomplete Bug description: High memory consumption 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: Mon May 13 09:47:53 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-10 (122 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
The correct solution to the problem I've been facing was finally solved on comment #58, thanks @prasanth-s-cmi. I've contacted the kernel developer responsible for these patches introduced around Linux 4.16.1 on https://bugzilla.redhat.com/show_bug.cgi?id=1571330 , and he will blacklist my laptop model (Lenovo G40-80) for newer versions of Linux. Meanwhile, `ahci.mobile_lpm_policy=0` can workaround this problem. ** Bug watch added: Red Hat Bugzilla #1571330 https://bugzilla.redhat.com/show_bug.cgi?id=1571330 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+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
