[Desktop-packages] [Bug 1827181] [NEW] 18.04 - Need to purge and reload alsa and pulseaudio to get sound
Public bug reported: When I start my computer (running Ubuntu 18.04.2 LTS), there is no sound from the speakers plugged into the line-out jack. In order to get sound, I need to run the following sequence of commands: sudo apt-get update && sudo apt-get upgrade sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio pavucontrol sudo alsa force-reload reboot sudo apt-get install pavucontrol pulseaudio --start My system is dual-boot with Windows 10, but it doesn't seem to need me to boot Windows 10 in order to lose the settings in Ubuntu. This problem started on 19 March 2019 when I was trying to record some audio with audacity and I've just found the above fix to get things running, but sadly the problem reverts when I shutdown. Related packages: pulseaudio: Installed: 1:11.1-1ubuntu7.2 Candidate: 1:11.1-1ubuntu7.2 Version table: *** 1:11.1-1ubuntu7.2 500 500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://nz.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 3.0-4 Candidate: 3.0-4 Version table: *** 3.0-4 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1827181 Title: 18.04 - Need to purge and reload alsa and pulseaudio to get sound Status in pulseaudio package in Ubuntu: New Bug description: When I start my computer (running Ubuntu 18.04.2 LTS), there is no sound from the speakers plugged into the line-out jack. In order to get sound, I need to run the following sequence of commands: sudo apt-get update && sudo apt-get upgrade sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio pavucontrol sudo alsa force-reload reboot sudo apt-get install pavucontrol pulseaudio --start My system is dual-boot with Windows 10, but it doesn't seem to need me to boot Windows 10 in order to lose the settings in Ubuntu. This problem started on 19 March 2019 when I was trying to record some audio with audacity and I've just found the above fix to get things running, but sadly the problem reverts when I shutdown. Related packages: pulseaudio: Installed: 1:11.1-1ubuntu7.2 Candidate: 1:11.1-1ubuntu7.2 Version table: *** 1:11.1-1ubuntu7.2 500 500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://nz.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 3.0-4 Candidate: 3.0-4 Version table: *** 3.0-4 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827181/+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 1827181] Re: 18.04 - Need to purge and reload alsa and pulseaudio to get sound
March 2019 may mean the problem started with the released of:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.2
But maybe not. Some other package (like the kernel) might also have
changed around then. To test this theory, please try installing the
previous version *.deb files from:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.1/+build/14932424
You only need the .deb files and not the .ddeb files. And even then you
only need to replace the ones already installed. To get a list of
packages you need, just run:
dpkg -l | grep 11.1-1ubuntu7.2 | awk '{print $2;}'
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
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/1827181
Title:
18.04 - Need to purge and reload alsa and pulseaudio to get sound
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When I start my computer (running Ubuntu 18.04.2 LTS), there is no
sound from the speakers plugged into the line-out jack.
In order to get sound, I need to run the following sequence of commands:
sudo apt-get update && sudo apt-get upgrade
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio pavucontrol
sudo alsa force-reload
reboot
sudo apt-get install pavucontrol
pulseaudio --start
My system is dual-boot with Windows 10, but it doesn't seem to need me
to boot Windows 10 in order to lose the settings in Ubuntu.
This problem started on 19 March 2019 when I was trying to record some
audio with audacity and I've just found the above fix to get things
running, but sadly the problem reverts when I shutdown.
Related packages:
pulseaudio:
Installed: 1:11.1-1ubuntu7.2
Candidate: 1:11.1-1ubuntu7.2
Version table:
*** 1:11.1-1ubuntu7.2 500
500 http://nz.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:11.1-1ubuntu7 500
500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
*** 1.0.25+dfsg-0ubuntu5 500
500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://nz.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
pavucontrol:
Installed: 3.0-4
Candidate: 3.0-4
Version table:
*** 3.0-4 500
500 http://nz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827181/+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 1824670] Re: Boot to black screen after Kubuntu 19.04 install
Hi guys! Thanks for you job! However, the bug is still here. Just updated from 18.10 to 19.04 (using do-system-upgrade) and bumped into this issue. I have the same symptoms with the black screen, no reaction on Ctrl+Alt+F(n), dmesg (via ssh) with lots of output - relevant part pasted below. Driver version is 340.107-0ubuntu3 (installed via sudo ubuntu-drivers autoinstall). Tried to play with GRUB_TERMINAL=console and all combinations of two parameters in GRUB_CMDLINE_LINUX_DEFAULT="nomodeset slab_common.usercopy_fallback=Y" (second one found somewhere in the inet). Nothing helps. Let me know if any further information from me may help. Regards, A. [ 22.834264] [ cut here ] [ 22.834268] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)! [ 22.834284] WARNING: CPU: 3 PID: 1621 at mm/usercopy.c:83 usercopy_warn+0x81/0xa0 [ 22.834285] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc btusb btrtl btbcm btintel bluetooth ecdh_generic input_leds nls_iso8859_1 nvidia_uvm(POE) snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_hda_codec joydev snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi nvidia(POE) snd_seq coretemp applesmc kvm_intel snd_seq_device snd_timer kvm input_polldev irqbypass snd soundcore i5400_edac mac_hid i5k_amb sch_fq_codel sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid nouveau mxm_wmi wmi video i2c_algo_bit ttm drm_kms_helper ahci syscopyarea sysfillrect firewire_ohci sysimgblt libahci i2c_i801 fb_sys_fops pata_acpi lpc_ich firewire_core drm e1000e crc_itu_t [ 22.834319] CPU: 3 PID: 1621 Comm: Xorg Tainted: P OE 5.0.0-14-generic #15-Ubuntu [ 22.834320] Hardware name: Apple Inc. MacPro3,1/Mac-F42C88C8, BIOS MP31.88Z.006C.B05.0802291410 02/29/08 [ 22.834321] RIP: 0010:usercopy_warn+0x81/0xa0 [ 22.834323] Code: 8f a6 41 51 4d 89 d8 48 c7 c0 98 a1 8e a6 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 28 c2 8f a6 4c 89 d2 48 89 c6 e8 11 03 df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 e2 ae 91 a6 49 89 f1 49 89 f3 eb [ 22.834324] RSP: 0018:ae8c82013b58 EFLAGS: 00010282 [ 22.834326] RAX: RBX: 99c9a325ae58 RCX: 0006 [ 22.834326] RDX: 0007 RSI: 0092 RDI: 99c9aead6440 [ 22.834327] RBP: ae8c82013b70 R08: 0001 R09: 03f3 [ 22.834328] R10: 0004 R11: R12: 0003 [ 22.834329] R13: 0001 R14: 99c9a325ae5b R15: 99c9a325aea0 [ 22.834330] FS: 7f0b25726a80() GS:99c9aeac() knlGS: [ 22.834332] CS: 0010 DS: ES: CR0: 80050033 [ 22.834332] CR2: 7f0b20d1e000 CR3: 000462cca000 CR4: 06e0 [ 22.834333] Call Trace: [ 22.834340] __check_heap_object+0xc2/0x110 [ 22.834342] __check_object_size+0x166/0x192 [ 22.834518] os_memcpy_to_user+0x26/0x50 [nvidia] [ 22.834601] _nv001372rm+0xa5/0x260 [nvidia] [ 22.834604] WARNING: kernel stack frame pointer at 2afdb6e3 in Xorg:1621 has bad value d0f12375 [ 22.834605] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 [ 22.834607] faf3ae30: ae8c82013b80 (0xae8c82013b80) [ 22.834609] 20f407ce: a587e342 (__check_heap_object+0xc2/0x110) [ 22.834610] c266b5f3: ae8c82013bb0 (0xae8c82013bb0) [ 22.834611] 6766f122: a58a6af6 (__check_object_size+0x166/0x192) [ 22.834612] 3e321a4b: 0003 (0x3) [ 22.834613] 899719c5: 99c9a325ae58 (0x99c9a325ae58) [ 22.834614] b60c2ee1: 55cd221aca20 (0x55cd221aca20) [ 22.834614] 8b8bf890: 99c9a325ae58 (0x99c9a325ae58) [ 22.834615] 7ce4f889: ae8c82013bd8 (0xae8c82013bd8) [ 22.834690] a8f3c230: c0f46026 (os_memcpy_to_user+0x26/0x50 [nvidia]) [ 22.834690] 3fa85e96: 0003 (0x3) [ 22.834691] 85c4b0d2: ... [ 22.834692] 3f0657a2: 55cd221aca20 (0x55cd221aca20) [ 22.834693] 2afdb6e3: 99c9a325ae50 (0x99c9a325ae50) [ 22.834775] d6e75a78: c0ecbd15 (_nv001372rm+0xa5/0x260 [nvidia]) [ 22.834776] 801c975c: ... [ 22.834777] 6adf9a3e: 99c9a5814928 (0x99c9a5814928) [ 22.834778] 3e673027: 99c9a325aed8 (0x99c9a325aed8) [ 22.834778] 6b537a97: 99c9a325ae80 (0x99c9a325ae80) [ 22.834869] 8fb2a5b0: c0b4a88a (_nv004784rm+0x4eba/0x5500 [nvidia]) [ 22.834870] e82ad0f1: ... [ 22.834871] 16d8f567: 99c9a325aed8 (0x99c9a325aed8) [ 22.834871] 98f78ca2: 7ffe3d8467c0 (0x7ffe3d8467c0) [ 22.8349
[Desktop-packages] [Bug 1770629] Re: Keyboard and mouse lockup when using media keys to adjust volume
** Attachment added: "journalctl output when reproducing this bug" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1770629/+attachment/5260476/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1770629 Title: Keyboard and mouse lockup when using media keys to adjust volume Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 LTS gnome-settings-daemon 3.28.1-0ubuntu1 Summary: When I press any of my keyboard's volume up/down/mute keys, my keyboard and mouse lock up completely. (Mouse pointer frozen and no keypresses have any effect). The rest of the system continues to function normally. The on-screen volume notification appears repeatedly every few seconds. Variations: --- Occasionally, I can press the buttons a few times with no effect, before the lock-up eventually happens. Also occasionally, my Gnome session may crash completely to a black screen a few seconds after the input devices lock up. I haven't been able to discern a pattern to when these different effects occur. Troubleshooting attempted: -- I can reproduce this when running from a Live USB on the same system. Disabling the keyboard shortcuts for volume up/down and mute in the keyboard settings GUI does not prevent this issue. If I set different keys for these shortcuts, they work fine - the problem is specific to my keyboard's special media keys. The other (non-audio-related) media keys on my keyboard work fine. I have gone through the suggested "Useful Information" steps at https://wiki.ubuntu.com/Hotkeys/Troubleshooting and will attach the output files to this report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 11 12:30:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (147 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-04-27 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1770629/+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 1770629] Re: Keyboard and mouse lockup when using media keys to adjust volume
Thanks for the reply. The PC is a desktop - Dell Precision Tower 5810. However... I may have narrowed this down to something related to my Dell USB soundbar. I've disconnected it and the issue goes away. The soundbar is a Dell AC511. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1770629 Title: Keyboard and mouse lockup when using media keys to adjust volume Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 LTS gnome-settings-daemon 3.28.1-0ubuntu1 Summary: When I press any of my keyboard's volume up/down/mute keys, my keyboard and mouse lock up completely. (Mouse pointer frozen and no keypresses have any effect). The rest of the system continues to function normally. The on-screen volume notification appears repeatedly every few seconds. Variations: --- Occasionally, I can press the buttons a few times with no effect, before the lock-up eventually happens. Also occasionally, my Gnome session may crash completely to a black screen a few seconds after the input devices lock up. I haven't been able to discern a pattern to when these different effects occur. Troubleshooting attempted: -- I can reproduce this when running from a Live USB on the same system. Disabling the keyboard shortcuts for volume up/down and mute in the keyboard settings GUI does not prevent this issue. If I set different keys for these shortcuts, they work fine - the problem is specific to my keyboard's special media keys. The other (non-audio-related) media keys on my keyboard work fine. I have gone through the suggested "Useful Information" steps at https://wiki.ubuntu.com/Hotkeys/Troubleshooting and will attach the output files to this report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 11 12:30:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (147 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-04-27 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1770629/+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 1770629] Re: Keyboard and mouse lockup when using media keys to adjust volume
Here is the relevant part of `lsusb -v` for this soundbar. ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1770629/+attachment/5260479/+files/lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1770629 Title: Keyboard and mouse lockup when using media keys to adjust volume Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 LTS gnome-settings-daemon 3.28.1-0ubuntu1 Summary: When I press any of my keyboard's volume up/down/mute keys, my keyboard and mouse lock up completely. (Mouse pointer frozen and no keypresses have any effect). The rest of the system continues to function normally. The on-screen volume notification appears repeatedly every few seconds. Variations: --- Occasionally, I can press the buttons a few times with no effect, before the lock-up eventually happens. Also occasionally, my Gnome session may crash completely to a black screen a few seconds after the input devices lock up. I haven't been able to discern a pattern to when these different effects occur. Troubleshooting attempted: -- I can reproduce this when running from a Live USB on the same system. Disabling the keyboard shortcuts for volume up/down and mute in the keyboard settings GUI does not prevent this issue. If I set different keys for these shortcuts, they work fine - the problem is specific to my keyboard's special media keys. The other (non-audio-related) media keys on my keyboard work fine. I have gone through the suggested "Useful Information" steps at https://wiki.ubuntu.com/Hotkeys/Troubleshooting and will attach the output files to this report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 11 12:30:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (147 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-04-27 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1770629/+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 1164016] Re: restore type-ahead find
+1 @teo1978 (teo8976) Users will decide. The most radical solution would be purging the whole GNOME desktop and install MATE DE instead. I switched to MATE in 2013 and I'm completely happy with it. In MATE the Caja file-manager (fork of Nautilus) has normal search even in 19.04. Also it has Extra Pane (acessible with key). See https://askubuntu.com/a/1097974/66509 for removal process. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1823722] Re: keyboard shortcuts are displayed not translated
Gunnar / Marco, could one of you please SRUify this bug? It's going to be included in the upload (backport from eoan). -- 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/1823722 Title: keyboard shortcuts are displayed not translated Status in Ubuntu Translations: New Status in language-support-translations-fr package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: Can't translate some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1827189] [NEW] Emacs/Gnus expects movemail in the wrong location
Public bug reported: After upgrading from cosmic to disco, Emacs/Gnus would no longer retrieve new mails; at Gnus startup I would get this error message: Mail source (directory :path "~/Mail/spool" :suffix ".spool") error (Searching for program). Continue? (yes or no) The actual error message could be found in the *Message* buffer, and fails because Gnus expected movemail at /usr/lib/emacs/26.1/, which had 2 problems: 1. Movemail is in the mailutils which was not installed (not a dependency) 2. After installing the mailutils package, movemail is in /usr/bin/movemail, so had to (setq mail-source-movemail-program "/usr/bin/movemail") in .gnus.el This resolves the issues which seem to have been caused by emacs no longer providing its own movemail? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: emacs 1:26.1+1-3.2ubuntu2 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: i3 Date: Wed May 1 12:20:42 2019 InstallationDate: Installed on 2019-02-26 (63 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco emacs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1827189 Title: Emacs/Gnus expects movemail in the wrong location Status in emacs package in Ubuntu: New Bug description: After upgrading from cosmic to disco, Emacs/Gnus would no longer retrieve new mails; at Gnus startup I would get this error message: Mail source (directory :path "~/Mail/spool" :suffix ".spool") error (Searching for program). Continue? (yes or no) The actual error message could be found in the *Message* buffer, and fails because Gnus expected movemail at /usr/lib/emacs/26.1/, which had 2 problems: 1. Movemail is in the mailutils which was not installed (not a dependency) 2. After installing the mailutils package, movemail is in /usr/bin/movemail, so had to (setq mail-source-movemail-program "/usr/bin/movemail") in .gnus.el This resolves the issues which seem to have been caused by emacs no longer providing its own movemail? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: emacs 1:26.1+1-3.2ubuntu2 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: i3 Date: Wed May 1 12:20:42 2019 InstallationDate: Installed on 2019-02-26 (63 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1827189/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Hi, Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the launcher) I don't know if this could means something dangerous in Wayland. https://bazaar.launchpad.net/~costales/gui-ufw/wayland/revision/19 Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in HPLIP: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago)
[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor
** Changed in: gnome-system-monitor (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: Invalid Status in libgtop2 package in Ubuntu: Fix Released Status in libgtop2 source package in Bionic: Fix Released Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+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 1800465] Re: Vulkan error when using NVIDIA-Prime
Same bug here on two different laptop. Fresh install Ubuntu 18.04.2 nvidia-driver-418 4.18.0-18-generic First $vulkaninfo => OK Switch on Intel with NVIDIA X Server settings reboot Switch to NVIDIA with NVIDIA X Server settings reboot $vulkaninfo => VK_ERROR_INITIALIZATION_FAILED $sudo vulkaninfo => OK then vulkaninfo => OK So now before launch Steam to play games that use vulkan I always do sudo vulkaninfo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+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
this bug needs SRUifying too please ** Changed in: gnome-shell (Ubuntu Disco) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Disco) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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: In Progress Status in gnome-shell source package in Disco: In Progress Status in gnome-shell source package in Eoan: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+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
Re: [Desktop-packages] [Bug 1816231] Re: There is regular screen flickering/flashing (when the mouse isn't moving)
Hey, I managed to modeset i915=0 and that seemed to stop the flickering. But now the display is at 800X600 resolution and there is no other option to change to. On Wed, May 1, 2019 at 7:50 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > The file 'journal.txt' is created in the current directory when you run: > > journalctl -b0 > journal.txt > > But if you have successfully removed 'xserver-xorg-video-intel' then you > may not need to do anything more. Did that fix it? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816231 > > Title: > There is regular screen flickering/flashing (when the mouse isn't > moving) > > Status in xserver-xorg-video-intel package in Ubuntu: > Incomplete > > Bug description: > I have installed the 18.04.2 lts version. I have a basic intel graphics > card > It says unable to locate package pkgname when I type apt-cache policy > pkgname. I think it's a problem with the xorg file. not sure. > When the mouse tracker is moving there does'nt seem to be a problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-15-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Feb 16 18:06:57 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] > InstallationDate: Installed on 2019-02-16 (0 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > MachineType: ASUSTeK COMPUTER INC. X555LAB > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic > root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/19/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X555LAB.303 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X555LAB > 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.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: X > dmi.product.name: X555LAB > dmi.product.sku: ASUS-NotebookSKU > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1816231/+subscriptions > -- *Azhar* -- 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/1816231 Title: There is regular screen flickering/flashing (when the mouse isn't moving) Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I have installed the 18.04.2 lts version. I have a basic intel graphics card It says unable to locate package pkgname when I type apt-cache policy pkgname. I think it's a problem with the xorg file. not sure. When the mouse tracker is moving there does'nt seem to be a problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 18:06:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (r
[Desktop-packages] [Bug 1827194] [NEW] Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Public bug reported: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Description changed: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. - This problem has been in Totem in for the past several versions of - Ubuntu, but in 19.04 the problem has slightly changed: Totem used to - become completely unresponsive and you had to force quit it, but in - 19.04 you can click the close button and it closes immediately. Other - than that, the problem is the same: all you get is a frozen black - screen. + This problem has been in Totem for the past several versions of Ubuntu, + but in 19.04 the problem has slightly changed: Totem used to become + completely unresponsive and you had to force quit it, but in 19.04 you + can click the close button and it closes immediately. Other than that, + the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Summary changed: - Loading a subtitled mkv file while already playing a subtitled mvk file makes the UI freeze + Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze -- 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/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: New Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Othe
[Desktop-packages] [Bug 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
This bug happens dozens of times a day after I upgrade to ubuntu19.04. Please do not let this bug to expire. -- 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/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Incomplete Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI 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/pulseaudio/+bug/1805077/+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 1826037] Re: Ubuntu Dock can't be transparent
** Description changed: - After community changes in GNOME shell the Ubuntu Dock can't be transparent now, discussion here: + After community changes in GNOME shell the Ubuntu Dock can't be transparent now (gsettings transparency-mode 'DYNAMIC') , discussion here: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/376 It's looks like, the transparent for controls in gnome shell (top bar,right menu) it must be managed by extension -- 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/1826037 Title: Ubuntu Dock can't be transparent Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After community changes in GNOME shell the Ubuntu Dock can't be transparent now (gsettings transparency-mode 'DYNAMIC') , discussion here: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/376 It's looks like, the transparent for controls in gnome shell (top bar,right menu) it must be managed by extension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1826037/+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 1808420] Re: gnome-system-monitor from Snap does not hide /dev/loop* mounts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1808420 Title: gnome-system-monitor from Snap does not hide /dev/loop* mounts Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: The gnome-system-monitor package preinstalled with Ubuntu 18.04 appears to have a problem with excluding /dev/loop* mounts from the File System tab. Attached is a screenshot of what it shows on my system. As you can see, there's a lot of /dev/loop* entries, and a lot of duplication of available disk space percentage. This is a pastebin of $ mount: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8101140k,nr_inodes=2025285,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627500k,mode=755) /dev/nvme0n1p3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22759) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) /var/lib/snapd/snaps/gnome-3-26-1604_74.snap on /snap/gnome-3-26-1604/74 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/telegram-desktop_384.snap on /snap/telegram-desktop/384 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-3-26-1604_70.snap on /snap/gnome-3-26-1604/70 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-calculator_180.snap on /snap/gnome-calculator/180 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_6034.snap on /snap/core/6034 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-calculator_238.snap on /snap/gnome-calculator/238 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/skype_63.snap on /snap/skype/63 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-characters_103.snap on /snap/gnome-characters/103 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_5897.snap on /snap/core/5897 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-characters_139.snap on /snap/gnome-characters/139 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-system-monitor_57.snap on /snap/gnome-system-monitor/57 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-system-monitor_51.snap on /snap/gnome-system-monitor/51 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/telegram-desktop_291.snap on /snap/telegra
[Desktop-packages] [Bug 1808420] Re: gnome-system-monitor from Snap does not hide /dev/loop* mounts
** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1808420 Title: gnome-system-monitor from Snap does not hide /dev/loop* mounts Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: The gnome-system-monitor package preinstalled with Ubuntu 18.04 appears to have a problem with excluding /dev/loop* mounts from the File System tab. Attached is a screenshot of what it shows on my system. As you can see, there's a lot of /dev/loop* entries, and a lot of duplication of available disk space percentage. This is a pastebin of $ mount: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8101140k,nr_inodes=2025285,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627500k,mode=755) /dev/nvme0n1p3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22759) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) /var/lib/snapd/snaps/gnome-3-26-1604_74.snap on /snap/gnome-3-26-1604/74 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/telegram-desktop_384.snap on /snap/telegram-desktop/384 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-3-26-1604_70.snap on /snap/gnome-3-26-1604/70 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-calculator_180.snap on /snap/gnome-calculator/180 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_6034.snap on /snap/core/6034 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-calculator_238.snap on /snap/gnome-calculator/238 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/skype_63.snap on /snap/skype/63 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-characters_103.snap on /snap/gnome-characters/103 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_5897.snap on /snap/core/5897 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-characters_139.snap on /snap/gnome-characters/139 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-system-monitor_57.snap on /snap/gnome-system-monitor/57 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/gnome-system-monitor_51.snap on /snap/gnome-system-monitor/51 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/telegram-desktop_291.snap on /snap/telegram-desktop/291 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/skype_66.snap on /snap/skype/66 type squashfs
[Desktop-packages] [Bug 1827199] [NEW] firefox menu font can not set by gnome tweak 3.32.0
Public bug reported: I use ubuntu19.04, gnome 3.32.1, gnome tweak version 3.32.0, firefox version 66.0.3 In ubuntu18.04, firefox menu font can be set by gnome-tweak, but in ubuntu19.04 firefox menu font can not set by gnome tweak now.(The default menu font for firefox is too big and ugly I think) I don't know how to set firefox menu font now. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1827199 Title: firefox menu font can not set by gnome tweak 3.32.0 Status in firefox package in Ubuntu: New Bug description: I use ubuntu19.04, gnome 3.32.1, gnome tweak version 3.32.0, firefox version 66.0.3 In ubuntu18.04, firefox menu font can be set by gnome-tweak, but in ubuntu19.04 firefox menu font can not set by gnome tweak now.(The default menu font for firefox is too big and ugly I think) I don't know how to set firefox menu font now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827199/+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 1826936] Re: Upgrade to 3.32.1 and SRU it
This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1 --- gnome-shell (3.32.1-1ubuntu1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with debian - Update to 3.32.1 upstream version (LP: #1826936) - Fixes Icon disappears from favorites (LP: #1822846) - Fix applications aren't focused in Wayland session (LP: #1826176) remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Handle the no-monitor case (LP: #1826797) [ Andrea Azzarone ] * d/p/volume-Add-back-sound-feedback-on-scroll.patch: Add missing import gnome-shell (3.32.1-1) experimental; urgency=medium [ Simon McVittie ] * d/rules: Create a temporary HOME, XDG_RUNTIME_DIR for the unit tests. This goes some way towards fixing test failures and FTBFS on buster's sbuild, as deployed on the s390x buildd. * d/.gitignore: Add [ Laurent Bigonville ] * New upstream release -- Marco Trevisan (Treviño) Wed, 01 May 2019 10:23:16 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826936 Title: Upgrade to 3.32.1 and SRU it 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: Confirmed Status in mutter source package in Disco: Confirmed Bug description: [ Description ] The first stable release in the 3.32 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. There are new fixes related to startup notifications and an X11 crash fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bu
[Desktop-packages] [Bug 1826176] Re: Applications do not receive focus in Wayland sessions
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
--
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/1826176
Title:
Applications do not receive focus in Wayland sessions
Status in GNOME Shell:
Fix Released
Status in Mutter:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
On a fresh install of Ubuntu 19.04 applications that are started from the
dash inside a Wayland session often do not receive focus.
The behavior is inconsistent. Some applications (like the terminal) always
properly get the focus. Some like GEdit en Chromium mostly do not receive focus
until suddenly they do. It seems to depend on other applications that are
already open and may have the focus but I could not discover the exact pattern.
Once clicked or Alt-tabbed into the applications work as expected. But
when you simply start typing after opening, for example, GEdit the
keystrokes may go to an application window that has just been obscured
buy the newly opened one.
This bug is similar to bug 1817924 but that one apparently is limited
to X sessions.
[ QA ]
No further verification as this is a fix coming with a GNOME micro
release update that is covered by this exception
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
ProblemType: BugDistroRelease: 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: Wed Apr 24 11:43:33 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-04-24 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64
(20190416)SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1826176/+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 1826182] Re: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
** Changed in: mutter (Ubuntu Eoan)
Status: In Progress => Fix Released
--
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/1826182
Title:
[DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a
dock with a monitor
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Disco:
In Progress
Status in mutter source package in Eoan:
Fix Released
Bug description:
[ Description ]
Ubuntu 19.04
DisplayLink properietary driver installed.
Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB
dock with one monitor connected.
What happens: The desktop session shuts down and throws me back into
the login screen, where Wayland sessions are no longer available.
What I would expect: the new monitor is taken into use and the desktop
session continues normally.
Installed: libmutter-4-0 3.32.0+git20190410-1ubuntu1
This issue is already fixed upstream:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/521
The fix has been released as part of mutter 3.32.1.
I would hope the mutter package would be updated to the new upstream
point release.
[ QA ]
No further verification as this is a fix coming with a GNOME micro
release update that is covered by this exception
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826182/+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 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1 --- gnome-shell (3.32.1-1ubuntu1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with debian - Update to 3.32.1 upstream version (LP: #1826936) - Fixes Icon disappears from favorites (LP: #1822846) - Fix applications aren't focused in Wayland session (LP: #1826176) remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Handle the no-monitor case (LP: #1826797) [ Andrea Azzarone ] * d/p/volume-Add-back-sound-feedback-on-scroll.patch: Add missing import gnome-shell (3.32.1-1) experimental; urgency=medium [ Simon McVittie ] * d/rules: Create a temporary HOME, XDG_RUNTIME_DIR for the unit tests. This goes some way towards fixing test failures and FTBFS on buster's sbuild, as deployed on the s390x buildd. * d/.gitignore: Add [ Laurent Bigonville ] * New upstream release -- Marco Trevisan (Treviño) Wed, 01 May 2019 10:23:16 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: In Progress Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@reso
[Desktop-packages] [Bug 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)
This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1 --- gnome-shell (3.32.1-1ubuntu1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with debian - Update to 3.32.1 upstream version (LP: #1826936) - Fixes Icon disappears from favorites (LP: #1822846) - Fix applications aren't focused in Wayland session (LP: #1826176) remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Handle the no-monitor case (LP: #1826797) [ Andrea Azzarone ] * d/p/volume-Add-back-sound-feedback-on-scroll.patch: Add missing import gnome-shell (3.32.1-1) experimental; urgency=medium [ Simon McVittie ] * d/rules: Create a temporary HOME, XDG_RUNTIME_DIR for the unit tests. This goes some way towards fixing test failures and FTBFS on buster's sbuild, as deployed on the s390x buildd. * d/.gitignore: Add [ Laurent Bigonville ] * New upstream release -- Marco Trevisan (Treviño) Wed, 01 May 2019 10:23:16 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: In Progress Bug description: [ Impact ] From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. [ QA ] No further verification as this is a fix coming with a GNOME micro release update that is covered by this exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME --- ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 Appor
[Desktop-packages] [Bug 1826176] Re: Applications do not receive focus in Wayland sessions
This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1 --- gnome-shell (3.32.1-1ubuntu1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with debian - Update to 3.32.1 upstream version (LP: #1826936) - Fixes Icon disappears from favorites (LP: #1822846) - Fix applications aren't focused in Wayland session (LP: #1826176) remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Handle the no-monitor case (LP: #1826797) [ Andrea Azzarone ] * d/p/volume-Add-back-sound-feedback-on-scroll.patch: Add missing import gnome-shell (3.32.1-1) experimental; urgency=medium [ Simon McVittie ] * d/rules: Create a temporary HOME, XDG_RUNTIME_DIR for the unit tests. This goes some way towards fixing test failures and FTBFS on buster's sbuild, as deployed on the s390x buildd. * d/.gitignore: Add [ Laurent Bigonville ] * New upstream release -- Marco Trevisan (Treviño) Wed, 01 May 2019 10:23:16 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826176 Title: Applications do not receive focus in Wayland sessions Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as ex
[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
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
** Changed in: mutter (Ubuntu Eoan)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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:
In Progress
Status in mutter package in Ubuntu:
Fix Released
Status in gnome-shell source package in Disco:
In Progress
Status in mutter source package in Disco:
In Progress
Status in gnome-shell source package in Eoan:
In Progress
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 1823722] Re: keyboard shortcuts are displayed not translated
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
--
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/1823722
Title:
keyboard shortcuts are displayed not translated
Status in Ubuntu Translations:
New
Status in language-support-translations-fr package in Ubuntu:
New
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Can't translate some keyboard shortcuts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1826936] Re: Upgrade to 3.32.1 and SRU it
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
--
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/1826936
Title:
Upgrade to 3.32.1 and SRU it
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:
Confirmed
Status in mutter source package in Disco:
Confirmed
Bug description:
[ Description ]
The first stable release in the 3.32 series.
[ QA ]
Run Ubuntu session, expect the shell to work normally with various
setups
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
[ Regresison potential ]
Most of commits were already included in stable ubuntu release, as per
git snapshot. There are new fixes related to startup notifications and
an X11 crash fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826936/+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 1827207] [NEW] [SRU] 0.56.2
Public bug reported: [ Description ] Upstream point release, uploaded under the GNOME MRE. This is a crash fix (see the linked Red Hat bug). commit 9a079492ea698f573dfc7129f1c79e4a865803b4 Author: Christian Persch Date: Sat Apr 20 19:41:46 2019 +0200 parser: glue: Correct parameter collection If the minimum value is greater than the maximum_value (which can happen e.g. when the minimum is 1 and the maximum is m_column_count - cursor.column), the parameter collection should return the minimum value, not the maximum value. (cherry picked from commit 8afa5e46905492779027ed2c04e8a63e30cd74df) src/parser-glue.hh | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) commit d08b9d0e4c3dbca586496d1807da9b430de0aadc Author: Christian Persch Date: Sat Apr 20 19:41:46 2019 +0200 Revert "parser: glue: Use std::clamp" This reverts commit 1a84c427cd2ea05939b86eb47c21a437d0ce6d79. https://bugzilla.redhat.com/show_bug.cgi?id=1701590 (cherry picked from commit d4da2ac7417c710bc7e9824062ab09d1187e815a) src/parser-glue.hh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) [ QA ] Test various terminal emulators, e.g. GNOME terminal, MATE terminal, and tilix. Make sure they all still work properly - e.g. multi window, multi tab, running commands, ... [ Regression potential ] It's reverting a commit back to the state the code had previously, so this doesn't feel very risky. If it's bad then the worst thing that could happen is that anything using Vte breaks. ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: vte2.91 (Ubuntu Disco) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: vte2.91 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: vte2.91 (Ubuntu) Status: New => Fix Released ** Changed in: vte2.91 (Ubuntu Disco) Status: New => In Progress ** Changed in: vte2.91 (Ubuntu Disco) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1827207 Title: [SRU] 0.56.2 Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Disco: In Progress Bug description: [ Description ] Upstream point release, uploaded under the GNOME MRE. This is a crash fix (see the linked Red Hat bug). commit 9a079492ea698f573dfc7129f1c79e4a865803b4 Author: Christian Persch Date: Sat Apr 20 19:41:46 2019 +0200 parser: glue: Correct parameter collection If the minimum value is greater than the maximum_value (which can happen e.g. when the minimum is 1 and the maximum is m_column_count - cursor.column), the parameter collection should return the minimum value, not the maximum value. (cherry picked from commit 8afa5e46905492779027ed2c04e8a63e30cd74df) src/parser-glue.hh | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) commit d08b9d0e4c3dbca586496d1807da9b430de0aadc Author: Christian Persch Date: Sat Apr 20 19:41:46 2019 +0200 Revert "parser: glue: Use std::clamp" This reverts commit 1a84c427cd2ea05939b86eb47c21a437d0ce6d79. https://bugzilla.redhat.com/show_bug.cgi?id=1701590 (cherry picked from commit d4da2ac7417c710bc7e9824062ab09d1187e815a) src/parser-glue.hh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) [ QA ] Test various terminal emulators, e.g. GNOME terminal, MATE terminal, and tilix. Make sure they all still work properly - e.g. multi window, multi tab, running commands, ... [ Regression potential ] It's reverting a commit back to the state the code had previously, so this doesn't feel very risky. If it's bad then the worst thing that could happen is that anything using Vte breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1827207/+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 1826874] Re: In Ubuntu's Thunderbird, Empty Deleted warns, Empty "Inbox"!
** Changed in: thunderbird (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1826874 Title: In Ubuntu's Thunderbird, Empty Deleted warns, Empty "Inbox"! Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: Issue: In Ubuntu desktop 18.10 and 19.04 (and perhaps years earlier?), when a Thunderbird user clicks on File>Empty Deleted, it warns that Empty "Inbox" will be done, instead! Ouch! (It does empty the correct folder anyway, but this should and does scare many users.) After a protracted dialog with the Mozilla Thunderbird support team, I've learned that Mozilla's own vanilla Thunderbird shows Empty "Trash", as it should. They say that the version of Thunderbird that comes bundled with Ubuntu is to blame - so please fix it. Note 1: Specifically, this wrong routine threatens to empty the active folder; commonly, that folder is "Inbox". Note 2: There's no prompt at all, if the "Trash" dialog box is suppressed. But default is (and should be) to have it enabled. Note 3: You can view the details of my Mozilla trouble-shooting (including my/Ubuntu's erroneous Thunderbird screen-print and Mozilla's correct one), here: https://support.mozilla.org/en-US/questions/1254659#answer-1216735 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1826874/+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 1822062] Re: Race condition on boot between cups and sssd
Sponsored for 'Eoan'. Let's start the SRU once cups land in eoan- releases (Fix Released). Thanks Victor ! - Eric ** Changed in: cups (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: cups (Ubuntu Disco) Status: New => In Progress ** Changed in: cups (Ubuntu Cosmic) Status: New => In Progress ** Changed in: cups (Ubuntu Bionic) Status: New => In Progress ** Changed in: cups (Ubuntu Xenial) Status: New => In Progress -- 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/1822062 Title: Race condition on boot between cups and sssd Status in cups package in Ubuntu: Fix Committed Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups source package in Eoan: Fix Committed Bug description: [Impact] * When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. * The patch adds an "After=sssd.service" clause to the service unit file. [Test Case] * Configure an external authentication service (LDAP, AD...) and create a group, for instance "lpadmins@tests.local" * Set SystemGroup to match that group in /etc/cups/cups-files.conf: SystemGroup lpadmins@tests.local * Reboot * If cups has started before sssd has finished booting, cups will crash: Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. * If cups starts after sssd, it will work fine. [Regression Potential] * Minimal: this patch affects just the ordering of the service unit file. [Other Info] * Upstream: https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d [Original description] When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. For instance, with a group named lpadmins@tests.local served from Active Directory through sssd, if the sssd service hasn't booted before cups: Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read "/etc/cups/cups-files.conf" due to errors. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 'exit-code'. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time over, scheduling restart. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, restart counter is at 2. Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers available locally... Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler. If sssd is running before cups starts, everything works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1825513] Re: High CPU usage when large document open
Further testing has revealed the issue to lie with a LibreOffice grammar extension called LanguageTool. This is a known issue in LanguageTool and removing the extension resolved the issue. See this bug in the LangugeTool bug tracker: https://github.com /languagetool-org/languagetool/issues/1217?_pjax=%23js-repo-pjax- container ** Bug watch added: github.com/languagetool-org/languagetool/issues #1217 https://github.com/languagetool-org/languagetool/issues/1217 -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: New Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1825513] Re: High CPU usage when large document open
Hmmm, after some digging into this issue with Tim, we may have uncovered the culprit. It looks like the 'LanguageTool' LibreOffice extension is causing the high CPU load, not LibreOffice itself. When installed, opening a large document will send LibreOffice's CPU usage skyrocketing. After a few minutes (depending on the size of the document), the usage does eventually drop back down below 5% again. When uninstalled, opening a large document inhibits a short spike in CPU usage, but quickly drops off. Tim, would you mind filing an upstream bug report for this at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and sharing the link to that bug here? For the Component field, select "Extensions". Thank you! -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: New Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1825513] Re: High CPU usage when large document open
Hmmm, after some digging into this issue with Tim, we may have uncovered the culprit. It looks like the 'LanguageTool' LibreOffice extension is causing the high CPU load, not LibreOffice itself. When installed, opening a large document will send LibreOffice's CPU usage skyrocketing. After a few minutes (depending on the size of the document), the usage does eventually drop back down below 5% again. When uninstalled, opening a large document inhibits a short spike in CPU usage, but quickly drops off. LangugeTool bug report: https://github.com/languagetool- org/languagetool/issues/1217?_pjax=%23js-repo-pjax-container ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Won't Fix -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: New Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1825513] Re: High CPU usage when large document open
Upstream bug reported here: https://bugs.documentfoundation.org/show_bug.cgi?id=125061 ** Bug watch added: Document Foundation Bugzilla #125061 https://bugs.documentfoundation.org/show_bug.cgi?id=125061 -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: New Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1823722] Re: keyboard shortcuts are displayed not translated
On 2019-05-01 11:13, Iain Lane wrote: > Gunnar / Marco, could one of you please SRUify this bug? It's going > to be included in the upload (backport from eoan). Not sure how those translations would be brought to the users. The strings from the XML files are now back in eoan: https://translations.launchpad.net/ubuntu/eoan/+source/mutter/+pots/mutter/fr and the translations will be included in the language packs for eoan once they are built. A SRU build will bring the strings to LP for disco too, but there is no plan AFAIK to accomplish a language pack update for disco. It means that the bug won't really be fixed for disco. Maybe it would be better to drop the reference to this bug from the changelog when uploading to disco? (I see that it's in the queue already, so I guess I suggest another modified upload.) -- 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/1823722 Title: keyboard shortcuts are displayed not translated Status in Ubuntu Translations: New Status in language-support-translations-fr package in Ubuntu: New Status in mutter package in Ubuntu: Fix Released Bug description: Can't translate some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1744619] Re: Transitioning GNOME away from libnm-glib
** Branch linked: lp:~khurshid-alam/unity-settings-daemon/libnm-port ** Branch linked: lp:~khurshid-alam/unity-control-center/libnm-port -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1744619 Title: Transitioning GNOME away from libnm-glib Status in network-manager-iodine package in Ubuntu: Fix Released Status in network-manager-l2tp package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Fix Released Status in network-manager-vpnc package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: Debian has dropped libnm-glib support from most of its VPN plugins. We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome- shell to properly interact with VPNs. unity-control-center will need to be ported away from libnm-glib for it to display VPNs. The only other known affected desktop is Cinnamon which has fixes "pending" Here's the Debian transition bug: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm At first look, KDE Plasma did not seem to be hurt by the libnm-glib support removal, but Kubuntu should probably check more closely. I am filing this bug to coordinate this transition and keep the VPN plugins in -proposed until we at least update gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-iodine/+bug/1744619/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Do we need a new rebuild of gvfs in bionic or did the 1.36.1-0ubuntu1.3 update pick up the samba change when it was built? Using samba 4.7.6+dfsg~ubuntu-0ubuntu2.9, I rebuilt gvfs 1.36.1-0ubuntu1.3 locally. I then restarted gvfsd-smb-browse without success.. killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse still nothing in Network neighbourhood.. and no sign of "smb-network: Forcing NT1 protocol version" in the output. I then killed the file manager and gvfsd-smb-browse, and typed: pkill gvfs GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse I restarted the file manager and this time, I could see "smb-network: Forcing NT1 protocol version" and Workgroup when browsing network:///. What I don't understand though, is that after each new reboot, with this locally built gvfs installed, I end up not seeing workgroup within network:///, nor "smb-network: Forcing NT1 protocol version" in the gvfsd-smb-browse output until after I pkill gvfs. Going back to the repository version of gvfs, and I can't see workgroup, nor "smb-network: Forcing NT1 protocol version" anymore, even after "pkill gvfs". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Triaged Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Triaged Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can
[Desktop-packages] [Bug 1823722] Re: keyboard shortcuts are displayed not translated
It'd be easier for me if the change could be accepted, even if it has no functional impact (that makes the SRU a straight backport). So to that end it'd be good to reassure the SRU team that this won't break anything. -- 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/1823722 Title: keyboard shortcuts are displayed not translated Status in Ubuntu Translations: New Status in language-support-translations-fr package in Ubuntu: New Status in mutter package in Ubuntu: Fix Released Bug description: Can't translate some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1827219] [NEW] package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134
Public bug reported: Upgrading from 14.04 to 16.04 got the error at install time and then after restart ProblemType: Package DistroRelease: Ubuntu 16.04 Package: upower 0.99.4-2ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177 Uname: Linux 4.4.0-147-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Wed May 1 13:22:28 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 134 InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: upower Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 UpgradeStatus: Upgraded to xenial on 2019-05-01 (0 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1827219 Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 Status in upower package in Ubuntu: New Bug description: Upgrading from 14.04 to 16.04 got the error at install time and then after restart ProblemType: Package DistroRelease: Ubuntu 16.04 Package: upower 0.99.4-2ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177 Uname: Linux 4.4.0-147-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Wed May 1 13:22:28 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 134 InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: upower Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 UpgradeStatus: Upgraded to xenial on 2019-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827219/+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 1827219] Re: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134
** Tags removed: need-duplicate-check -- 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/1827219 Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 Status in upower package in Ubuntu: New Bug description: Upgrading from 14.04 to 16.04 got the error at install time and then after restart ProblemType: Package DistroRelease: Ubuntu 16.04 Package: upower 0.99.4-2ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177 Uname: Linux 4.4.0-147-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Wed May 1 13:22:28 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 134 InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: upower Title: package upower 0.99.4-2ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 UpgradeStatus: Upgraded to xenial on 2019-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827219/+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 1827235] [NEW] Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS
Public bug reported: Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et reste figé sur les points sous le logo Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 1 17:30:47 2019 DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2019-04-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed May 1 17:26:15 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 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/1827235 Title: Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS Status in xorg package in Ubuntu: New Bug description: Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et reste figé sur les points sous le logo Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 1 17:30:47 2019 DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2019-04-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.
[Desktop-packages] [Bug 1823722] Re: keyboard shortcuts are displayed not translated
Ok, I "SRUified" it. Dropped the Ubuntu MP too. ** Description changed: + [Impact] + + Navigation shortcuts are untranslated in g-c-c. Those strings come from + mutter, and they were discarded when the translation template was + created at build time due to a missing build-depend. That build-depend + is included in the new disco upload. + + [Test Case] + + Visit this page: + + https://translations.launchpad.net/ubuntu/disco/+source/mutter/+pots/mutter/fr + + and confirm that strings from data/50-mutter-navigation.xml are shown. + + [Regression Potential] + + None. + + [Original description] + Can't translate some keyboard shortcuts ** No longer affects: language-support-translations-fr (Ubuntu) ** Also affects: mutter (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Disco) Status: New => In Progress -- 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/1823722 Title: keyboard shortcuts are displayed not translated Status in Ubuntu Translations: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: In Progress Bug description: [Impact] Navigation shortcuts are untranslated in g-c-c. Those strings come from mutter, and they were discarded when the translation template was created at build time due to a missing build-depend. That build-depend is included in the new disco upload. [Test Case] Visit this page: https://translations.launchpad.net/ubuntu/disco/+source/mutter/+pots/mutter/fr and confirm that strings from data/50-mutter-navigation.xml are shown. [Regression Potential] None. [Original description] Can't translate some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/d
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs] Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Just testing Disco and wanted to see what login options are available after adding 'gnome-shell-extensions' and found that logging out lands me on a black screen that's unresponsive to any keyboard input. I'll test on some slightly different hardware soon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 16:18:56 2019 InstallationDate: Installed on 2019-04-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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) mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+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 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/d
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs] Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Just testing Disco and wanted to see what login options are available after adding 'gnome-shell-extensions' and found that logging out lands me on a black screen that's unresponsive to any keyboard input. I'll test on some slightly different hardware soon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 16:18:56 2019 InstallationDate: Installed on 2019-04-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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) mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+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 1826468]
I confirm it is fixed in 版本: 6.3.0.0.alpha0+ Build ID: 1ae5ca077119982ae83833871326c86d9930ae11 CPU 线程: 4; 操作系统: Linux 4.18; UI 渲染: 默认; VCL: gtk3; 区域语言: zh-CN (zh_CN.UTF-8); UI 语言: zh-CN Calc: threaded -- 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/1826468 Title: [upstream] Libreoffice Calc cannot export PDF to a network drive Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Triaged Bug description: After upgrading from 18.10 to 19.04 I lost possibility to export a document to PDF, if a document is on a network drive (it's a DAVS network folder in my case). I receive a pop-up windows about general I/O error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 23:35:20 2019 InstallationDate: Installed on 2018-05-05 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1826468/+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 1631246] Re: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também e
** Tags added: cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631246 Title: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit- options.d/api.twitter.com.conf', que também está no pacote account- plugin-twitter 0.12+16.04.20160126-0ubuntu1 Status in One Hundred Papercuts: Confirmed Status in account-plugins package in Ubuntu: Confirmed Status in kaccounts-providers package in Ubuntu: Confirmed Bug description: Error during installation of KDE Plasma on Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 7 01:55:46 2016 ErrorMessage: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-09-11 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1631246/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
A new rebuild is needed. To verify in another way, check the Depends line of the gvfs-backends package: $ dpkg -s gvfs-backends|grep Depends|grep smbclient Depends: libarchive13 (>= 3.0.4), , libsmbclient (>= 2:4.0.3+dfsg1) versus $ dpkg -s gvfs-backends|grep Depends|grep smbclient Depends: libarchive13 (>= 3.0.4), , libsmbclient (>= 2:4.7.6+dfsg~ubuntu-0ubuntu2.8~) It must require a newer libsmbclient like in the second case above. The old windows network is a bit brittle. Elections need to take place, a master browser has to be elected, etc. Even getting a name can take a while, as the network needs to be checked for collisions. Usually it's a matter of time until the computers show up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Triaged Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Triaged Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in s
[Desktop-packages] [Bug 1825513]
Further testing has revealed the issue to lie with a LibreOffice grammar extension called LanguageTool. This is a known issue in LanguageTool and removing the extension resolved the issue. See this bug in the LangugeTool bug tracker: https://github.com /languagetool-org/languagetool/issues/1217?_pjax=%23js-repo-pjax- container -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1825513] Re: High CPU usage when large document open
** Changed in: df-libreoffice Status: New => Won't Fix -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Won't Fix Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-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 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
yparitcher, thank you for the upstream bug report. As soon as upstream finds a (backportable) solution we will add it to this SRU and report back here. ** Changed in: modemmanager (Ubuntu Bionic) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Confirmed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Regarding apache2, https://bz.apache.org/bugzilla/show_bug.cgi?id=57471 is still open, and I just tried a 2.4.38 build with pcre2, and it doesn't work. Switching the task back to incomplete according to the bug instructions. ** Changed in: apache2 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Incomplete Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
costales writes: > Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the > launcher) > I don't know if this could means something dangerous in Wayland. I'm not sure if it will fix things run as root via pkexec but it will if you manually run gui programs as root. There's no risk involved since root can already do anything anyhow, including debug the X server and force it to let them connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in HPLIP: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generi
[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
The situation with apache2 is what I documented in https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9: “But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570” trunk is the 2.5.x branch, not 2.4.x. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Incomplete Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Thanks for the update, I missed that comment (again). I guess it can be moved back to "triaged" then. ** Changed in: apache2 (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which states: * [92175749] Revert "Switch from the deprecated libpcre3 to the newer (!) libpcre2." libpcre2 is not a drop-in replacement and not detected by zsh's configure script. (Closes: #909084, reopens LP#1792544) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1822062] Re: Race condition on boot between cups and sssd
This bug was fixed in the package cups - 2.2.10-6ubuntu1 --- cups (2.2.10-6ubuntu1) eoan; urgency=medium * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if installed (LP: #1822062) -- Victor Tapia Wed, 24 Apr 2019 17:04:55 +0200 ** Changed in: cups (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1822062 Title: Race condition on boot between cups and sssd Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups source package in Eoan: Fix Released Bug description: [Impact] * When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. * The patch adds an "After=sssd.service" clause to the service unit file. [Test Case] * Configure an external authentication service (LDAP, AD...) and create a group, for instance "lpadmins@tests.local" * Set SystemGroup to match that group in /etc/cups/cups-files.conf: SystemGroup lpadmins@tests.local * Reboot * If cups has started before sssd has finished booting, cups will crash: Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. * If cups starts after sssd, it will work fine. [Regression Potential] * Minimal: this patch affects just the ordering of the service unit file. [Other Info] * Upstream: https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d [Original description] When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. For instance, with a group named lpadmins@tests.local served from Active Directory through sssd, if the sssd service hasn't booted before cups: Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read "/etc/cups/cups-files.conf" due to errors. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 'exit-code'. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time over, scheduling restart. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, restart counter is at 2. Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers available locally... Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler. If sssd is running before cups starts, everything works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1827284] [NEW] No animation when GNOME Activities overview is opened
Public bug reported: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "The bug" https://bugs.launchpad.net/bugs/1827284/+attachment/5260585/+files/Screencap.webm -- 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/1827284 Title: No animation when GNOME Activities overview is opened Status in gnome-shell package in Ubuntu: New Bug description: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827284/+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 1827295] Re: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed()
*** This bug is a duplicate of bug 1795372 *** https://bugs.launchpad.net/bugs/1795372 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1795372, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1827295/+attachment/5260611/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260613/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260616/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260617/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260618/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260619/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1827295/+attachment/5260620/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1795372 gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827295 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() Status in gnome-control-center package in Ubuntu: New Bug description: Similar bugs were reported in the past, but were either marked fixed or closed invalid (those I got to see), so I'll report a new one. This crash occurred while I deleted a USB (tethering) network connection profile on Settings -> Network on Ubuntu 18.04.2 (used ~ daily, upgraded from 16.04 about half a year ago). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 2 01:19:17 2019 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55f2c522b723 : jmpq *0xc0(%rax) PC (0x55f2c522b723) ok source "*0xc0(%rax)" ok SP (0x7fffd591fd58) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: net_device_simple_get_speed () () g_cclosure_marshal_VOID__BOOLEANv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827295/+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 1795372] Re: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed()
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795372 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Firstly, I didn't get this in 18.04, only since the upgrade to beta of 18.10 a couple of days ago. For that reason suspect not a dupe of #1735662 I was interacting with the network tab in control center *because*, since that update to Cosmic beta, I've been having an admittedly minor cosmetic problem (but one that bugs me) where the top panel network icon continues to show as being wifi after plugging into a thunderbolt 3 dock with an ethernet connection, although it only settles down to that after a minute or so of apparent indecision. The ethernet connection is *up*, but in Bionic that meant that's reliably the one that showed, correctly IMHO because that's the one with the lower routing metric, and one certainly hopes is the fastest too. In addition, potentially relevant, I see two wired connections in the network preferences, and in the "wired" part of the status menu. One for "Wired connection 1" and one with the name of my ethernet interface, which in this case, in the new style, is "enp63s0". It's the latter that seems now to get automatically selected when I plug into the dock. (The ethernet port on the TB3 dock is the *only* wired connection this laptop has ever had, and that only ever on my home network.) I can't say whether I also had two such wired connection entries before the upgrade to Cosmic, as I didn't have cause to look (the status icon always behaved as expected). Given the name of the method/function that crashed, is it possible that this is also behind the apparent indecision of the network status icon, and it often settling down on the wrong interface. After posting this bug report I will attempt to delete the wired connection called "Wired connection 1", that currently seems to be unused, and see what happens thereafter. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 11:55:55 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-11 (19 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: gnome-control-center network ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x555ef44e2043 : jmpq *0xc0(%rax) PC (0x555ef44e2043) ok source "*0xc0(%rax)" ok SP (0x7ffeff419998) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: net_device_simple_get_speed () ?? () g_cclosure_marshal_VOID__BOOLEANv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() UpgradeStatus: Upgraded to cosmic on 2018-09-29 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795372/+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 1827284] Re: No animation when GNOME Activities overview is opened
** Description changed: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. + + It's worth mentioning that the animation shows up if you access + activities through the top right hot corner, but it doesn't if you press + the button or the Windows key. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827284 Title: No animation when GNOME Activities overview is opened Status in gnome-shell package in Ubuntu: New Bug description: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. It's worth mentioning that the animation shows up if you access activities through the top right hot corner, but it doesn't if you press the button or the Windows key. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827284/+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 1827299] [NEW] incorrect statistics in nautilus
Public bug reported: I'm using UBUNTU 18.04 I have a directory with 23 sub directories and 24000 files and 93GB used. below is the output of df -h /dev/sda9 119G 89G 25G 79% /Cabs When i go and high light the 23 sub directories and get a total of the sub directories thru properties, it seem to loop an it goes thru each directory. I end up getting some value like 4000 and 24 GB. If i do the same thing on a NAS attached file system, it never stops. I get similar results in 19.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 20:31:06 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'650x567+37+120'" InstallationDate: Installed on 2019-04-22 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1827299 Title: incorrect statistics in nautilus Status in nautilus package in Ubuntu: New Bug description: I'm using UBUNTU 18.04 I have a directory with 23 sub directories and 24000 files and 93GB used. below is the output of df -h /dev/sda9 119G 89G 25G 79% /Cabs When i go and high light the 23 sub directories and get a total of the sub directories thru properties, it seem to loop an it goes thru each directory. I end up getting some value like 4000 and 24 GB. If i do the same thing on a NAS attached file system, it never stops. I get similar results in 19.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 20:31:06 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'650x567+37+120'" InstallationDate: Installed on 2019-04-22 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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/1827299/+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 1827303] [NEW] Libreoffice Snap Doesn't Display Equation Editor and Can't Type Subscript Characters?
Public bug reported: Equation editor doesn't appear in the menu bar and subscript characters (CTRL + SHIFT + B) types empty characters. Video of issue here: https://www.youtube.com/watch?v=W1mKApYZdbg&feature=youtu.be Platform: Kubuntu 19.04 Kernel: 15.0.0-13-generic ** 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/1827303 Title: Libreoffice Snap Doesn't Display Equation Editor and Can't Type Subscript Characters? Status in libreoffice package in Ubuntu: New Bug description: Equation editor doesn't appear in the menu bar and subscript characters (CTRL + SHIFT + B) types empty characters. Video of issue here: https://www.youtube.com/watch?v=W1mKApYZdbg&feature=youtu.be Platform: Kubuntu 19.04 Kernel: 15.0.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827303/+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 1740709] Re: GtkSpinButton's '+' changes width if insensitive
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: ubuntu-themes Status: New => Won't Fix ** Changed in: ubuntu-themes (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1740709 Title: GtkSpinButton's '+' changes width if insensitive Status in Ubuntu theme: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: GtkSpinButton consists of a (typically numeric) input field, followed by a '-' and finally a '+' sign. The width of the '+' sign depends on whether it's sensitive or not. It shouldn't, it should have a constant width. Happens with Ubuntu's default Ambiance and Radiance themes. Does not happen with GTK+'s default Adwaita. Example 1: Open dconf-editor and navigate to /ca/desrt/dconf- editor/demo/integer-16-unsigned. Uncheck "Use default value" and use the +/- buttons to alter the value. As it reaches 65535, that is, the '+' button becomes insensitive, its width increases. Click '-' to make the '+' sign sensitive again, its width shrinks back. Example 2: Open gnome-terminal, Edit -> Profile Preferences, Scrolling tab, toggle the checkbox in front of "Limit scrollback to" back and forth. Notice how the '+' sign keeps changing width, and the "lines" label keeps jumping back and forth accordingly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Dec 31 22:08:32 2017 InstallationDate: Installed on 2016-11-09 (416 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740709/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: New Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI 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/pulseaudio/+bug/1805077/+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 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
** Also affects: gnome-shell (Ubuntu Eoan) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: In Progress Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland events: Connection reset by peer Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: Script threw an exception ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Mon Apr 29 09:33:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (145 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826797/+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 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)
** Also affects: gnome-shell (Ubuntu Eoan) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: In Progress Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Impact ] From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. [ QA ] No further verification as this is a fix coming with a GNOME micro release update that is covered by this exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME --- ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+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 1827030] Re: Keyboard brightness control not working
@Sebastien Yes. I have one project using GNOME. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
When totem is frozen please open a terminal and run: killall -ABRT totem Now wait a while for a crash report to be written to disk. The totem window should vanish when it's done. Next, send the resulting crash report per these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: Incomplete Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1827194/+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 1827235] Re: Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS
Please: 1. Reproduce the problem. Wait a minute or two and then turn the power off. 2. Turn the power on again. 3. Run this command: journalctl -b-1 > prevboot.txt and then send us the resulting file 'prevboot.txt'. ** 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/1827235 Title: Ordinateur ne s'éteint pas sous ubuntu 18-04 LTS Status in Ubuntu: Incomplete Bug description: Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et reste figé sur les points sous le logo Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 1 17:30:47 2019 DistUpgraded: 2019-05-01 13:16:39,149 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2019-04-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=9631566a-db77-4321-8f5e-f7dcd5218802 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-01 (0 days ago) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed May 1 17:26:15 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827235/+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 1827284] Re: No animation when GNOME Activities overview is opened
I noticed this issue upstream in Gnome 3.30 and 3.32 too. But I assumed it was a *feature* and not a bug -- maybe an attempt by the developers to make opening the app drawer faster before the fix for bug 1750197 existed. I didn't realize this was a regression compared to the original Gnome 3.28 behaviour. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1827284 Title: No animation when GNOME Activities overview is opened Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: New Status in gnome-shell source package in Eoan: Confirmed Bug description: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. It's worth mentioning that the animation shows up if you access activities through the top right hot corner, but it doesn't if you press the button or the Windows key. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827284/+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 1827284] Re: No animation when GNOME Activities overview is opened
If this bug does get fixed then the fix would likely go into Ubuntu 19.10 and 18.04, but not the versions in between. Because the versions in between were released with this behaviour, where it is arguably a feature. ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Low Status: Confirmed ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu Eoan) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827284 Title: No animation when GNOME Activities overview is opened Status in gnome-shell package in Ubuntu: Opinion Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell source package in Eoan: Opinion Bug description: On Ubuntu 18.04.2, Xorg, Gnome version 3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when you open the activities panel. When you close it, the animation shows up normally. The animation used to work, but it stopped by the end of April 2019. It doesn't seem to be a video driver issue, since it happens both when using Nvidia and Intel graphics. The issue persists after disabling all Gnome extensions. It's worth mentioning that the animation shows up if you access activities through the top right hot corner, but it doesn't if you press the button or the Windows key. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 1 18:00:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-11 (141 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827284/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
I used ubuntu-bug as per instructions. The first time ubuntu-bug crashed when I hit the Send button, upon a second attempt it might have been successful, but I'm not sure. The ubuntu-bug window closed immediately when I hit Send, without feedback from either from the ubuntu-bug UI or in the terminal. I'm not sure if the information can find its way to this particular bug report given that I was never asked to specify where it belongs. This is all rather confusing. Upon further testing of Totem, I have discovered that what's triggering the issue is the subtitles being turned off. Simply open a file, turn the subtitles off, and try to load a new file. No need to wait. -- 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/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: Incomplete Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1827194/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Please follow all the instructions in: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment and tell us what you find. -- 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/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: Incomplete Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1827194/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Actually, this might be what you're looking for? The timestamp seems off though. https://errors.ubuntu.com/oops/5303ab96-6c83-11e9-92de-fa163e6cac46 -- 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/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: Incomplete Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1827194/+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 1795372] Re: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed()
~seb128: Since this also affects 18.04.2 via #1827295, is an SRU possible / needed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795372 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Firstly, I didn't get this in 18.04, only since the upgrade to beta of 18.10 a couple of days ago. For that reason suspect not a dupe of #1735662 I was interacting with the network tab in control center *because*, since that update to Cosmic beta, I've been having an admittedly minor cosmetic problem (but one that bugs me) where the top panel network icon continues to show as being wifi after plugging into a thunderbolt 3 dock with an ethernet connection, although it only settles down to that after a minute or so of apparent indecision. The ethernet connection is *up*, but in Bionic that meant that's reliably the one that showed, correctly IMHO because that's the one with the lower routing metric, and one certainly hopes is the fastest too. In addition, potentially relevant, I see two wired connections in the network preferences, and in the "wired" part of the status menu. One for "Wired connection 1" and one with the name of my ethernet interface, which in this case, in the new style, is "enp63s0". It's the latter that seems now to get automatically selected when I plug into the dock. (The ethernet port on the TB3 dock is the *only* wired connection this laptop has ever had, and that only ever on my home network.) I can't say whether I also had two such wired connection entries before the upgrade to Cosmic, as I didn't have cause to look (the status icon always behaved as expected). Given the name of the method/function that crashed, is it possible that this is also behind the apparent indecision of the network status icon, and it often settling down on the wrong interface. After posting this bug report I will attempt to delete the wired connection called "Wired connection 1", that currently seems to be unused, and see what happens thereafter. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 11:55:55 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-11 (19 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: gnome-control-center network ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x555ef44e2043 : jmpq *0xc0(%rax) PC (0x555ef44e2043) ok source "*0xc0(%rax)" ok SP (0x7ffeff419998) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-control-center StacktraceTop: net_device_simple_get_speed () ?? () g_cclosure_marshal_VOID__BOOLEANv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed() UpgradeStatus: Upgraded to cosmic on 2018-09-29 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795372/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
That's certainly one totem crash, thanks :) Unfortunately that one doesn't seem to be readable/retraceable. So please try repeating with more freezes and forced crashes. -- 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/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in totem package in Ubuntu: Incomplete Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-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: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1827194/+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 1423912] Re: Chrome Remote Desktop Plugin Fails To Show Screen On Client
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1423912 Title: Chrome Remote Desktop Plugin Fails To Show Screen On Client Status in chromium-browser package in Ubuntu: Expired Bug description: If I'm trying to remotely access my Ubuntu machine from my Android device using the Chrome Remote Desktop app, all the app lives me is a black screen with an "X" as a mouse pointer. No commands filter through to the computer either, so if I do a CTRL ALT DEL, nothing happens. Please fix. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 40.0.2214.111-0ubuntu0.14.10.1. ProcVersionSignature: Ubuntu 3.16.0-30.40-lowlatency 3.16.7-ckt3 Uname: Linux 3.16.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 20 08:49:13 2015 InstallationDate: Installed on 2014-11-08 (104 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1423912/+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 829015] Re: Thunderbird "Login Failed" dialogue loop
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/829015 Title: Thunderbird "Login Failed" dialogue loop Status in thunderbird package in Ubuntu: Expired Bug description: I set up thunderbird to be my mail client on my work computer. It has been working without issue My network administrator made me change my network password, which I have done. 1. I open thunderbird, and it downloads my incoming mail from our company mail, no problem. 2. It displays a dialogue box saying "Login to failed." 3. I click the "Enter New Password" button. Expected behavior = Login text box appears Actual behavior = The "Login Failed" dialogue box just keeps refreshing and appearing on the screen ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.11+build2+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 Architecture: amd64 Date: Thu Aug 18 12:50:12 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/829015/+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 231502] Re: Passphrase dialog doesn't accept input
[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.] ** Changed in: seahorse (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/231502 Title: Passphrase dialog doesn't accept input Status in seahorse package in Ubuntu: Expired Bug description: Binary package hint: seahorse Since upgrading to Hardy Heron, I ran into problems with the Passphrase dialog when using Enigmail with Thunderbird. It'll plug along fine, not grabbing focus, but accepting input. But then, at some point, I'll hit "send" on a message, the passphrase dialog will come up, and it won't accept input. Even if I click to give it focus, it still won't accept input. Characters don't show in the text box, and typing return won't confirm/close the dialog. Strangely, hitting Escape _will_ close the dialog. Once this starts happening, it seems to keep happening. Logging out/in, even restarting (IIRC) don't fix the problem. It took me a while to figure out that Enigmail was delegating the passphrase stuff to a gpg-agent, and wrapping thunderbird with a script that unsets GPG_AGENT_INFO did the trick (so that it doesn't call out to seahorse). Once I experienced the problem and tracked it to seahorse, I also tried gpg directly from the commandline with --use-agent, and see the same symptoms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/231502/+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 1187724] Re: thunderbird crashes at startup
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1187724 Title: thunderbird crashes at startup Status in thunderbird package in Ubuntu: Expired Bug description: This is repeatible. thunderbird --safe-mode also crashes Removing ~.thunderbird/ does not fix the problem. Running thunderbird as another user (different home directory, user never ran thunderbird before) DOES fix the problem and thunderbird starts normally. Clearly there is something about my user environment which is crashing thunderbird - but it is also a bug in thunderbird (it should not crash). I have tried removing gconf settings too - but that made no difference. Next step suggestions would be welcome! Cheers Tim ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: thunderbird 17.0.6+build1-0ubuntu0.13.04.1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twatts 1920 F pulseaudio BuildID: 20130510125337 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Jun 5 11:24:25 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-26 (39 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 137.73.122.1 dev eth0 proto static 137.73.122.0/24 dev eth0 proto kernel scope link src 137.73.122.214 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NoProfiles: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/31/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0F428D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/31/2009:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1187724/+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 1186636] Re: about:permissions doesn't remember changes
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/1186636
Title:
about:permissions doesn't remember changes
Status in firefox package in Ubuntu:
Expired
Bug description:
I went to about:config and changed plugins.click_to_play to true, as
instructed at e.g. https://support.mozilla.org/en-US/questions/956759
Now I'd like youtube to play without clicking. I go to
about:permissions, find youtube.com and www.youtube.com, and set
Plugins to "Allow". Now go to youtube, and ask it to show me
something. It sits there, waiting for me to click on the player
window as instructed by plugins.click_to_play. Huh? Go back to
about:permissions, and find out that Plugins under www.youtube.com has
been reset to Always Ask.
Expected behaviour: about:permissions should save my changes, and
www.youtube.com (e.g.) should stop asking for permission to play
videos.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: firefox 21.0+build2-0ubuntu0.13.04.2
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bwp4240 F pulseaudio
/dev/snd/controlC0: bwp4240 F pulseaudio
BuildID: 20130512193848
Channel: Unavailable
Date: Sat Jun 1 14:57:15 2013
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-05-18 (14 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 10.1.1.1 dev wlan0 proto static
10.1.1.0/24 dev wlan0 proto kernel scope link src 10.1.1.10 metric 9
169.254.0.0/16 dev wlan0 scope link metric 1000
MarkForUpload: True
PrefSources:
prefs.js
[Profile]/extensions/{f69e22c7-bc50-414a-9269-0f5c344cd94c}/defaults/preferences/defaults.js
Profiles: Profile0 (Default) - LastVersion=21.0/20130512193848 (In use)
RelatedPackageVersions:
google-talkplugin 3.19.1.0-1
icedtea-7-plugin 1.3.2-1ubuntu1
totem-mozilla 3.6.3-0ubuntu6
rhythmbox-mozilla 2.98-0ubuntu5
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC7WW (2.27 )
dmi.board.name: 6465CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6465CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1186636/+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 372389] Re: copy filter broken resulting in empty email from 01.01.1970
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/372389 Title: copy filter broken resulting in empty email from 01.01.1970 Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird To reproduce the problem 2 filters are needed, example: 1: if 'to or cc' contains 'my_add...@test.net' copy to 'directory_1' 2: if 'subject' contains 'test_123' move to 'directory_test' with such filter when the email is received which match both filters the email correctly appears in 'directory_test' but in 'directory_1' where should be copied at the begining instead of original one is only empty email with date 01/01/1970 I saw some similar bugs reported about 2007 but using latest Thunderbird I have the same issue, Cheers, Goral, ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.28-11-generic i686 UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/372389/+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 1827328] [NEW] ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
Public bug reported:
In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).
This means that ttys, that are explicitly blacklisted from Modem Manager
by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is still opened
and probed by Modem Manager although it should not.
This is a common cause of problems and frustrations for people working
with actual serial devices, e.g. within embedded development (e.g.
Arduino and the like). See https://nick.zoic.org/art/failed-to-set-dtr-
rts-systemd-modemmanager/ for an example.
A proposed solution is to change the following line in:
/lib/systemd/system/ModemManager.service
from:
ExecStart=/usr/sbin/ModemManager --filter-policy=strict
to:
ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: modemmanager 1.10.0-1 [modified:
lib/systemd/system/ModemManager.service]
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: Thu May 2 15:35:58 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-26 (340 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)
** Affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1827328
Title:
ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
Status in modemmanager package in Ubuntu:
New
Bug description:
In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).
This means that ttys, that are explicitly blacklisted from Modem
Manager by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is
still opened and probed by Modem Manager although it should not.
This is a common cause of problems and frustrations for people working
with actual serial devices, e.g. within embedded development (e.g.
Arduino and the like). See https://nick.zoic.org/art/failed-to-set-
dtr-rts-systemd-modemmanager/ for an example.
A proposed solution is to change the following line in:
/lib/systemd/system/ModemManager.service
from:
ExecStart=/usr/sbin/ModemManager --filter-policy=strict
to:
ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: modemmanager 1.10.0-1 [modified:
lib/systemd/system/ModemManager.service]
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: Thu May 2 15:35:58 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-26 (340 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1827328/+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
