[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Hello I've verified this -proposed pkg on my local. #2 on description working fine. xtrusia@ubuntu:~$ dpkg -l | grep network-manager ii network-manager1.10.6-2ubuntu1.4 amd64network management framework (daemon and userspace tools) ii network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1.2 all NetworkManager configuration to enable connectivity checking ii network-manager-gnome 1.8.10-2ubuntu3 amd64network management framework (GNOME frontend) ii network-manager-pptp 1.2.6-1 amd64network management framework (PPTP plugin core) ii network-manager-pptp-gnome 1.2.6-1 amd64network management framework (PPTP plugin GNOME GUI) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode
[Desktop-packages] [Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate
I can confirm 3.35.92-1 fixed it too. ** Changed in: gnome-system-monitor (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1862478 Title: gnome-system-monitor can't measure network transfer rate Status in gnome-system-monitor package in Ubuntu: Fix Released Bug description: It started happening since I updated today and version 3.35.90 got installed. It had been working normally before that. The total number of bytes received seems to be accurate (I really downloaded a bit over 1GB of data when the screenshot was taken), but the transfer rate is not being measured accurately. The real transfer rate when the screenshot was taken was around 10 MB/s while it shows just a few bytes/second. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 8 22:29:41 2020 InstallationDate: Installed on 2019-05-15 (269 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I see a lot of comments about Libre and just wanted to add that it is not an office issue. This is for sure a copy issue. It just brings a lot of comments about office stuff because there is text being copied and pasted. Truth is the copy function only seems to work every other time after the first time. You can copy some text, paste it, copy some more, and when you paste it will be the first text again. Go back copy new text again, paste it and it is the new text, repeat... In some desktop environments it pastes nothing at all instead of a duplicate. I am guessing this is because some DE's empty the clipboard after a paste instead of holding until overwritten? Pressing Ctrl+C twice every time will allow pasting of the text. It's the copy function that's not working. I am fuzzy about why it does not effect everything. But in my case I noticed this issue while trying to copy text from a PDF in Master PDF Editor and also Foxit Reader and paste to anything else. Text editor, browser, Libre Calc, etc. I tested from the Ubuntu Budgie 2020-03-02 Daily build of 20.04 and the issue is still present. I also think it is worth mentioning that I tested from Ubuntu Mate 19.10 and the problem isn't present. I hope that helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate
On Ubuntu 20.04 gnome-system-monitor (3.35.92-1) solved the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1862478 Title: gnome-system-monitor can't measure network transfer rate Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: It started happening since I updated today and version 3.35.90 got installed. It had been working normally before that. The total number of bytes received seems to be accurate (I really downloaded a bit over 1GB of data when the screenshot was taken), but the transfer rate is not being measured accurately. The real transfer rate when the screenshot was taken was around 10 MB/s while it shows just a few bytes/second. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 8 22:29:41 2020 InstallationDate: Installed on 2019-05-15 (269 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865976] [NEW] horrible noises
Public bug reported: My system has, on more than one occasion, spontaneously begun making horrible noises. Don't have to be doing anything that generates audio. Orca wasn't even turned on and was not set to use cicero. The previous time this happened, I was able to trace it to speech dispatcher/cicero. pavucontrol was helpful.On the most recent occasion, I killed sd_cicero and the noise stopped. The noise sounded like a stale ring buffer was suddenly being played continuously. The contents of which were extremely unpleasant. sudo apt-get remove speech-dispatcher-cicero cicero dpkg -l | fgrep -i speech-dispatcher ii speech-dispatcher 0.8.8-1ubuntu1 amd64Common interface to speech synthesizers ii speech-dispatcher-audio-plugins:amd64 0.8.8-1ubuntu1 amd64Speech Dispatcher: Audio output plugins ii speech-dispatcher-espeak-ng 0.8.8-1ubuntu1 amd64Speech Dispatcher: Espeak-ng output module ii speech-dispatcher-festival 0.8.8-1ubuntu1 amd64Festival support for Speech Dispatcher ii speech-dispatcher-flite 0.8.8-1ubuntu1 amd64Speech Dispatcher: Flite output module ii speech-dispatcher-pico 0.8.8-2 amd64Speech Dispatcher: Pico output module ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: speech-dispatcher-cicero 0.8.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 00:26:38 2020 InstallationDate: Installed on 2019-05-02 (306 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1865976 Title: horrible noises Status in speech-dispatcher package in Ubuntu: New Bug description: My system has, on more than one occasion, spontaneously begun making horrible noises. Don't have to be doing anything that generates audio. Orca wasn't even turned on and was not set to use cicero. The previous time this happened, I was able to trace it to speech dispatcher/cicero. pavucontrol was helpful.On the most recent occasion, I killed sd_cicero and the noise stopped. The noise sounded like a stale ring buffer was suddenly being played continuously. The contents of which were extremely unpleasant. sudo apt-get remove speech-dispatcher-cicero cicero dpkg -l | fgrep -i speech-dispatcher ii speech-dispatcher 0.8.8-1ubuntu1 amd64Common interface to speech synthesizers ii speech-dispatcher-audio-plugins:amd64 0.8.8-1ubuntu1 amd64Speech Dispatcher: Audio output plugins ii speech-dispatcher-espeak-ng 0.8.8-1ubuntu1 amd64Speech Dispatcher: Espeak-ng output module ii speech-dispatcher-festival 0.8.8-1ubuntu1 amd64Festival support for Speech Dispatcher ii speech-dispatcher-flite 0.8.8-1ubuntu1 amd64Speech Dispatcher: Flite output module ii speech-dispatcher-pico 0.8.8-2 amd64Speech Dispatcher: Pico output module ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: speech-dispatcher-cicero 0.8.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 00:26:38 2020 InstallationDate: Installed on 2019-05-02 (306 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePa
[Desktop-packages] [Bug 1865975] [NEW] Blank 'Updates' screen
Public bug reported: The software updater keeps interrupting me with "updates available" and then shows me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 06:40:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2902 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "Selection_450.png" https://bugs.launchpad.net/bugs/1865975/+attachment/5333259/+files/Selection_450.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1865975 Title: Blank 'Updates' screen Status in gnome-software package in Ubuntu: New Bug description: The software updater keeps interrupting me with "updates available" and then shows me a blank screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 06:40:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2902 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- 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/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering" chapter of the README, and the extension specifications: https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt https://www.khronos.org/registry/OpenGL/extensions/NV/NV_gpu_multicast.tx
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
This is personally impacting my ability to use Chromium to run the F5 SSL VPN, which uses the f5-epi and f5-vpn schemes. There needs to be a way for individual users to add to the whitelist. Adding more schemes like "apt" is just making the issue less painful. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865963] [NEW] Screen not repainting dirty regions on some apps (vmwgfx_scanout_update: failed to send dirty (-22, Invalid argument))
Public bug reported: When using gvim and some other apps, regions of windows will sometimes not repaint until the window is moved or otherwise interacted with. Someone posted a workaround patch on the upstream gitlab and it seems to fix the issue for me. Upstream bug is here: https://gitlab.freedesktop.org/xorg/driver/xf86 -video-vmware/issues/8 ** Affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Patch from upstream bug" https://bugs.launchpad.net/bugs/1865963/+attachment/5333230/+files/vmwgfx-dirty-union.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1865963 Title: Screen not repainting dirty regions on some apps (vmwgfx_scanout_update: failed to send dirty (-22, Invalid argument)) Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: When using gvim and some other apps, regions of windows will sometimes not repaint until the window is moved or otherwise interacted with. Someone posted a workaround patch on the upstream gitlab and it seems to fix the issue for me. Upstream bug is here: https://gitlab.freedesktop.org/xorg/driver/xf86 -video-vmware/issues/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1865963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
Please file an upstream bug at intel graphics upstream: https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861746] Re: moving the "Account Settings" window makes the main window shrink and move along in the background
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1861746 Title: moving the "Account Settings" window makes the main window shrink and move along in the background Status in thunderbird package in Ubuntu: Confirmed Bug description: I start my thunderbird and maximize the main window. Then I open "Account Settings". This shows the new settings window that is smaller than the main window (see screenshot "before.png"). This is fine just like that. But when I start moving the settings window around (by clicking the top window bar), the main window is being resized to a very small size, such that it is not visible behind the settings window. Moreover, it seems to move along with the settings window. When I close the settings, I can see the very small main window (see screenshot "after.png"). I actually don't think this is a thunderbird problem, it is probably something more general. I remember having a similar issue with the LibreOffice options in Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.4.2+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BuildID: 20200123140255 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 4 00:33:14 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-02-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.2/20200123140255 (In use) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780680] Re: Older version in bionic than in xenial
** Changed in: linux-meta-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta-gcp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780680 Title: Older version in bionic than in xenial Status in fuse-umfuse-ext2 package in Ubuntu: New Status in libclc package in Ubuntu: Won't Fix Status in libdrm package in Ubuntu: Won't Fix Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-meta-gcp package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in patch package in Ubuntu: Invalid Status in python-pyvmomi package in Ubuntu: Invalid Status in snapcraft package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Bug description: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1 python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1 snapcraft 2.42+17.10 < 2.42.1 wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1 Some of these are older in bionic than in xenial too. Shouldn’t there be an automated check for this? (See also: bug 1780679, bug 1780681.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865907] Re: Loading IM context type 'ibus' failed
Symptom unreproducible after glib upgraded to proposed libglib2.0-0 /focal-proposed,now 2.64.0-1 amd64 [installed]. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865907 Title: Loading IM context type 'ibus' failed Status in glib2.0 package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Regression issue caused by recent system updates on Ubuntu 20.04 Focal Fossa (development branch) Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865937] Re: Bluetooth not working with Realtek RTL8821CE
** Package changed: ubuntu => udisks2 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1865937 Title: Bluetooth not working with Realtek RTL8821CE Status in udisks2 package in Ubuntu: New Bug description: ubuntu 18.04 LTS does not detect me bluetooth with Realtek RTL8821CE ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules Date: Tue Mar 3 22:09:48 2020 InstallationDate: Installed on 2020-02-24 (8 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5321 Quanta Computer, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=dc3879b6-59db-4668-b7e8-ff223e1f5c1b ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6EC36EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1865937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865937] [NEW] Bluetooth not working with Realtek RTL8821CE
You have been subscribed to a public bug: ubuntu 18.04 LTS does not detect me bluetooth with Realtek RTL8821CE ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules Date: Tue Mar 3 22:09:48 2020 InstallationDate: Installed on 2020-02-24 (8 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5321 Quanta Computer, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=dc3879b6-59db-4668-b7e8-ff223e1f5c1b ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6EC36EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Bluetooth not working with Realtek RTL8821CE https://bugs.launchpad.net/bugs/1865937 You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 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 1865942] [NEW] delete key doesn't move desktop files to trash
Public bug reported: When I select an icon in my desktop, be it a folder or file, the "delete" key doesn't do anything with it anymore. I was expecting it to be moved to the trash folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 18:22:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (142 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-30 (32 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Tags added: champagne -- 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/1865942 Title: delete key doesn't move desktop files to trash Status in gnome-shell package in Ubuntu: New Bug description: When I select an icon in my desktop, be it a folder or file, the "delete" key doesn't do anything with it anymore. I was expecting it to be moved to the trash folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 18:22:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (142 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-30 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
> It appears we would need a new upstream bug to track this because the old one didn't go anywhere. This is not true. The old one did go somewhere: It examined the behavior and clearly concluded that upstream gnome-terminal is NOT buggy here, it never was. It's one of the Ubuntu patches that introduces the bug. This conclusion was also stated in this thread here. Could you please clarify how you expect upstream gnome-terminal to fix this situation? Meanwhile, this bug is almost 3 years old, and I haven't seen any worthwile comment from any Ubuntu developer trying to track down which of its patches, and which part within that is the culprit. Or if you believe that upstream gnome-terminal is indeed buggy, this bug just doesn't happen to trigger anywhere else, except with your perfect innocent patches, then this claim should be justified with technical arguments, something I haven't seen in this thread yet. And I can't help to notice that this is not the only issue where Ubuntu introduces a regression to the overall gnome-terminal user experience, and then really doesn't care about fixing it. Bug 1770507 is another prominent example, you guys broke something during the feature freeze period(!) of the previous LTS, and still til this day haven't cared about fixing. I'm sad and disappointed to see that the software I've been co- developing for years, putting my passion, heart, and lots and lots of time into, is broken in multiple ways by perhaps the most popular Linux distribution, and its developers just don't care. I don't even know what to think about you pointing fingers at us. Instead, maybe could you Ubuntu devs finally please, pretty please get yourself together and fix at the very least these two bugs that YOU introduced, in time for the just-around-the-corner LTS release? If simply by dropping the patches that introduces the bugs, along with then dropping whatever features those patches add, so it be. Thanks! I firmly believe that Ubuntu should revise its bug prioritizing policy, and handle with much-much higher priority if one of its changes introduces a regression from mainstream. It should be something like: if a regression is found, and not fixed within a week, the patch is automatically dropped. Think about it... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865943] [NEW] Dran and drop to desktop area doesn't work
Public bug reported: If I have a folder window open, and drag a file from it into the desktop area, that is somehow forbidden and the icon just moves back to the folder where it came from, in a "moving" animation. It's almost as if I didn't have filesystem permissions to move it to the desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.35.92-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 18:25:07 2020 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.window-state' b'initial-size' b'(972, 469)' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-13 (142 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-01-30 (32 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug chamgagne focal ** Tags added: chamgagne -- 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/1865943 Title: Dran and drop to desktop area doesn't work Status in nautilus package in Ubuntu: New Bug description: If I have a folder window open, and drag a file from it into the desktop area, that is somehow forbidden and the icon just moves back to the folder where it came from, in a "moving" animation. It's almost as if I didn't have filesystem permissions to move it to the desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.35.92-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 18:25:07 2020 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.window-state' b'initial-size' b'(972, 469)' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-13 (142 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-01-30 (32 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1865943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865410] Re: Gnome Shell freeze
The only crashes I can find on my system have all been uploaded already. There also, doesn't seem to be anything related to firefox (the browser in use at the time of the crash) or gnome-shell. However, there are some recent crashes: (all on 2020-02-27) - https://errors.ubuntu.com/oops/d115f75a-59c7-11ea-a9e9-fa163e983629 - https://errors.ubuntu.com/oops/95c6d304-59c7-11ea-a0d9-fa163e6cac46 - https://errors.ubuntu.com/oops/6753dda8-59c4-11ea-97d0-fa163e102db1 -- 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/1865410 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-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/gnome-shell/+bug/1865410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : h
[Desktop-packages] [Bug 1865936] [NEW] gnome-calculator (snap) fails on 19.10
Public bug reported: Hello -- This is a clean Ubuntu 10.10 install onto a new disk. For many days now I've been clicking on the calculator. It just doesn't work. No message or error report. I am looking for an alternative caclulator to install. Today I tried to run the calculator from the command line --It failed but at least it displayed some information about the error that stops it working. See below: $ gnome-calculator 2020/03/04 07:34:57.038784 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/Moort/home/william/.Xauthority" cannot create user data directory: /home/william/snap/gnome-calculator/544: Not a directory $ whereis gnome-calculator gnome-calculator: /snap/bin/gnome-calculator $ ll /home/william/snap/gnome-calculator/ total 20 drwxr-xr-x 5 william william 4096 Feb 6 03:07 ./ drwxr-xr-x 9 william william 4096 Dec 14 00:25 ../ drwxr-xr-x 2 william william 4096 Aug 29 2019 536/ drwxr-xr-x 2 william william 4096 Aug 29 2019 544/ drwxr-xr-x 2 william william 4096 Aug 29 2019 common/ lrwxrwxrwx 1 william william3 Feb 6 03:07 current -> 544/ As you can see the requisite directory is There! I am sad to report that this kind of error has been seen before on 19.04 I had hoped eventually someone would correct this -- There is a systemic failure here makins snaps. None of them appear to work with my install. My home directory is on Another disk. This is pretty much standard practice in my work place. I recommend this problem be fixed for ALL snaps. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1865936 Title: gnome-calculator (snap) fails on 19.10 Status in gnome-calculator package in Ubuntu: New Bug description: Hello -- This is a clean Ubuntu 10.10 install onto a new disk. For many days now I've been clicking on the calculator. It just doesn't work. No message or error report. I am looking for an alternative caclulator to install. Today I tried to run the calculator from the command line --It failed but at least it displayed some information about the error that stops it working. See below: $ gnome-calculator 2020/03/04 07:34:57.038784 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/Moort/home/william/.Xauthority" cannot create user data directory: /home/william/snap/gnome-calculator/544: Not a directory $ whereis gnome-calculator gnome-calculator: /snap/bin/gnome-calculator $ ll /home/william/snap/gnome-calculator/ total 20 drwxr-xr-x 5 william william 4096 Feb 6 03:07 ./ drwxr-xr-x 9 william william 4096 Dec 14 00:25 ../ drwxr-xr-x 2 william william 4096 Aug 29 2019 536/ drwxr-xr-x 2 william william 4096 Aug 29 2019 544/ drwxr-xr-x 2 william william 4096 Aug 29 2019 common/ lrwxrwxrwx 1 william william3 Feb 6 03:07 current -> 544/ As you can see the requisite directory is There! I am sad to report that this kind of error has been seen before on 19.04 I had hoped eventually someone would correct this -- There is a systemic failure here makins snaps. None of them appear to work with my install. My home directory is on Another disk. This is pretty much standard practice in my work place. I recommend this problem be fixed for ALL snaps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1865936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797678] Re: Printing stops with Status as "Idle - Filter failed"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1797678 Title: Printing stops with Status as "Idle - Filter failed" Status in cups package in Ubuntu: Confirmed Bug description: This happened after an upgrade from Xenial to Bionic on this Barebones PC. Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem did not occur. It also occurred with a clean install on another Barebones PC, but was fixed by installing package hplip. I've tried installing hplip on this PC but to no effect. PS I don't know if the problem is with CUPS or hplip or another package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 13 09:10:56 2018 InstallationDate: Installed on 2018-02-09 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Deskjet_2540_series_527711_: ipp://HPD0BF9C527711.local:631/ipp/print device for HP-Deskjet-2540-series: dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711 device for Samsung-SCX-472x: socket://192.168.101.20:9100 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', '/etc/cups/ppd/Samsung-SCX-472x.ppd', '/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796948] Re: cups gives back "filter failed" for all trials to print to any printer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1796948 Title: cups gives back "filter failed" for all trials to print to any printer Status in cups package in Ubuntu: Confirmed Bug description: Any printing attempt to any printer is quitted with "filter failed" by cups. Even for test pages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:21:26 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1796948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I confirm the bug The bug applies to all the distros I have tried: Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc. I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc. It's a general problem, not just of mutter and Gnome The bug exists only with Mesa and Modesetting, if you install xf86-video-intel (Arch and Manjaro), the mouse does not lock but the mouse flashes and multiplies Also, when there is a lock, I noticed that the left side of the screen "unlocks", but the mouse starts flashing (with Mesa and Modesetting) It happens especially when I watch videos in full screen or at 60fps on Youtube Intel Celeron J3160, with Hdmi (I can't try with VGA) Edit: yesterday I tried to download and boot through USB Ubuntu 14.04.6 unity 64 bit ... and surprise: the problem does not exist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865907] Re: Loading IM context type 'ibus' failed
Thanks for your report! I could reproduce the problem, which is a bit weird because IBus was updated yesterday and the IBus input methods I tested worked fine then... Anyway, I see in the error message: "GLib version too old". So I upgraded the libglib2.0-* packages to version 2.64.0-1 (from focal- proposed) and that fixed the issue. So it looks like we just need to be patient and wait for libglib2.0-* to migrate to focal-release. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed ** Changed in: ibus (Ubuntu) Importance: Undecided => High ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865907 Title: Loading IM context type 'ibus' failed Status in glib2.0 package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Regression issue caused by recent system updates on Ubuntu 20.04 Focal Fossa (development branch) Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864071] Autopkgtest regression report (libreoffice/1:6.3.5-0ubuntu0.19.10.1)
All autopkgtests for the newly accepted libreoffice (1:6.3.5-0ubuntu0.19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: apparmor/2.13.3-5ubuntu1 (amd64) natbraille/unknown (amd64, i386) parlatype/unknown (i386) lloconv/unknown (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#libreoffice [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1864071 Title: [SRU] libreoffice 6.3.5 for eoan Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Eoan: Fix Committed Bug description: [Impact] * LibreOffice 6.3.5 is in its fifth bugfix release of the 6.3 line. For a list of fixed bugs compared to 6.3.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.3.5/RC2#List_of_fixed_bugs (that's a total of 84 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 84 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1864071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865910] [NEW] package system-config-printer-common 1.5.12-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote system-config-printer-common, o script post-in
Public bug reported: It just bugged. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: system-config-printer-common 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Mon Mar 2 16:19:25 2020 ErrorMessage: o subprocesso instalado, do pacote system-config-printer-common, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Lpstat: device for Brother_DCP_L2540DW_series: implicitclass://Brother_DCP_L2540DW_series/ device for HP_LaserJet_M1536dnf_MFP_0263D0_: implicitclass://HP_LaserJet_M1536dnf_MFP_0263D0_/ device for Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_: implicitclass://Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_/ MachineType: Hewlett-Packard HP Z620 Workstation PackageArchitecture: all Papersize: a4 PpdFiles: Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_: Samsung M332x 382x 402x Series, driverless, cups-filters 1.27.2 Brother_DCP_L2540DW_series: Brother DCP-L2540DW series, driverless, cups-filters 1.27.2 HP_LaserJet_M1536dnf_MFP_0263D0_: HP LaserJet M1536dnf MFP, driverless, cups-filters 1.27.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=9a0a521e-567e-43b6-b4ac-e9503050a563 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: system-config-printer Title: package system-config-printer-common 1.5.12-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote system-config-printer-common, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.50 dmi.board.asset.tag: BRG340F0QQ dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: BRG340F0QQ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.50:bd08/15/2013:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.product.sku: C3X82EC#AC4 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.dbus-1.system.d.com.redhat.NewPrinterNotification.conf: 2020-02-24T18:15:11 mtime.conffile..etc.dbus-1.system.d.com.redhat.PrinterDriversInstaller.conf: 2020-02-24T18:15:11 ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1865910 Title: package system-config-printer-common 1.5.12-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote system-config- printer-common, o script post-installation retornou erro do status de saída 1 Status in system-config-printer package in Ubuntu: New Bug description: It just bugged. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: system-config-printer-common 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Mon Mar 2 16:19:25 2020 ErrorMessage: o subprocesso instalado, do pacote system-config-printer-common, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Lpstat: device for Brother_DCP_L2540DW_series: implicitclass://Brother_DCP_L2540DW_series/ device for HP_LaserJet_M1536dnf_MFP_0263D0_: implicitclass://HP_LaserJet_M1536dnf_MFP_0263D0_/ device for Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_: implicitclass://Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_/ MachineType: Hewlett-Packard HP Z620 Workstation PackageArchitecture: all Papersize: a4 PpdFiles: Samsung_M332x_382x_402x_Series_SEC30CDA7CB4B83_: Samsung M332x 382x 402x Series, driverless, cups-filters 1.27.2 Brother_DCP_L2540DW_series: Brother DCP-L2540DW series, driverless, cups-filters 1.27.2 HP_LaserJet_M1536dnf_MFP_0263D0_: HP LaserJet M1536dnf MFP, driverless, cups-filters 1.27.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=9a0a521e-567e-43b6-b4ac-e9503050a563 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubun
[Desktop-packages] [Bug 1865865] Re: Icon spring animation starts/ends in the wrong location (near the top of the dock)
** Changed in: gnome-shell (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1865865 Title: Icon spring animation starts/ends in the wrong location (near the top of the dock) Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Icon spring animation starts/ends in the wrong location (near the top of the dock). This only seems to happen using the Ubuntu Dock with Gnome Shell 3.35. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 12:06:44 2020 InstallationDate: Installed on 2020-02-25 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865907] Re: Loading IM context type 'ibus' failed
** Description changed: + Regression issue caused by recent system updates on Ubuntu 20.04 Focal + Fossa (development branch) + Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 - current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865907 Title: Loading IM context type 'ibus' failed Status in ibus package in Ubuntu: New Bug description: Regression issue caused by recent system updates on Ubuntu 20.04 Focal Fossa (development branch) Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864577] Re: Ubuntu logo is not displayed in the 'About' Pane
This bug was fixed in the package gnome-control-center - 1:3.35.91-0ubuntu3 --- gnome-control-center (1:3.35.91-0ubuntu3) focal; urgency=medium * debian/patches/0003-info-overview-Use-the-Ubuntu-logo-prominently.patch: - Fix Ubuntu logo not showing in about panel (LP: #1864577) -- Robert Ancell Tue, 03 Mar 2020 13:55:58 +0100 ** Changed in: gnome-control-center (Ubuntu Focal) 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/1864577 Title: Ubuntu logo is not displayed in the 'About' Pane Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: On Focal, if you go to the 'About' pane in gnome-control-center, a large GNOME icon is displayed. On previous releases, usually an Ubuntu logo is displayed instead. Is this change intentional? Or did upstream GNOME change a file name or something? Attached is a screenshot. $ sudo apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu1 Candidate: 1:3.35.91-0ubuntu1 Version table: *** 1:3.35.91-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1864577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865907] [NEW] Loading IM context type 'ibus' failed
Public bug reported: Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865907 Title: Loading IM context type 'ibus' failed Status in ibus package in Ubuntu: New Bug description: Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865896] Re: totem segfaults on ubuntu-mate 18.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1865896 Title: totem segfaults on ubuntu-mate 18.04 Status in totem package in Ubuntu: Incomplete Bug description: Totem crashes on launch along with the desktop/Xorg. BTW I am not using any dm but only managing my desktop with openbox wm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 3 21:43:10 2020 InstallationDate: Installed on 2018-05-11 (661 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1865896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865896] [NEW] totem segfaults on ubuntu-mate 18.04
Public bug reported: Totem crashes on launch along with the desktop/Xorg. BTW I am not using any dm but only managing my desktop with openbox wm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 3 21:43:10 2020 InstallationDate: Installed on 2018-05-11 (661 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "totem.log" https://bugs.launchpad.net/bugs/1865896/+attachment/5333055/+files/totem.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1865896 Title: totem segfaults on ubuntu-mate 18.04 Status in totem package in Ubuntu: New Bug description: Totem crashes on launch along with the desktop/Xorg. BTW I am not using any dm but only managing my desktop with openbox wm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 3 21:43:10 2020 InstallationDate: Installed on 2018-05-11 (661 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1865896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode
In Ubuntu 18.04 LTS this is still an issue, the described behaviour still occurs exactly as described. Probably this is expected with your smartphone but absolutely not from your Laptop! -- 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/1767542 Title: Turning off WiFi enables Airplane mode Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Turning off the WiFi from the top right control enables Airplane mode (see screenshots). Also after turning off airplane mode, the Wi-Fi is not turned back on, rather the Bluetooth is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 17:46:34 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461260] Re: No sound was heard when running System Testing on a new Intel Apple iMac
** Changed in: linux-backports-modules-2.6.31 (Ubuntu) Status: Confirmed => Won't Fix -- 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/461260 Title: No sound was heard when running System Testing on a new Intel Apple iMac Status in alsa-driver package in Ubuntu: Confirmed Status in linux-backports-modules-2.6.31 package in Ubuntu: Won't Fix Bug description: I preformed a new install, updated, and upgraded Karmic Beta on a new Intel Apple iMac. No non-free drivers are in use. I ran System Testing and heard no sound. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scottmaccal 1690 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x5060 irq 20' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,106b3c00,00100103' Controls : 29 Simple ctrls : 15 CheckboxCommand: alsa_record_playback CheckboxTest: alsa_record_playback_alternates Date: Mon Oct 26 13:16:59 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3) Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/461260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
@Marc: Please see my short conversation with Alex on IRC:
https://irclogs.ubuntu.com/2020/02/11/%23ubuntu-desktop.html
I will ask Laney about the current status.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865444] Re: [radeon] Dual monitor loop login
Okay after some experimenting I found switching to Wayland brings up both monitors after login But no mouse pointer -- 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/1865444 Title: [radeon] Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864071] Re: [SRU] libreoffice 6.3.5 for eoan
** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Committed -- 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/1864071 Title: [SRU] libreoffice 6.3.5 for eoan Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Eoan: Fix Committed Bug description: [Impact] * LibreOffice 6.3.5 is in its fifth bugfix release of the 6.3 line. For a list of fixed bugs compared to 6.3.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.3.5/RC2#List_of_fixed_bugs (that's a total of 84 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 84 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1864071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
Is anyone actively working on the glib2.0 SRUs? We are blocked on them
for our ibus security update...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.39 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#network-manager [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-
[Desktop-packages] [Bug 1850267] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.39 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#network-manager [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [impact] test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] The d/t/control file 'nm' test section, for bionic, needs to include dnsmasq-base in its dep list. disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855009] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.39 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#network-manager [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
It appears we would need a new upstream bug to track this because the old one didn't go anywhere. Please create one in: https://gitlab.gnome.org/GNOME/gnome-terminal/issues or https://gitlab.gnome.org/GNOME/gtk/issues and then tell us the URL. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()
On 2020-03-03 14:33, Mel wrote: > Hi Gunnar have updated and no further crash reports > On ibis Great! Closing then. Please feel free to submit a new bug report would the issue re-appear. ** Changed in: ibus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865857 Title: ibus-x11 crashed with SIGABRT in __open_nocancel() Status in ibus package in Ubuntu: Invalid Bug description: possible Xorg crashing ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.21-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:24:27 2020 ExecutablePath: /usr/lib/ibus/ibus-x11 ExecutableTimestamp: 1581612711 InstallationDate: Installed on 2020-02-29 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcCwd: /home/mel ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45 __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, posix_mode=, prot=prot@entry=438, read_write=8, is32not64=) at fileops.c:186 _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281 __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 "/etc/localtime") at iofopen.c:75 _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()
Hi Gunnar have updated and no further crash reports On ibis Still dealing with previous bug on dual monitor login I had this problem on 18.04 and found no resolve -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865857 Title: ibus-x11 crashed with SIGABRT in __open_nocancel() Status in ibus package in Ubuntu: Incomplete Bug description: possible Xorg crashing ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.21-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:24:27 2020 ExecutablePath: /usr/lib/ibus/ibus-x11 ExecutableTimestamp: 1581612711 InstallationDate: Installed on 2020-02-29 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcCwd: /home/mel ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45 __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, posix_mode=, prot=prot@entry=438, read_write=8, is32not64=) at fileops.c:186 _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281 __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 "/etc/localtime") at iofopen.c:75 _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
What's the current status of this bug? Where is the fix? One of my report is made duplicate to this bug but I think this is much older. I'm using 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Please find some solution for this bug ** Changed in: alsa-driver (Ubuntu) Status: Expired => Incomplete ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864577] Re: Ubuntu logo is not displayed in the 'About' Pane
** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => Fix Committed -- 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/1864577 Title: Ubuntu logo is not displayed in the 'About' Pane Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Committed Bug description: On Focal, if you go to the 'About' pane in gnome-control-center, a large GNOME icon is displayed. On previous releases, usually an Ubuntu logo is displayed instead. Is this change intentional? Or did upstream GNOME change a file name or something? Attached is a screenshot. $ sudo apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu1 Candidate: 1:3.35.91-0ubuntu1 Version table: *** 1:3.35.91-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1864577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Changed in: pulseaudio (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()
IBus was recently upgraded to 1.5.22-1~exp1ubuntu1. Can you please update the packages on your system (including IBus): sudo apt update sudo apt upgrade and let us know if the issue is still present. ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865857 Title: ibus-x11 crashed with SIGABRT in __open_nocancel() Status in ibus package in Ubuntu: Incomplete Bug description: possible Xorg crashing ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.21-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:24:27 2020 ExecutablePath: /usr/lib/ibus/ibus-x11 ExecutableTimestamp: 1581612711 InstallationDate: Installed on 2020-02-29 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcCwd: /home/mel ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45 __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, posix_mode=, prot=prot@entry=438, read_write=8, is32not64=) at fileops.c:186 _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281 __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 "/etc/localtime") at iofopen.c:75 _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865871] Re: appearance setting view shows thick border
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1865871 Title: appearance setting view shows thick border Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) 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/1865871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865871] Re: appearance setting view shows thick border
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1865871 Title: appearance setting view shows thick border Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) 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/1865871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865870] Re: xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1865870 Title: xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine after that. lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 uname -a Linux 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx graphics: lshw -c video *-display Beschreibung: VGA compatible controller Produkt: TU106M [GeForce RTX 2060 Mobile] Hersteller: NVIDIA Corporation Physische ID: 0 Bus-Informationen: pci@:01:00.0 Version: a1 Breite: 64 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom Konfiguration: driver=nvidia latency=0 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07 *-display Beschreibung: VGA compatible controller Produkt: UHD Graphics 630 (Mobile) Hersteller: Intel Corporation Physische ID: 2 Bus-Informationen: pci@:00:02.0 Version: 00 Breite: 64 bits Takt: 33MHz Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom Konfiguration: driver=i915 latency=0 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff ioport:5000(Größe=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1865870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865871] [NEW] appearance setting view shows thick border
Public bug reported: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "appearance setting picture" https://bugs.launchpad.net/bugs/1865871/+attachment/5333031/+files/appearance-setting.png -- 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/1865871 Title: appearance setting view shows thick border Status in gnome-control-center package in Ubuntu: New Bug description: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) 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/1865871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865870] Re: xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
** Attachment added: "Xorg.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1865870/+attachment/5333030/+files/Xorg.log -- 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/1865870 Title: xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" Status in xorg-server package in Ubuntu: New Bug description: After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine after that. lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 uname -a Linux 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx graphics: lshw -c video *-display Beschreibung: VGA compatible controller Produkt: TU106M [GeForce RTX 2060 Mobile] Hersteller: NVIDIA Corporation Physische ID: 0 Bus-Informationen: pci@:01:00.0 Version: a1 Breite: 64 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom Konfiguration: driver=nvidia latency=0 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07 *-display Beschreibung: VGA compatible controller Produkt: UHD Graphics 630 (Mobile) Hersteller: Intel Corporation Physische ID: 2 Bus-Informationen: pci@:00:02.0 Version: 00 Breite: 64 bits Takt: 33MHz Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom Konfiguration: driver=i915 latency=0 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff ioport:5000(Größe=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1865870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865870] [NEW] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
Public bug reported: After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine after that. lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 uname -a Linux 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx graphics: lshw -c video *-display Beschreibung: VGA compatible controller Produkt: TU106M [GeForce RTX 2060 Mobile] Hersteller: NVIDIA Corporation Physische ID: 0 Bus-Informationen: pci@:01:00.0 Version: a1 Breite: 64 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom Konfiguration: driver=nvidia latency=0 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07 *-display Beschreibung: VGA compatible controller Produkt: UHD Graphics 630 (Mobile) Hersteller: Intel Corporation Physische ID: 2 Bus-Informationen: pci@:00:02.0 Version: 00 Breite: 64 bits Takt: 33MHz Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom Konfiguration: driver=i915 latency=0 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff ioport:5000(Größe=64) memory:c-d ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/bugs/1865870/+attachment/5333029/+files/Xorg.0.log.old ** Attachment removed: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1865870/+attachment/5333029/+files/Xorg.0.log.old -- 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/1865870 Title: xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" Status in xorg-server package in Ubuntu: New Bug description: After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
I tested all versions since 18.04 up to 20.04, in no live session I
could reproduce this problem. Yet this problem occurs in our
installations. The youngest installation is about three weeks old and
has the same bug.
Is there a way to end pulseaudio and prevent it from auto-restarting, so
I can try and get some debug from "pulseaudio -vvv"? Killing the process
with kill/pkill, or with "pulseaudio --kill" restarts it immediately.
Attached is the output to syslog when dis- and reconnectiong the USB
headset.
** Attachment added: "pulseaudio_syslog"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5333028/+files/pulseaudio_syslog
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833116] Re: chtmax98090 not working out of the box
https://bugzilla.kernel.org/show_bug.cgi?id=201787#c14 Bug is only "fixed" for Swanky and Gnawty chromebooks. They are marked to use a quirk, as an update breaks sound. To get a fix you should contact with Hans de Goede (you can in bugzilla) and ask for a fix. -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850001] Re: nautilus hangs on file delete
I had the same issue today, and I remember the last thing I done yesterday before failing was installing the MegaSync extension. I have just removed that package and restarted and Nautilus is working again. I hope this would be useful. -- 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/1850001 Title: nautilus hangs on file delete Status in nautilus package in Ubuntu: New Bug description: Nautilus hangs when deleting a file. The file does not get deleted. This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT- CLICK attempt at deleting. This is reproducible in this boot session. This has never happened since the install of the OS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 18:12:36 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-10-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833116] Re: chtmax98090 not working out of the box
Attached is the output of the crashlog from 20.04 after applying the git settings as detailed in the OP and rebooting - Pulseaudio seems to be crashing. ** Attachment added: "_usr_bin_pulseaudio.1000.crash" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+attachment/5333027/+files/_usr_bin_pulseaudio.1000.crash -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865865] Re: Icon spring animation starts/ends in the wrong location (near the top of the dock)
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1865865 Title: Icon spring animation starts/ends in the wrong location (near the top of the dock) Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Icon spring animation starts/ends in the wrong location (near the top of the dock). This only seems to happen using the Ubuntu Dock with Gnome Shell 3.35. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 12:06:44 2020 InstallationDate: Installed on 2020-02-25 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1865857 Title: ibus-x11 crashed with SIGABRT in __open_nocancel() Status in ibus package in Ubuntu: New Bug description: possible Xorg crashing ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.21-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:24:27 2020 ExecutablePath: /usr/lib/ibus/ibus-x11 ExecutableTimestamp: 1581612711 InstallationDate: Installed on 2020-02-29 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcCwd: /home/mel ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45 __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, posix_mode=, prot=prot@entry=438, read_write=8, is32not64=) at fileops.c:186 _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281 __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 "/etc/localtime") at iofopen.c:75 _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863468] Re: Libreoffice Snap is not available in Turkish
** Tags added: snap -- 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/1863468 Title: Libreoffice Snap is not available in Turkish Status in libreoffice package in Ubuntu: Fix Committed Bug description: Libreoffice Snap is not available in Turkish. Although there are many other language packs available, there is no Turkish language support. I am having difficulty using it because I do not speak English. I was able to write this message through Google Translate anyway. I request the addition of Turkish language for the Libreoffice Snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865080] Re: tracker-miner-fs crashed with signal 5
*** This bug is a duplicate of bug 1864153 *** https://bugs.launchpad.net/bugs/1864153 ** This bug is no longer a duplicate of private bug 1864556 ** This bug has been marked a duplicate of bug 1864153 tracker-extract crashed with signal 5 in start_thread() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1865080 Title: tracker-miner-fs crashed with signal 5 Status in tracker-miners package in Ubuntu: New Bug description: tracker-miner-fs crashes every time at bootup ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: tracker-miner-fs 2.3.1-3build1 Uname: Linux 5.5.6-050506-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Thu Feb 27 22:20:45 2020 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationDate: Installed on 2019-01-28 (395 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/lib/tracker/tracker-miner-fs Signal: 5 SourcePackage: tracker-miners StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 start_thread (arg=) at pthread_create.c:479 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: tracker-miner-fs crashed with signal 5 UpgradeStatus: Upgraded to focal on 2019-10-18 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1865080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865865] [NEW] Icon spring animation starts/ends in the wrong location (near the top of the dock)
Public bug reported: Icon spring animation starts/ends in the wrong location (near the top of the dock). This only seems to happen using the Ubuntu Dock with Gnome Shell 3.35. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 12:06:44 2020 InstallationDate: Installed on 2020-02-25 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1865865 Title: Icon spring animation starts/ends in the wrong location (near the top of the dock) Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Icon spring animation starts/ends in the wrong location (near the top of the dock). This only seems to happen using the Ubuntu Dock with Gnome Shell 3.35. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 12:06:44 2020 InstallationDate: Installed on 2020-02-25 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865862] [NEW] 'sound' settings require changing device and back again
Public bug reported: I have two actual audio devices plugged in: 1. speaker under my monitor plugged into the 3.5mm headphone jack, 2. a set of USB headphones. The 'Sound' settings panel shows three devices: 1. Headphones - built in audio 2. Digital output (s/pdif) - Jambra UC Voice 750 MS 3. Headphones - Jambra UC Voice 750 MS (I don't really know what 2 is - I usually ignore it) Normally, after plugging the headphones in, it has 3 selected, but the 'Test' button still plays through 1. I have to change the 'output device' to 1, then back to 3 in order to make it work on 3. So, this bug is that the control centre does not reflect reality when you launch it. It looks like it is automatically selecting the headphones just plugged in, but it hasn't actually changed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 17:59:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1865862 Title: 'sound' settings require changing device and back again Status in gnome-control-center package in Ubuntu: New Bug description: I have two actual audio devices plugged in: 1. speaker under my monitor plugged into the 3.5mm headphone jack, 2. a set of USB headphones. The 'Sound' settings panel shows three devices: 1. Headphones - built in audio 2. Digital output (s/pdif) - Jambra UC Voice 750 MS 3. Headphones - Jambra UC Voice 750 MS (I don't really know what 2 is - I usually ignore it) Normally, after plugging the headphones in, it has 3 selected, but the 'Test' button still plays through 1. I have to change the 'output device' to 1, then back to 3 in order to make it work on 3. So, this bug is that the control centre does not reflect reality when you launch it. It looks like it is automatically selecting the headphones just plugged in, but it hasn't actually changed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 17:59:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
Thanks. If you can then please also try Ubuntu 19.10
(https://ubuntu.com/download/desktop) so we can get a slightly better
idea of which PulseAudio version introduced the fix.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
Got feedback from one of my colleagues that running Ubuntu 18.04.4 with
Kernel 5.3.0-40, "pkill -U $USER pulseaudio" does not resolve the
problem, only a full restart of the system.
Is there anything I can do to provide additional logs? Running a
debugger when plugging in the headset, logfiles with a specific log
level?
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
Just tested with Ubuntu 20.04, the problem does not occur in the live
session.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Hello bugproxy, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not don
[Desktop-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
Hello Dan, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq
Hello Dan, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [impact] test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] The d/t/control file 'nm' test section, for bionic, needs to include dnsmasq-base in its dep list. disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865563] Re: password box not centered
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => 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/1865563 Title: password box not centered Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Committed Bug description: When logging in, one of the two isn't centered on screen: either the password input box, or the avatar. See attached photograph. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:41:54 2020 InstallationDate: Installed on 2019-10-13 (141 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-30 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865563] Re: password box not centered
Hi. This is fixed in the latest Yaru master :) Thanks for taking the time to report this ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed -- 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/1865563 Title: password box not centered Status in gnome-shell package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Fix Committed Bug description: When logging in, one of the two isn't centered on screen: either the password input box, or the avatar. See attached photograph. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:41:54 2020 InstallationDate: Installed on 2019-10-13 (141 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-30 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: No UI indication for fingerprint enrolling progress
** Tags added: rls-ff-incoming -- 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/1865845 Title: No UI indication for fingerprint enrolling progress Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: No UI indication for fingerprint enrolling progress
** Summary changed: - no fingerprint enrolling progress information + No UI indication for fingerprint enrolling progress -- 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/1865845 Title: No UI indication for fingerprint enrolling progress Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864052] Re: gnome-shell crashed with SIGABRT in src/core/window.c:1591:meta_window_unmanage: assertion failed: (g_list_find (workspace->windows, window) == NULL)
** Tags added: champagne
--
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/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_unmanage: assertion failed:
(g_list_find (workspace->windows, window) == NULL)
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/3e51baba6960038ed185034581cb83e4dd4776e6
---
gnome-shell crashes whenever in CHrome you pop out a video into a
floating video, or close the floating video (move the video back into
the main window).
To test, you can use
javascript:document.getElementsByTagName('video')[0].requestPictureInPicture();
to make a video float on any site, even if the site does not have a
button for it. I only tested Netflix.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 20 15:36:33 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-03-14 (707 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: Upgraded to focal on 2019-11-25 (87 days ago)
UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild
sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864052/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865645] Re: its crash sometimes and its hang
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1865645 Title: its crash sometimes and its hang Status in xorg package in Ubuntu: Won't Fix Bug description: its crash sometimes and its hang ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 04:50:48 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e] InstallationDate: Installed on 2019-06-24 (252 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 064e:3401 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ac0XX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ac0XX dmi.product.sku: Y4P52AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1865645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: no fingerprint enrolling progress information
after user click 'Next', there is no message remind user the progress of fingerprint enrollment. And also no reminder for the necessary of 12 times finger pressing. ** Attachment added: "Screenshot from 2020-03-03 11-13-25.png" https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment/5332971/+files/Screenshot%20from%202020-03-03%2011-13-25.png -- 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/1865845 Title: no fingerprint enrolling progress information Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: no fingerprint enrolling progress information
user page in setting failed forever after fingerprint enrolling time out. ** Attachment added: "Screenshot from 2020-03-03 16-49-54.png" https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment/5332968/+files/Screenshot%20from%202020-03-03%2016-49-54.png -- 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/1865845 Title: no fingerprint enrolling progress information Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865563] Re: password box not centered
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865563 Title: password box not centered Status in gnome-shell package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: When logging in, one of the two isn't centered on screen: either the password input box, or the avatar. See attached photograph. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:41:54 2020 InstallationDate: Installed on 2019-10-13 (141 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-30 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] [NEW] no fingerprint enrolling progress information
Public bug reported: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: Undecided Assignee: Alex Tu (alextu) Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- 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/1865845 Title: no fingerprint enrolling progress information Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865444] Re: [radeon] Dual monitor loop login
Thanks. The only relevant error I can find in there is strange: Mar 02 11:49:30 mel-Aspire-M5600-AM3600 gnome-shell[3916]: gnome-shell: Fatal IO error 0 (Success) on X server :0. and Feb 29 20:58:53 mel-Aspire-M5600-AM3600 gnome-shell[3068]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. So it sounds like Xorg is crashing... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- 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/1865444 Title: [radeon] Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
As I said earlier I totally agree with the comment above : Manual whitelisting from the snap team will always be a blocker for such a widely adopted use of an important browser. That will push people to use chrome which IMO a failure on the libre software side. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865410] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Project changed: gnome-shell => ubuntu ** No longer affects: ubuntu ** Summary changed: - Xorg freeze + Gnome Shell freeze -- 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/1865410 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg
[Desktop-packages] [Bug 1865444] Re: Dual monitor loop login
** Tags added: radeon ** Summary changed: - Dual monitor loop login + [radeon] Dual monitor loop login -- 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/1865444 Title: [radeon] Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865838] [NEW] no error popup while exceed maximal fingerprint retry during login
Public bug reported: from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. Steps to reproduce issue: 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. It will confuse user. Suggest behavior: 1. Each time user try fingerprint failed, show error message to remind user. 2. When user exceed 5 time errors, show error message to remind user input password instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gdm3 (Ubuntu) Importance: Undecided Assignee: Alex Tu (alextu) Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Alex Tu (alextu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error popup while exceed maximal fingerprint retry during login Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: New Bug description: from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. Steps to reproduce issue: 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. It will confuse user. Suggest behavior: 1. Each time user try fingerprint failed, show error message to remind user. 2. When user exceed 5 time errors, show error message to remind user input password instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863400] Re: gnome-shell reports problem on boot
Happened again. Bug did not seem to submit report once more. Screenshot as per comment #2 Report was produced which I managed to see the details but sending report did not return a bug ID. See this from terminal where I carried out action 1a in comment #3. Still no bug ID. dave@dave-ThinkPad-T410:~$ ls -alt /var/crash total 21384 -rw-r- 1 gdm whoopsie 21887221 Mar 2 23:32 _usr_bin_gnome-shell.121.crash drwxrwsrwt 2 root whoopsie 4096 Mar 2 23:32 . drwxr-xr-x 14 root root 4096 Jul 25 2018 .. dave@dave-ThinkPad-T410:~$ sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash [sudo] password for dave: dave@dave-ThinkPad-T410:~$ ls -alt /var/crash total 21596 drwxrwsrwt 2 root whoopsie 4096 Mar 3 07:22 . -rw--- 1 whoopsie whoopsie0 Mar 3 07:22 _usr_bin_gnome-shell.121.uploaded -rw-r--r-- 1 root whoopsie0 Mar 3 07:22 _usr_bin_gnome-shell.121.upload -rw-r- 1 gdm whoopsie 22105281 Mar 3 07:18 _usr_bin_gnome-shell.121.crash drwxr-xr-x 14 root root 4096 Jul 25 2018 .. dave@dave-ThinkPad-T410:~$ See this from terminal where I carried out action 1b in comment #3. No form was automatically opened in web browser (I use Firefox) dave@dave-ThinkPad-T410:~$ sudo apport-cli /var/crash/_usr_bin_gnome-shell.121.crash [sudo] password for dave: *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (22.1 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S dave@dave-ThinkPad-T410:~$ Carried out Step 2 in comment #3 but it was only showing the same one from 14th Feb 2020 as per comment #9 Although I carry out full updates and upgrades regularly I will once more carry out the instructions in comment #10. I will retain the contents of /var/crash for now and only report back here if necessary. -- 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/1863400 Title: gnome-shell reports problem on boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem reported at boot but does not seem to collect data and send, just does nothing. See attached screenshot of window. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description: Ubuntu 18.04.4 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Version table: *** 3.28.4-0ubuntu18.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
