[Desktop-packages] [Bug 1914230] Re: [High priority] Screen keyboard doesn't display other languages characters, only english
OK, let's make this bug about Japanese which is already being tracked in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3422 Thai it seems already exists in GNOME 3.36 according to https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3106 The other keyboard layouts I'm not sure about. Please log upstream bugs for each at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3422 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3422 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3106 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3106 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3422 Importance: Unknown Status: Unknown ** Summary changed: - [High priority] Screen keyboard doesn't display other languages characters, only english + On-screen keyboard for Japanese doesn't display Japanese characters, only English ** Changed in: gnome-shell (Ubuntu) Importance: Wishlist => Medium -- 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/1914230 Title: On-screen keyboard for Japanese doesn't display Japanese characters, only English Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914230] Re: [High priority] Screen keyboard doesn't display other languages characters, only english
@vanvugt "Please choose a specific language for this bug to be about." Tamil, Thai, Sinhala(Sinhalese), Korean, Chinese, Japanese etc. Steps to reproduce 1. Add these languages (may not need to apply system wide) 2. Switch to eg: Japanese 3. Tap(touch) on text field then screen keyboard will be appear automatically (Or force open screen keyboard manually) 4. You will see that, it still appear in english (This also applicable to english characters based languages similar Spanish. just doesn't appear its unique screen keyboard) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914230 Title: [High priority] Screen keyboard doesn't display other languages characters, only english Status in gnome-shell package in Ubuntu: New Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Josue, the first step would be to fix your usb_modeswitch package installation, maybe by re-installing it. Once you see in your logs that it runs normally when the stick is inserted, check if your problem persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654733] Re: Incorrect Bitrate shown after mp3 VBR encoding
Seems to work fine here. Encoded a wav to mp3-vbr (quality=0.0) Output bitrate = 224 kbps $ gst-discoverer-1.0 Track1.mp3 Analyzing file:///home/gst/Music/X/Y/Track1.mp3 Done discovering file:///home/gst/Music/X/Y/Track1.mp3 Topology: unknown: ID3 tag audio: MPEG-1 Layer 3 (MP3) Properties: Duration: 0:09:15.23100 Seekable: yes Live: no Tags: track count: 6 track number: 4 encoder: Rhythmbox 123451234 title: X artist: Y album: Z genre: Test container format: ID3 tag has crc: false channel mode: joint-stereo audio codec: MPEG-1 Layer 3 (MP3) nominal bitrate: 224000 Where do you see the incorrect bitrate ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1654733 Title: Incorrect Bitrate shown after mp3 VBR encoding Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Triaged Bug description: Ubuntu 16.04 rhythmbox 3.3 Wrong bitrate reported in file metatdata even though file seems to be correct quality and size after CD import. Metadata shown incorrectly in rhythmbox, nautilus and vlc (PC and Android). Case 1 Rhythmbox rip Edit/preferences/music VBR quality 0,0 selected (best quality) track imported from CD; size of mp3 file = 9,0 MB Bitrate shown in metadata: 31 kbps Sample rate 44100 Case 2 Rhythmbox rip Edit/preferences/music VBR quality 9,9 selected (lowest quality) track imported from CD; size of mp3 file = 1,3 MB Bitrate shown in metadata: 7 kbps Sample rate 11025 Case 3 - different software Asunder CD ripper VBR 245 kbps (best quality) track imported from CD; size of mp3 file = 9,0 MB (same as case 1 above) Bitrate shown in metadata: 237 kbps Sample rate 44100 Track used: Rickie Jones Pirates track 1, 5 min 30 secs To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1654733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914288] Re: Xorg freeze
Thanks for the bug report. 1. Next time the freeze happens please reboot and then in a Terminal window run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 2. Please also follow these steps in case the freeze is the result of something crashing: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 3. Please try an older kernel series if you can, like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.94/ and tell us if that avoids the problem. ** 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/1914288 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: Freezes randomly during usage and always after recovering from suspend mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 16:51:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08ca] InstallationDate: Installed on 2020-09-10 (144 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 3583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 amdgpu.dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0NN4D6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914225] Re: Emoji button and pack for screen keyboard
Please request the feature from the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues and then tell us the new issue ID here. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914225 Title: Emoji button and pack for screen keyboard Status in gnome-shell package in Ubuntu: Incomplete Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) I aware that ubuntu offer "insert emoji" feature but it's not usable everywhere and keyboard shortcut method also the same. https://www.omgubuntu.co.uk/2018/06/use-emoji-linux-ubuntu-apps Furthermore, both methods cant use as force input to any text field or any limited environment as if it has built-in on screen keyboard I noticed there're few keyboard types but its annoying to use with every languages. (because such keyboards are one type and our common language keyboards are another so always has to switch) Samples in two steps https://gitee.com/mHatsune/chaya/raw/master/disk/emoji3.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/emoji4.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914226] Re: Add option to enable screen-keyboard icon in dock
The screenshot provided is from Windows 10 so it's hard to tell which "dock" you are requesting this for. Please specify which part of the screen you are requesting this on. ** Tags added: osk ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914226 Title: Add option to enable screen-keyboard icon in dock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Currently if enable it through universal access > screen keyboard then it makes quite annoying due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914223] Re: Add screen keyboard modes (option to morph into several keyboards)
Please request the feature from the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues and then tell us the new issue ID here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914223 Title: Add screen keyboard modes (option to morph into several keyboards) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Add screen keyboard modes (option to morph into several keyboards) Modes: Normal(default), Thumb and Standard (standard has all keys has on physical keyboard that doesn't even has on current ubuntu screen keyboard) https://gitee.com/mHatsune/chaya/raw/master/disk/modes.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/standard.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/thumb.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914164] Re: [nvidia] [radeon] Shell labels randomly disappear from the menu panel (top bar)
Thanks. It's possible there's some VT switching happening in the screen locking/unlocking. Or just mode switching. If so then that can trigger an annoying feature of the Nvidia driver where it will forget its textures: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt We don't yet have all the fixes we need to deal with that feature of Nvidia, and it can't be turned off either. The other bugs associated with this are bug 1876632 and bug 1855757. There's also bug 1910435 which sounds most similar to this, but the author of that bug is not responding at the moment. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1914164 Title: [nvidia] [radeon] Shell labels randomly disappear from the menu panel (top bar) Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files. Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context! Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x507 Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I'm
[Desktop-packages] [Bug 1914230] Re: [High priority] Screen keyboard doesn't display other languages characters, only english
Please choose a specific language for this bug to be about. ** Tags added: osk ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914230 Title: [High priority] Screen keyboard doesn't display other languages characters, only english Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914223] Re: Add screen keyboard modes (option to morph into several keyboards)
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Tags added: osk -- 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/1914223 Title: Add screen keyboard modes (option to morph into several keyboards) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Add screen keyboard modes (option to morph into several keyboards) Modes: Normal(default), Thumb and Standard (standard has all keys has on physical keyboard that doesn't even has on current ubuntu screen keyboard) https://gitee.com/mHatsune/chaya/raw/master/disk/modes.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/standard.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/thumb.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914225] Re: Emoji button and pack for screen keyboard
** Tags added: osk -- 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/1914225 Title: Emoji button and pack for screen keyboard Status in gnome-shell package in Ubuntu: Incomplete Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) I aware that ubuntu offer "insert emoji" feature but it's not usable everywhere and keyboard shortcut method also the same. https://www.omgubuntu.co.uk/2018/06/use-emoji-linux-ubuntu-apps Furthermore, both methods cant use as force input to any text field or any limited environment as if it has built-in on screen keyboard I noticed there're few keyboard types but its annoying to use with every languages. (because such keyboards are one type and our common language keyboards are another so always has to switch) Samples in two steps https://gitee.com/mHatsune/chaya/raw/master/disk/emoji3.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/emoji4.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914164] Re: [nvidia] Shell labels randomly disappear from the menu panel (top bar)
** Tags added: radeon ** Summary changed: - [nvidia] Shell labels randomly disappear from the menu panel (top bar) + [nvidia] [radeon] Shell labels randomly disappear from the menu panel (top bar) ** Tags added: hybrid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914164 Title: [nvidia] [radeon] Shell labels randomly disappear from the menu panel (top bar) Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files. Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context! Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x507 Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I'm also using a StreamDeck USB device, if that's useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Tested on kernel 5.11.0-rc6.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=f
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I've checked and it's true that working, but not fully. The secondary mouse
click doesn't work if I press the right bottom corner of the touchpad
(registers primary mouse click).
Rotation, pitching, swipe with 3/4 fingers doesn't seem to work either.
** Attachment added: "evtest"
https://bugs.launchpad.net/fedora/+source/linux/+bug/1887190/+attachment/5459188/+files/evtest
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulsea
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Tags removed: verification-needed-groovy
** Tags added: verification-failed-groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256colo
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** No longer affects: ubuntu-translations ** Changed in: hwe-next Status: New => Fix Released ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: Fix Released Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Groovy: Fix Committed Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Indeed it doesn't seem to be with usb_modeswitch: 5.4 Feb 2 18:18:31 ubuntu-dev pppd[3132]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 2 18:18:31 ubuntu-dev pppd[3132]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 2 18:18:31 ubuntu-dev pppd[3132]: nm-ppp-plugin: got credentials from NetworkManager Feb 2 18:18:31 ubuntu-dev pppd[3132]: PAP authentication succeeded Feb 2 18:18:31 ubuntu-dev pppd[3132]: nm-ppp-plugin: status 8 / phase 'network' Feb 2 18:18:31 ubuntu-dev kernel: [ 184.332332] PPP BSD Compression module registered Feb 2 18:18:31 ubuntu-dev kernel: [ 184.341856] PPP Deflate Compression module registered Feb 2 18:18:38 ubuntu-dev kernel: [ 191.426698] sd 4:0:0:1: [sdd] Attached SCSI removable disk Feb 2 18:18:39 ubuntu-dev kernel: [ 192.201305] ISO 9660 Extensions: Microsoft Joliet Level 1 Feb 2 18:18:39 ubuntu-dev kernel: [ 192.206633] ISOFS: changing to secondary root 5.8 Feb 2 18:05:43 ubuntu-dev pppd[7058]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 2 18:05:43 ubuntu-dev pppd[7058]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 2 18:05:43 ubuntu-dev pppd[7058]: nm-ppp-plugin: got credentials from NetworkManager Feb 2 18:05:43 ubuntu-dev pppd[7058]: PAP authentication succeeded Feb 2 18:05:43 ubuntu-dev pppd[7058]: nm-ppp-plugin: status 8 / phase 'network' Feb 2 18:05:54 ubuntu-dev kernel: [ 1965.172744] sd 4:0:0:1: [sdd] Attached SCSI removable disk Feb 2 18:05:55 ubuntu-dev kernel: [ 1965.757767] usb 1-3: USB disconnect, device number 33 Feb 2 18:05:55 ubuntu-dev kernel: [ 1965.757905] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device Could you (or someone else) please reassign to the kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
@Sebastien Bacher Just doing an occasional Python GET request to the
same URL others are using:
https://location.services.mozilla.com/v1/geolocate?key=geoclue
Alternatively, calling that URL in a browser. It works occasionally, but
mostly it just returns a 403. The JSON string:
{"error":{"errors":[{"domain":"usageLimits","reason":"dailyLimitExceeded","message":"You
have exceeded your daily limit."}],"code":403,"message":"You have
exceeded your daily limit."}}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Triaged
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Looking at the original 5.4 syslog again we can see the same error so I don't think that is the issue: Jan 11 10:51:06 ubuntu usb_modeswitch_dispatcher[6535]: Unable to open bind list file: No such file or directory Jan 11 10:51:06 ubuntu usb_modeswitch[6535]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 10:51:06 ubuntu usb_modeswitch[6535]: usb_modeswitch: please report the device ID to the Linux USB developers! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Hi Dimitri John Ledkov (@xnox), What happens when installed driver with ubuntu-drivers is updated with the update manager? In this case, new module that is not installed with ubuntu-driver will not be signed? Can you share an official reference that the Ubuntu-drivers tool automatically signs the modules? I have never come across any information about the auto-signature capability of the ubuntu-drivers tool and I wondering how it works. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906877] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1906877 Title: diagnostics panel can leave automatic crash reporting enabled Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Incomplete Status in gnome-control-center source package in Focal: Incomplete Status in gnome-control-center source package in Groovy: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Bug description: * Impact If one selects "Automatic" in the "Send error reports to Canonical" portion of "Problem Reporting" the file /var/lib/apport/autoreport is created. However, if you later switch to "Never" the file is not removed but the panel continues to show "Never". * Test case - change the automatic report option in settings to automatic and then to never, the /var/lib/apport/autoreport file should be removed * Regression potential The patch modifies the whoopsie configuration, check that the service status is right for the 3 auto/manual/never options ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 4 12:38:37 2020 InstallationDate: Installed on 2016-01-22 (1778 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905791] Re: Resizing in awesome WM makes chromium stop redrawing its window
Excellent, thanks for following up Balint. It's weird that the upstream bug report isn't marked fixed though. -- 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/1905791 Title: Resizing in awesome WM makes chromium stop redrawing its window Status in chromium-browser package in Ubuntu: Fix Released Bug description: Start chromium in awesome. Start a new terminal. Try clicking on chromium. It is working, it is just not redrawn making it mostly useless. The last version that worked for sure was the 1328 snap version, but it is not available anymore. Reproducible on Ubuntu 20.04 and 21.04. Maybe on other releases as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** No longer affects: xorg-server-hwe-18.04 (Ubuntu) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Focal) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Groovy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Groovy: Fix Committed Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled
This bug was fixed in the package gnome-control-center - 1:3.38.3-0ubuntu1 --- gnome-control-center (1:3.38.3-0ubuntu1) groovy; urgency=medium * New stable version (lp: #1911918) * debian/patches/gitlab_ucm_mixer_control_select.patch: - removed, the change is in the new version * debian/patches/0016-diagnostics-Add-Whoopsie-support.patch: - correct set and reflect the autoreport configuration (lp: #1906877) -- Sebastien Bacher Fri, 15 Jan 2021 16:09:17 +0100 ** Changed in: gnome-control-center (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1906877 Title: diagnostics panel can leave automatic crash reporting enabled Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Incomplete Status in gnome-control-center source package in Focal: Incomplete Status in gnome-control-center source package in Groovy: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Bug description: * Impact If one selects "Automatic" in the "Send error reports to Canonical" portion of "Problem Reporting" the file /var/lib/apport/autoreport is created. However, if you later switch to "Never" the file is not removed but the panel continues to show "Never". * Test case - change the automatic report option in settings to automatic and then to never, the /var/lib/apport/autoreport file should be removed * Regression potential The patch modifies the whoopsie configuration, check that the service status is right for the 3 auto/manual/never options ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 4 12:38:37 2020 InstallationDate: Installed on 2016-01-22 (1778 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Update Released
The verification of the Stable Release Update for wslu has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Groovy: Fix Released Status in wslu source package in Hirsute: Fix Released Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911918] Re: SRU the current 3.38 stable update
This bug was fixed in the package gnome-control-center - 1:3.38.3-0ubuntu1 --- gnome-control-center (1:3.38.3-0ubuntu1) groovy; urgency=medium * New stable version (lp: #1911918) * debian/patches/gitlab_ucm_mixer_control_select.patch: - removed, the change is in the new version * debian/patches/0016-diagnostics-Add-Whoopsie-support.patch: - correct set and reflect the autoreport configuration (lp: #1906877) -- Sebastien Bacher Fri, 15 Jan 2021 16:09:17 +0100 ** Changed in: gnome-control-center (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1911918 Title: SRU the current 3.38 stable update Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential The changes are small fixes but ensure each page of the setting is still loading, also check that the printing panel layout is still correct and that the sound panel works correctly since that's where the less trivial changes have been commited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1911918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911918] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1911918 Title: SRU the current 3.38 stable update Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Status in gnome-control-center source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential The changes are small fixes but ensure each page of the setting is still loading, also check that the printing panel layout is still correct and that the sound panel works correctly since that's where the less trivial changes have been commited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1911918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Re: [SRU] Avoid error message when the file doesn't exist
This bug was fixed in the package wslu - 3.2.1-0ubuntu1.1 --- wslu (3.2.1-0ubuntu1.1) groovy; urgency=medium * header: Avoid error message when the file doesn't exist (LP: #1911379) -- Patrick Wu Wed, 13 Jan 2021 11:26:25 +0800 ** Changed in: wslu (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Groovy: Fix Released Status in wslu source package in Hirsute: Fix Released Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914178] Re: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914178 Title: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue Status in firefox package in Ubuntu: New Bug description: No further information available ProblemType: Package DistroRelease: Ubuntu 20.10 Package: firefox 84.0.2+build1-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.3 AptOrdering: firefox:amd64: Install firefox-locale-en:amd64: Install firefox-locale-fr:amd64: Install libmysqlclient21:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yvan 3192 F pulseaudio /dev/snd/controlC0: yvan 3192 F pulseaudio /dev/snd/controlC1: yvan 3192 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable Date: Mon Feb 1 23:09:11 2021 DpkgHistoryLog: Start-Date: 2021-02-01 23:09:03 Commandline: apt-get upgrade Requested-By: yvan (1000) Upgrade: firefox-locale-en:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1), firefox-locale-fr:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1), libmysqlclient21:amd64 (8.0.22-0ubuntu0.20.10.2, 8.0.23-0ubuntu0.20.10.1), firefox:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue ForcedLayersAccel: False IpRoute: default via 192.168.0.254 dev enp4s0 proto dhcp metric 100 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.30 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904859] Re: [snap] cannot send file from Nautilus
This bug was fixed in the package nautilus-sendto - 3.8.6-3ubuntu0.20.10.1 --- nautilus-sendto (3.8.6-3ubuntu0.20.10.1) groovy; urgency=medium * debian/patches/gitlab_thunderbird_cmd.patch: - remove an old workaround for thunderbird, it's not useful anymore and is creating problem with the snap cmd (lp: #1904859) -- Sebastien Bacher Mon, 23 Nov 2020 20:31:53 +0100 ** Changed in: nautilus-sendto (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus Status in nautilus-sendto package in Ubuntu: Fix Released Status in nautilus-sendto source package in Focal: Fix Released Status in nautilus-sendto source package in Groovy: Fix Released Bug description: * Impact Nautilus->sendto fails to use the thunderbird snap command * Test case On a Ubuntu default session $ snap install thunderbird $ nautilus $ right click on a file and select the sendto entry -> thunderbird should be started with a composer dialog and the selected attachment included * Regression potential The patch removes an old hack that parsed and changed the thunderbird command, verify that thunderbird is still correctly start using it from different source (snap, deb, flatpak?) - TB 78.5.0 snap Focal Nothing happens when I right-click on a file (using Nautilus) from my home and choose 'send to'. I did not have such a problem using TB deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Just for reference the syslog for 5.4.0-65-generic where it works fine. ** Attachment added: "5.4.0-65-syslog.txt" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5459181/+files/5.4.0-65-syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911934] Update Released
The verification of the Stable Release Update for gnome-desktop3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1911934 Title: SRU the current 3.38 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Groovy: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.38.3 * Regression potential The update has updated translations and version number, translations are part of langpacks and not shipped with the update so it leaves the version string to verify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1911934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911934] Re: SRU the current 3.38 stable update
This bug was fixed in the package gnome-desktop3 - 3.38.3-0ubuntu1 --- gnome-desktop3 (3.38.3-0ubuntu1) groovy; urgency=medium * New stable version (lp: #1911934) -- Sebastien Bacher Fri, 15 Jan 2021 17:32:07 +0100 ** Changed in: gnome-desktop3 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1911934 Title: SRU the current 3.38 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Groovy: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.38.3 * Regression potential The update has updated translations and version number, translations are part of langpacks and not shipped with the update so it leaves the version string to verify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1911934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver
Fixed in Ubuntu Hirsute --- system-config-printer (1.5.15-0ubuntu1) hirsute; urgency=medium * New upstream release: - UI freeze when changing the driver of an existing printer fixed (Upstream issue #179) - Compatible with new autoconf [...] -- Till Kamppeter Tue, 26 Jan 2021 12:25:00 +0100 ** Also affects: system-config-printer (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: system-config-printer (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: system-config-printer (Ubuntu) Importance: Undecided => Medium ** Changed in: system-config-printer (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: system-config-printer (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: system-config-printer (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: New Status in system-config-printer source package in Groovy: New Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Attachment added: "5.8.0-41-syslog-test-1.txt" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5459178/+files/5.8.0-41-syslog-test-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905791] Re: Resizing in awesome WM makes chromium stop redrawing its window
Fixed in: $ snap list chromium Name Version Rev Tracking Publisher Notes chromium 88.0.4324.96 1466 latest/stable canonical✓ - ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1905791 Title: Resizing in awesome WM makes chromium stop redrawing its window Status in chromium-browser package in Ubuntu: Fix Released Bug description: Start chromium in awesome. Start a new terminal. Try clicking on chromium. It is working, it is just not redrawn making it mostly useless. The last version that worked for sure was the 1328 snap version, but it is not available anymore. Reproducible on Ubuntu 20.04 and 21.04. Maybe on other releases as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Attachment added: "5.8.0-41-syslog-test-2.txt" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5459179/+files/5.8.0-41-syslog-test-2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Attachment added: "5.8.0-41-install.txt" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5459180/+files/5.8.0-41-install.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Tried 5.8.0-41-generic. First try: It connects and disconnects several times: Feb 2 17:40:18 ubuntu-dev pppd[3599]: PAP authentication succeeded Feb 2 17:41:07 ubuntu-dev pppd[3827]: PAP authentication succeeded Feb 2 17:42:00 ubuntu-dev pppd[4018]: PAP authentication succeeded But it eventually works. Second try: Never works. See attached syslog files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1384952] Re: USB Soundcard no microphone (input) device
In #17 doesn't work for me, if I do that I have only a dummy output and no mic in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1384952 Title: USB Soundcard no microphone (input) device Status in alsa-driver package in Ubuntu: Confirmed Bug description: My Asus Xonar U7 Echelon External sound device working without input/capture device. No input device , Nothing recording with my usb soundcard. ~$ arecord -l List of CAPTURE Hardware Devices card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 ~$ lsusb Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alper 2249 F pulseaudio /dev/snd/pcmC1D0p: alper 2249 F...m pulseaudio /dev/snd/controlC1: alper 2249 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 24 00:46:11 2014 InstallationDate: Installed on 2014-10-07 (16 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7693 dmi.product.version: 2.0 dmi.sys.vendor: MSI modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1384952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
** Branch linked: lp:~mozillateam/firefox/firefox.groovy ** Branch linked: lp:firefox -- 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/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Incomplete Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914289] Re: Nautilus takes ~1 minute to open
PS: I do not have any NFS shares, and I have tried disabling Tracker. (Added this detail, since a lot of user seems to have issues like this caused by the combination of NFS shares and Tracker.) -- 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/1914289 Title: Nautilus takes ~1 minute to open Status in nautilus package in Ubuntu: New Bug description: Almost every time I try to launch Nautilus – whether via the panel, via the terminal, or by clicking "Open" buttons in programs – it takes close to 1 minute to launch. I have timed it using a watch, and it seems to take between 30 seconds and 1 minute from the relevant button is pressed before Nautilus appears on screen. This has been occurring for months. I think it started occuring after updating to Ubuntu 20.10, but I no longer remember precisely. I guessed it was a known issue that would be fixed, or just an issue specific to my setup, but now I am beginning to wonder whether I am facing some kind of true bug. All my hours of Google-fu and poking around the system has turned up nothing useful. In contrast to e.g. #1886021, there are no error messaged in the terminal that give any hints. Nor are there anything useful in the syslog – at least that I am able to spot. Given how infuriating it is to always have to wait for 30+ seconds to open any file dialog, I am very willing to help debug this. But I have now reached the limits of my (admittedly limited) debugging abilities. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 21:00:46 2021 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-05-04 (1005 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-07 (87 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-brasero3.12.2-6ubuntu1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1914289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
I'll give it a try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
** Branch linked: lp:~mozillateam/firefox/firefox.focal -- 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/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Incomplete Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914288] Re: Xorg freeze
** Information type changed from Private Security to Private ** Information type changed from Private to Public Security ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1914288 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Freezes randomly during usage and always after recovering from suspend mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 16:51:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08ca] InstallationDate: Installed on 2020-09-10 (144 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 3583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 amdgpu.dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0NN4D6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914289] [NEW] Nautilus takes ~1 minute to open
Public bug reported: Almost every time I try to launch Nautilus – whether via the panel, via the terminal, or by clicking "Open" buttons in programs – it takes close to 1 minute to launch. I have timed it using a watch, and it seems to take between 30 seconds and 1 minute from the relevant button is pressed before Nautilus appears on screen. This has been occurring for months. I think it started occuring after updating to Ubuntu 20.10, but I no longer remember precisely. I guessed it was a known issue that would be fixed, or just an issue specific to my setup, but now I am beginning to wonder whether I am facing some kind of true bug. All my hours of Google-fu and poking around the system has turned up nothing useful. In contrast to e.g. #1886021, there are no error messaged in the terminal that give any hints. Nor are there anything useful in the syslog – at least that I am able to spot. Given how infuriating it is to always have to wait for 30+ seconds to open any file dialog, I am very willing to help debug this. But I have now reached the limits of my (admittedly limited) debugging abilities. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 21:00:46 2021 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-05-04 (1005 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-07 (87 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-brasero3.12.2-6ubuntu1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy nautilus -- 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/1914289 Title: Nautilus takes ~1 minute to open Status in nautilus package in Ubuntu: New Bug description: Almost every time I try to launch Nautilus – whether via the panel, via the terminal, or by clicking "Open" buttons in programs – it takes close to 1 minute to launch. I have timed it using a watch, and it seems to take between 30 seconds and 1 minute from the relevant button is pressed before Nautilus appears on screen. This has been occurring for months. I think it started occuring after updating to Ubuntu 20.10, but I no longer remember precisely. I guessed it was a known issue that would be fixed, or just an issue specific to my setup, but now I am beginning to wonder whether I am facing some kind of true bug. All my hours of Google-fu and poking around the system has turned up nothing useful. In contrast to e.g. #1886021, there are no error messaged in the terminal that give any hints. Nor are there anything useful in the syslog – at least that I am able to spot. Given how infuriating it is to always have to wait for 30+ seconds to open any file dialog, I am very willing to help debug this. But I have now reached the limits of my (admittedly limited) debugging abilities. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 21:00:46 2021 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-05-04 (1005 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-07 (87 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-brasero3.12.2-6ubuntu1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1914289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
** Branch linked: lp:~mozillateam/firefox/firefox.bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Incomplete Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914288] [NEW] Xorg freeze
Public bug reported: Freezes randomly during usage and always after recovering from suspend mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 16:51:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08ca] InstallationDate: Installed on 2020-09-10 (144 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 3583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 amdgpu.dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0NN4D6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu ** Information type changed from Public to Private Security -- 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/1914288 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Freezes randomly during usage and always after recovering from suspend mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 16:51:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08ca] InstallationDate: Installed on 2020-09-10 (144 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 3583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 amdgpu.dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0NN4D6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 vers
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
>Jean- (jean-helou) wrote 6 hours ago: #87 >the next step to get a full fix and improved sound quality for voip calls over >BT headset is >coming in >https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 This is good news! Proper support for mSBC is critical for me to consider this bug resolved. It was the original intention of opening the bug in the first place :) -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
So as I understand it with the 5.8 kernel on Ubuntu 20.04 LTS the device is not recognized. Is that correct? If it is could you please test with the linux-image-5.8.0-41-generic package? Thanks in advance! ** Changed in: usb-modeswitch (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
Launchpad has imported 19 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1679933. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-12-01T05:46:55+00:00 Tetsuharu-ohzeki wrote: ## Environment - macOS Big Sur 11.0.1 - I reproduced this bug on macOS Caralina 10.15.7 too. - https://hg.mozilla.org/mozilla-central/rev/b0865ea584621ce9e7f68833565e3d8ae117ce32 ## Steps to reproduce 1. Launch Firefox. 2. Try to open a new window from the context menu on the icon in Dock ## Actual Result - Firefox is not responsible with rainbow cursor. - Firefox does not comeback and I need to quit Firefox forcely. - I reproduce this bug a few days ago. - I does not face this bug rarely on a new profile Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/0 On 2020-12-01T23:19:03+00:00 Dtownsend wrote: (In reply to Tetsuharu OHZEKI [:tetsuharu] (UTC+9) from comment #0) > - Firefox is not responsible with rainbow cursor. > - Firefox does not comeback and I need to quit Firefox forcely. > - I reproduce this bug a few days ago. > - I does not face this bug rarely on a new profile Can you clarify whether this means you do not see this with a new profile? Do you know which Nightly this started happening with? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/1 On 2020-12-02T13:42:40+00:00 Tetsuharu-ohzeki wrote: > Can you clarify whether this means you do not see this with a new profile? Yes. I face this bug reraly on a new profile. > Do you know which Nightly this started happening with? Sorry, I don't remember the concrete date about which Nightly starts to happen.. I feel that I faced this bug frequently from 11/20 (Fri) ~ 23 (Mon). At least I seem at that time which U.S entered to thanksgiving holiday. - Additional Information are: * WIth [yeasterday's Nightly](https://hg.mozilla.org/mozilla-central/rev/abafe6c923eb566ffb94fd6afe0e06766d0c27a6), I have not faced this bug. But I'm not sure about that this bug has been fixed actually. This bug sometimes does not happen. I seem that the step to reproduce is depends on some timing issue. * My main profile enables fission.autostart=true. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/2 On 2020-12-04T16:05:52+00:00 Tetsuharu-ohzeki wrote: Created attachment 9191329 stack information This is an information which I got from the macOS' dialog to report the crash shown after force quit Firefox Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/3 On 2020-12-04T17:34:21+00:00 Dtownsend wrote: Based on the stack info it looks like maybe Firefox was stuck in a deadlock somewhere in the HTTP code so moving this over there for mre investigation. Is this still occurring? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/4 On 2020-12-04T17:56:32+00:00 Tetsuharu-ohzeki wrote: > Is this still occurring? Yes. I seem this was some changed from the before. On the before, this bug is reproducible on launching Firefox every time. But now, - I face this bug on launching Firefox first time after daily update, and it's not always happens. - I feel this bug happens if I open a context window on the dock and opening an window. - But the timing is a bit scatterd. - If this bug does not happen in 10 sec after launching Firefox, then I never face to this bug whilte using Firefox until close. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914147/comments/5 On 2020-12-04T19:20:36+00:00 Dd-mozilla wrote: CacheIO Thread holds mRCWNLock and try to dispatch SyncRunnable on the main thread: 45 mozilla::net::nsHttpChannel::OnCacheEntryCheck(nsICacheEntry*, nsIApplicationCache*, unsigned int*) + 2485 (XUL + 7218629) [0x107e7d5c5] 1-45 45 mozilla::net::nsHttpChannel::OpenCacheInputStream(nsICacheEntry*, bool, bool) + 1539 (XUL + 7225683) [0x107e7f153] 1-45 45 mozilla::net::CacheEntry::GetSecurityInfo(nsISupports**) + 197 (XUL + 41189653) [0x109ee3115] 1-45 45 NS_DeserializeObject(nsTSubstring const&, nsISupports**) + 131 (XUL + 6
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
** Branch linked: lp:~mozillateam/firefox/firefox.xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Incomplete Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Changed in: usb-modeswitch (Ubuntu Focal) Milestone: focal-updates => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: Incomplete Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Tags added: sru-20200104 ** Tags added: sru-20200125 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: New Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"
This bug was fixed in the package libunity - 7.1.4+19.04.20190319-5 --- libunity (7.1.4+19.04.20190319-5) unstable; urgency=medium * debian/control: - fix typo in the Conflicts keyword * extras,src/Makefile.am: - set --shared-library valac option so the generated gir which is needed for the correct depends to be created * remove debian/patches which isn't use by the current packaging, it was an indication of the changes applied to the source but those are commited directly to the vcs now -- Sebastien Bacher Mon, 01 Feb 2021 18:01:36 +0100 ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1268210 Title: unity-scopes-runner: Typo in package description: "scoped" Status in Package Descriptions for Ubuntu: Triaged Status in libunity: Fix Committed Status in libunity package in Ubuntu: Fix Released Bug description: Package: unity-scopes-runner Version: 7.1.3+14.04.20131106-0ubuntu1 Hello, The package description contains a small typo, I think: The scope runner is a handy tool for wrapping on a desktop the various scoped installed on the system. Should be: The scope runner is a handy tool for wrapping on a desktop the various scopes installed on the system. in the string #16945 https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-main/fr/16945 Regards, Pascal To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1268210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
To elaborate, the error means that usb_modeswitch was not run at all, so anything that happens afterwards is unrelated to the package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: New Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
In both the "good" and the "bad" syslog, this error sticks out: Jan 19 18:24:06 ubuntu systemd[6325]: usb_modeswitch@1-3.service: Failed at step EXEC spawning /usr/sbin/usb_modeswitch_dispatcher: No such file or directory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: New Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
Thanks for the report Sergio. Could you please do the following (in a terminal) to help us diagnose the problem? $ sudo apt install firefox-dbg $ firefox -g # to launch firefox in gdb # at the gdb prompt, type "run" (without double quotes) then enter # when firefox hangs, get a complete backtrace by issuing: (gdb) t a a bt Save that backtrace to a file and attach it here. Thanks! ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Incomplete Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147] Re: Firefox hangs after upgrade to version 85
This could be https://bugzilla.mozilla.org/show_bug.cgi?id=1689809. ** Bug watch added: Mozilla Bugzilla #1689809 https://bugzilla.mozilla.org/show_bug.cgi?id=1689809 ** Bug watch added: Mozilla Bugzilla #1679933 https://bugzilla.mozilla.org/show_bug.cgi?id=1679933 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1679933 Importance: Unknown Status: Unknown -- 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/1914147 Title: Firefox hangs after upgrade to version 85 Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914148] Re: Firefox connstantly disabled on Apparmor
** Changed in: firefox (Ubuntu) Status: New => Won't Fix -- 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/1914148 Title: Firefox connstantly disabled on Apparmor Status in firefox package in Ubuntu: Won't Fix Bug description: Once again Apparmor policies are constantly disabled for Firefox. -I've reported this bug in December, then came a patch, then for the last month of January - regardless of updates, Firefox profiles are skipped. - You cannot be serious? -This is a consistent seccurity issue! - Please write rules that consistently work or teach us how to do so / deal with Mozilla "Feb 02 00:17:24 USER apparmor.systemd[1117]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 02 00:17:24 USER apparmor.systemd[1118]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 02 00:17:24 USER systemd[1]: Finished Load AppArmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Konstantin is right. I'm also using the snap for now but for different reasons this is not a good solution for beginners - like my parents for example. -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914274] [NEW] calendar needs relogging to sync for the first time after installation
Public bug reported: Just after installation of the system, I connected the calendar to my Google account. I was surprised that the events are not there, and there was no message about it. It turned out that in only synced after logging in and then logging out. It would be nice if it syncs without that, but if that's impossible/too hard to implement, there should be at least some message saying that logging out and in is needed. I was confused and didn't know why it doesn't work at first. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 17:57:31 2021 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2020-09-23 (131 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1914274 Title: calendar needs relogging to sync for the first time after installation Status in gnome-calendar package in Ubuntu: New Bug description: Just after installation of the system, I connected the calendar to my Google account. I was surprised that the events are not there, and there was no message about it. It turned out that in only synced after logging in and then logging out. It would be nice if it syncs without that, but if that's impossible/too hard to implement, there should be at least some message saying that logging out and in is needed. I was confused and didn't know why it doesn't work at first. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 17:57:31 2021 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2020-09-23 (131 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1914274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914077] Re: [snap] Add Greek langpack to LibreOffice snap package
** Merge proposal linked: https://code.launchpad.net/~libreoffice/+git/libreoffice-snap/+merge/397368 -- 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/1914077 Title: [snap] Add Greek langpack to LibreOffice snap package Status in libreoffice package in Ubuntu: New Bug description: Currently, the Libreoffice snap package supports the following UI languages: English (USA) Catalan Chinese (Traditional) French (France) German Hungarian Italian Japanese Polish Portuguese (both Portugal and Brazil) Russian Spanish (Spain) Turkish Greek is spoken by 11.1m people, which is a similar number for Catalan and Hundarian. In the Greek Public Service (for example, the judicial system), there are many Ubuntu laptops with no upgrade path for the latest version of LibreOffice. Can you please add Greek to the list? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1914077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
@michel.ekimia The Broadcom wifi driver issue has been fixed in https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914077] Re: [snap] Add Greek langpack to LibreOffice snap package
The original thread: https://forum.snapcraft.io/t/add-greek-langpack-to- libreoffice-snap-package/22496/4 ** Summary changed: - Add Greek langpack to LibreOffice snap package + [snap] Add Greek langpack to LibreOffice snap package -- 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/1914077 Title: [snap] Add Greek langpack to LibreOffice snap package Status in libreoffice package in Ubuntu: New Bug description: Currently, the Libreoffice snap package supports the following UI languages: English (USA) Catalan Chinese (Traditional) French (France) German Hungarian Italian Japanese Polish Portuguese (both Portugal and Brazil) Russian Spanish (Spain) Turkish Greek is spoken by 11.1m people, which is a similar number for Catalan and Hundarian. In the Greek Public Service (for example, the judicial system), there are many Ubuntu laptops with no upgrade path for the latest version of LibreOffice. Can you please add Greek to the list? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1914077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Also affects: usb-modeswitch (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: usb-modeswitch (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: usb-modeswitch (Ubuntu Focal) Milestone: None => focal-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Status in usb-modeswitch source package in Focal: New Status in usb-modeswitch source package in Hirsute: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908502] Re: [MIR] libdeflate
** Changed in: libdeflate (Ubuntu Hirsute) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in tiff package in Ubuntu: Triaged Status in libdeflate source package in Hirsute: New Status in tiff source package in Hirsute: Triaged Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Re: [SRU] Avoid error message when the file doesn't exist
It is tested and confirmed to be fixed. https://cdn.patrickwu.space/garage/screenshots/Screenshot%202021-02-02%20at%2010.49.44%20PM.png ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Groovy: Fix Committed Status in wslu source package in Hirsute: Fix Released Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
>From the log you linked: Get:263 http://ftpmaster.internal/ubuntu hirsute-proposed/main amd64 network-manager amd64 1.28.0-2ubuntu1 [2002 kB] ** Package changed: systemd (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: New Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914164] Re: [nvidia] Shell labels randomly disappear from the menu panel (top bar)
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5459123/+files/journal.txt -- 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/1914164 Title: [nvidia] Shell labels randomly disappear from the menu panel (top bar) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files. Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context! Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x507 Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I'm also using a StreamDeck USB device, if that's useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 22:16:07 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-18 (290 days ago)
[Desktop-packages] [Bug 1914164] Re: [nvidia] Shell labels randomly disappear from the menu panel (top bar)
This is a desktop computer so I don't suspend and resume. However I do lock the screen regularly, but I could not reproduce the problem by locking and unlocking the screen. The problem seems to occur after a certain amount of uptime, though I have not measured how much uptime. Requested output attached. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914164/+attachment/5459122/+files/lspci.txt -- 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/1914164 Title: [nvidia] Shell labels randomly disappear from the menu panel (top bar) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files. Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context! Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x507 Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. I'm also using a StreamDeck USB device, if that's useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux
[Desktop-packages] [Bug 1914062] [NEW] NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
You have been subscribed to a public bug: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: rls-hh-incoming update-excuse -- NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC https://bugs.launchpad.net/bugs/1914062 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
This bug was fixed in the package flatpak - 1.8.2-1ubuntu0.1 --- flatpak (1.8.2-1ubuntu0.1) groovy-security; urgency=medium * SECURITY UPDATE: Flatpak sandbox escape via spawn portal (LP: #1911473) - debian/patches/CVE-2021-21261-1.patch: common: Add a backport of G_DBUS_METHOD_INVOCATION_HANDLED. - debian/patches/CVE-2021-21261-2.patch: run: Convert all environment variables into bwrap arguments. - debian/patches/CVE-2021-21261-3.patch: tests: Expand coverage for environment variable overrides. - debian/patches/CVE-2021-21261-4.patch: context: Add --env-fd option. - debian/patches/CVE-2021-21261-5.patch: portal: Convert --env in extra-args into --env-fd. - debian/patches/CVE-2021-21261-6.patch: tests: Exercise --env-fd. - debian/patches/CVE-2021-21261-7.patch: portal: Do not use caller-supplied variables in environment. - debian/patches/CVE-2021-21261-8.patch: tests: Assert that --env= does not go in `flatpak run` or bwrap environ. - CVE-2021-21261 -- Andrew Hayzen Fri, 22 Jan 2021 00:59:12 + ** Changed in: flatpak (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: Fix Released Status in flatpak source package in Focal: Fix Released Status in flatpak source package in Groovy: Fix Released Status in flatpak source package in Hirsute: Fix Released Bug description: [Links] Upstream Advisory: https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2 Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261 DSA: https://security-tracker.debian.org/tracker/DSA-4830-1 [Impact] Versions in Ubuntu right now: Hirsute: 1.8.4-2 Groovy: 1.8.2-1 Focal: 1.6.5-0ubuntu0.1 Bionic: 1.0.9-0ubuntu0.1 Affected versions: >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5 Patched versions: Expected to be >= 1.9.4, 1.8.x >= 1.8.5 There are also branches with patches for 1.6.x (Ubuntu 20.04), but nothing available yet for 1.0.x (Ubuntu 18.04). [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Simon McVittie discovered a bug in the flatpak-portal service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller- specified environment variables to non-sandboxed processes on the host system, and in particular to the flatpak run command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the flatpak run command, and use them to execute arbitrary code that is not in a sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1912498] Re: Preinstall some new essential raspi packages in the official raspi images
** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: ubuntu-meta (Ubuntu Focal) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912498 Title: Preinstall some new essential raspi packages in the official raspi images Status in livecd-rootfs package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Opinion Status in livecd-rootfs source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Bug description: [Impact] For 20.04.2, also as part of support for some new Pi variants (CM4, Pi400), we want to preinstall some new essential packages in our raspi images such as rpi-eeprom, raspberrypi-userland etc. This can be done in two possible ways. One is the 'old way', with a single change to livecd-rootfs adding the new packages. But what we'd like to propose this time is actually a more proper way, i.e. introducing device-specific raspi seeds and a raspi meta-package that would pull in all the needed dependencies. This way is better for the future, as if we decide we want to add new packages to existing raspi installations, we can do it easily by modifying the seeds and rebuilding meta. Currently we have no way like this. So the current approach includes changes in the following components: * The ubuntu and platform seeds (git branches) * ubuntu-meta package (adding ubuntu-server-raspi) * livecd-rootfs package (installing the raspi-server task) [Test Case] After accepting all the package into -proposed (and making sure the git seed changes are merged), run a raspi arm64 and armhf build. Check if the image boots. Confirm that the new images have the following seeded: rpi-eeprom, libraspberrypi-bin, flash-kernel, pi-bluetooth. Compare manifests between a normal, previous raspi image build and the one using seeds - check if nothing has been 'dropped'. Also, check if no other image builds have been affected and still build correctly, compare image manifests. [Where problems could occur] In its current form, as the update touches some livecd-rootfs auto/config paths, it's possible that a malformed cut-paste broke some edge case scenario, so it's good if other non-raspi builds are also checked for correctness. Seed changes are less likely to break anything, but manifests should be checked in case something got dropped by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913651] Re: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu-drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install
** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d 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/ubuntu-drivers-common/+bug/1913651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: Fix for Ghostscript 9.50 upstream bug needs to be back-ported
** Changed in: ghostscript (Ubuntu Focal) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: Fix for Ghostscript 9.50 upstream bug needs to be back-ported Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: New Bug description: Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Changed in: libx11 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: libx11 (Ubuntu Groovy) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: New Status in libx11 source package in Focal: New Status in libx11 source package in Groovy: New Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
This bug was fixed in the package flatpak - 1.6.5-0ubuntu0.2 --- flatpak (1.6.5-0ubuntu0.2) focal-security; urgency=medium * SECURITY UPDATE: Flatpak sandbox escape via spawn portal (LP: #1911473) - debian/patches/CVE-2021-21261-1.patch: tests: Add minimal version of "ok" helper. - debian/patches/CVE-2021-21261-2.patch: common: Add a backport of G_DBUS_METHOD_INVOCATION_HANDLED. - debian/patches/CVE-2021-21261-3.patch: run: Convert all environment variables into bwrap arguments. - debian/patches/CVE-2021-21261-4.patch: tests: Expand coverage for environment variable overrides. - debian/patches/CVE-2021-21261-5.patch: context: Add --env-fd option. - debian/patches/CVE-2021-21261-6.patch: portal: Convert --env in extra-args into --env-fd. - debian/patches/CVE-2021-21261-7.patch: tests: Exercise --env-fd. - debian/patches/CVE-2021-21261-8.patch: portal: Do not use caller-supplied variables in environment. - debian/patches/CVE-2021-21261-9.patch: tests: Assert that --env= does not go in `flatpak run` or bwrap environ. - CVE-2021-21261 -- Andrew Hayzen Wed, 13 Jan 2021 21:09:15 + ** Changed in: flatpak (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: flatpak (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: Fix Released Status in flatpak source package in Focal: Fix Released Status in flatpak source package in Groovy: Fix Released Status in flatpak source package in Hirsute: Fix Released Bug description: [Links] Upstream Advisory: https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2 Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261 DSA: https://security-tracker.debian.org/tracker/DSA-4830-1 [Impact] Versions in Ubuntu right now: Hirsute: 1.8.4-2 Groovy: 1.8.2-1 Focal: 1.6.5-0ubuntu0.1 Bionic: 1.0.9-0ubuntu0.1 Affected versions: >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5 Patched versions: Expected to be >= 1.9.4, 1.8.x >= 1.8.5 There are also branches with patches for 1.6.x (Ubuntu 20.04), but nothing available yet for 1.0.x (Ubuntu 18.04). [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Simon McVittie discovered a bug in the flatpak-portal service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller- specified environment variables to non-sandboxed processes on the host system, and in particular to the flatpak run command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the flatpak run command, and use them to execute arbitrary code that is not in a sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled
Thanks to @JayShauer's clue about evolution-alarm-notify, I finally managed to stop the phantom reminder popups that have plagued me since upgrading to Ubuntu 20.04. I did it by deleting this file (which hadn't been changed in years): ~/.local/share/evolution/calendar/system/calendar.ics BACKGROUND: I have not used evolution for years -- I use Thunderbird now -- but after recently upgrading to Ubuntu 20.04, I suddenly started getting alarm popups for events that are not on my Thunderbird calendar, but were on my evolution calendar several years ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1805666 Title: Evolution Alarm Notify continues pop-up reminders even though notifications disabled Status in evolution-data-server package in Ubuntu: Invalid Bug description: I have turned off notifications for evolution alarm notify in settings: https://i.imgur.com/BNlfgzA.png But I still get pop-ups from the evolution alarm notify app for calendar events: https://i.imgur.com/BBdr9gm.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 28 11:31:46 2018 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2018-07-14 (136 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Retrying with the release pocket version of network-manager it fails the same way https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210129_131945_c0965@/log.gz reassigning to systemd ** Package changed: network-manager (Ubuntu) => systemd (Ubuntu) ** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in systemd package in Ubuntu: New Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
In Ubuntu-Budgie the above trick doesn't solve the problem. I notice that Ubuntu Desktop is using gdm3 whereas Ubuntu Budgie is using lightdm. They are calling xorg with different arguments. So I reconfigured Budgie for gdm3 and, after creating the monitor.xml file, the flicker is gone. I hope, this helps to fix the problem in Budgie. Let me know, if I can do something else. Respective xorg command lines: Ubuntu-Budgie: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Ubuntu Desktop: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 Ubuntu-Budgie with gdm3: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
the next step to get a full fix and improved sound quality for voip calls over BT headset is coming in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914230] [NEW] [High priority] Screen keyboard doesn't display other languages characters, only english
Public bug reported: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914230 Title: [High priority] Screen keyboard doesn't display other languages characters, only english Status in gnome-shell package in Ubuntu: New Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914226] [NEW] Add option to enable screen-keyboard icon in dock
Public bug reported: Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Currently if enable it through universal access > screen keyboard then it makes quite annoying due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914226 Title: Add option to enable screen-keyboard icon in dock Status in gnome-shell package in Ubuntu: New Bug description: Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Currently if enable it through universal access > screen keyboard then it makes quite annoying due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914225] [NEW] Emoji button and pack for screen keyboard
Public bug reported: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) I aware that ubuntu offer "insert emoji" feature but it's not usable everywhere and keyboard shortcut method also the same. https://www.omgubuntu.co.uk/2018/06/use-emoji-linux-ubuntu-apps Furthermore, both methods cant use as force input to any text field or any limited environment as if it has built-in on screen keyboard I noticed there're few keyboard types but its annoying to use with every languages. (because such keyboards are one type and our common language keyboards are another so always has to switch) Samples in two steps https://gitee.com/mHatsune/chaya/raw/master/disk/emoji3.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/emoji4.jpg ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914225 Title: Emoji button and pack for screen keyboard Status in gnome-shell package in Ubuntu: New Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) I aware that ubuntu offer "insert emoji" feature but it's not usable everywhere and keyboard shortcut method also the same. https://www.omgubuntu.co.uk/2018/06/use-emoji-linux-ubuntu-apps Furthermore, both methods cant use as force input to any text field or any limited environment as if it has built-in on screen keyboard I noticed there're few keyboard types but its annoying to use with every languages. (because such keyboards are one type and our common language keyboards are another so always has to switch) Samples in two steps https://gitee.com/mHatsune/chaya/raw/master/disk/emoji3.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/emoji4.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914223] [NEW] Add screen keyboard modes (option to morph into several keyboards)
Public bug reported: Add screen keyboard modes (option to morph into several keyboards) Modes: Normal(default), Thumb and Standard (standard has all keys has on physical keyboard that doesn't even has on current ubuntu screen keyboard) https://gitee.com/mHatsune/chaya/raw/master/disk/modes.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/standard.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/thumb.jpg ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914223 Title: Add screen keyboard modes (option to morph into several keyboards) Status in gnome-shell package in Ubuntu: New Bug description: Add screen keyboard modes (option to morph into several keyboards) Modes: Normal(default), Thumb and Standard (standard has all keys has on physical keyboard that doesn't even has on current ubuntu screen keyboard) https://gitee.com/mHatsune/chaya/raw/master/disk/modes.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/standard.jpg https://gitee.com/mHatsune/chaya/raw/master/disk/thumb.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899893] Re: Ubuntu default screen keyboard to be movable
** Description changed: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) - 1. Add option for enable screen keyboard movable + Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg - - 2. Add screen keyboard modes (option to morph into several keyboards) - Normal(default), Thumb and Standard (standard has all keys has on physical keyboard) - https://gitlab.com/cloud.ch/bugs/-/raw/master/modes.jpg - https://gitlab.com/cloud.ch/bugs/-/raw/master/thumb.jpg - https://gitlab.com/cloud.ch/bugs/-/raw/master/standard.jpg - - 3. Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) - (Enable it through universal access > screen keyboard then it quite annoying due pop up often) - https://gitlab.com/cloud.ch/bugs/-/raw/master/screenkeyboard.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1899893 Title: Ubuntu default screen keyboard to be movable Status in gnome-shell package in Ubuntu: Triaged Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914220] Re: Dark mode for screen keyboard
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914220 Title: Dark mode for screen keyboard Status in gnome-shell package in Ubuntu: Invalid Bug description: Sample image: https://gitee.com/mHatsune/chaya/raw/master/disk/win-10 -keyboard-undocked.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver
I have uploaded the package which is applied atattach patch to my PPA. https://launchpad.net/~ikuya-fruitsbasket/+archive/ubuntu/scp It seems to fix this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Confirmed Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914220] [NEW] Dark mode for screen keyboard
Public bug reported: Sample image: https://gitee.com/mHatsune/chaya/raw/master/disk/win-10 -keyboard-undocked.jpg ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914220 Title: Dark mode for screen keyboard Status in gnome-shell package in Ubuntu: Invalid Bug description: Sample image: https://gitee.com/mHatsune/chaya/raw/master/disk/win-10 -keyboard-undocked.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
Have to add to the above: after first login, I rearranged the screens using the Display Settings. That creates a file ~/.config/monitors.xml. That file does some magic in preventing the flickering. However, it becomes effective only after logging out and logging in again, so I was mislead when testing the flickering above. Anyways: deleting the file, logging out, logging in (Xorg) and the flickering is back. Rearranging screens, logging out/in: flickering is gone. With this, I'll try on Ubuntu-Budgie again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
Firefox does do some things differently to what I would refer to as an "GTK app" so I don't count Firefox as a GTK app even though it uses some GTK. Using Xwayland may be a common factor but that's probably more of a correlation than causation. Anything that's not yet ported to native Wayland will fall into the same category and end up using Xwayland. -- 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/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1831039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
Hi, first to say: I've been testing Ubuntu-Budgie. There is no option to run on Wayland. So I downloaded (2021-02-02) and installed Ubuntu 21.04 Desktop to perform the test and found some surprising results: 1. fresh installation, running on Xorg: the flickering is clearly visible. In fact, the cursor flickers, if anywhere on the screen some redrawing happens. To reproduce: open Term. A slight flickering is visible whenever the console cursor is disappearing and reappearing. This is also the case outside the Term window. Increase the effect by launching Firefox and browse to cnn.com. While opening the page, a lot of redrawing is happening (the little bullet in the tab, some line in the bottom about loading, and the many items on the page. During the pay load, cursor is flickering anywhere on the screen. 2. logout and login, this time on Wayland: No such effect. 3. logout and login, again on Xorg, again no such effect! Btw.: I cancelled to install updates to keep a stable environment, so just the version as indicated above. If you have any idea, how logging in on Wayland cured this effect (reinstalled two times to be sure), I might be able to check on Ubuntu- Budgie (where I can't simply select Wayland). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubun
[Desktop-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
Firefox uses GTK, but in a Wayland session it runs on XWayland, the same for Qt apps and Chrome, they run on XWayland in a Wayland session. That's a common factor. -- 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/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1831039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Yes this bug is about the log messages only, not about it causing any problems. It's not impossible the two bugs are related but I would really need to investigate your freezes first to be sure. Just as I do for multiple such bug reports every day. Instead of clouding this bug with potentially unrelated comments please open a new bug about your freezes by running: ubuntu-bug gnome-shell and I will investigate it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Daniel, To be honest, I'm not quite sure what this ticket is all about. If it's just that people see these lines in their log, then surely, it's not worth having an open ticket about. On the other hand, I'm saying that I have been investigating this for two weeks, and I can say with 95% confidence that when my laptop freezes, the very last thing I see in my syslog, and in journalctl is a spam output of these lines. If you do a search for "keysym, ubuntu, freeze, dell, laptop", I'm pretty sure you'll be down a rabbit hole with many other people reporting similar freezes (e.g. https://itectec.com/ubuntu/ubuntu- ubuntu-19-04-stops-working/). There's also an issue in gnome/mutter that looks like it may be closer to the origin, but I'm not sure at this point (https://gitlab.gnome.org/GNOME/mutter/-/issues/606). Again, I'm just not sure. So, other than opening a vague ticket, do you have any suggestions as to where I can track this bug to the origin. Like I said, it's really killing our company's experience (we've got several new laptops running 20.04.1 LTS and none of us are using these machines for simple browsing -- in other words, it's critical that our work is not randomly lost due to a freeze). Also, note, I noticed this bug only once with the oem kernel (whereas it happened multiple times with the generic kernel). And also, I caught it once when I was explicitly looking for it to happen when I did a key press of one of the multimedia buttons (two key presses). ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #606 https://gitlab.gnome.org/GNOME/mutter/-/issues/606 -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
