[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
* When I pulled monitor from power and plugged it again it start showing my screen. (I should read it before i clicked POST. ... yea. There is no 'edit' here... I have to remember that) -- 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/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Ok... Problem is solved by ... puling out POWER from monitor! It is weird but for some reason when i unplugged monitor from power and pulled it again it start showing my screen. It is weird but to be honest I've tried so many things before and nothing helped... I've changed drivers few times... so many restarts... I've even changed hdmi cabel. I assume that monitor is OK because it showed grub/spash screen and when I tried run older linux kernel it showd text on second screen. Not sure what went wrong... maybe something with strength of hdmi signal? Screen still turns black every few minutes for ~second but at least it works. Thanks :) -- 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/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : ht
[Desktop-packages] [Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin
xxhash was a code split from a package already in main and already promoted in Disco/Eoan. It came back now as dependency for rsync and (thanks Steve) Foundations is subscribed to cover it. Can be promoted to main in groovy ** Changed in: xxhash (Ubuntu) Status: Incomplete => In Progress ** Changed in: xxhash (Ubuntu) Assignee: Steve Langasek (vorlon) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to teckit in Ubuntu. https://bugs.launchpad.net/bugs/1803230 Title: [MIR] teckit & xxhash, new rdeps of texlive-bin Status in teckit package in Ubuntu: Fix Released Status in xxhash package in Ubuntu: In Progress Bug description: teckit & xxhash, new rdeps of texlive-bin teckit was formerly bundled in texlive-bin (I believe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teckit/+bug/1803230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers
> I really wish hplip upstream developement would happen on a public VCS, > so that we could better understand the reasons behind such changes (and > a place where we could discuss our 74 patches…). Damn, I need to get better :) we have only 56 downstream patches :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1883898 Title: version 3.20.6 turns off plugin requirement for most printers Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Status in hplip package in Fedora: Confirmed Bug description: Hi, hplip-3.20.6 turns off plugin requirement for most devices which required the plugin at the past. This will make devices which really need it unable to print and most scanning will not work. Would you mind reverting the changes in models.dat? Thank you in advance! Zdenek To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1883898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885067] [NEW] package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置
Public bug reported: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libcurl4-gnutls-dev:amd64: Install libcurl3-gnutls:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 06:16:38 2020 ErrorMessage: 依赖关系问题 - 仍未被配置 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: emacs Title: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (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 emacs in Ubuntu. https://bugs.launchpad.net/bugs/1885067 Title: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 Status in emacs package in Ubuntu: New Bug description: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libcurl4-gnutls-dev:amd64: Install libcurl3-gnutls:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 06:16:38 2020 ErrorMessage: 依赖关系问题 - 仍未被配置 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: emacs Title: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1885067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885065] [NEW] i fucking dont know its your shit
Public bug reported: i dont fucking nknow ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1885065 Title: i fucking dont know its your shit Status in software-properties package in Ubuntu: New Bug description: i dont fucking nknow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1885065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
Another idea: You seem to be using the default Xorg session so that increases the possible set of components that could tamper with the power state. Please try logging into 'Ubuntu on Wayland' to see if the problem happens there. And another idea: Check that you don't have 'tlp' installed. It causes random power management bugs. Assuming the issue is not tlp, please also report it upstream at: https://gitlab.gnome.org/GNOME/mutter/issues If you are feeling adventurous then it might help to figure out the exact time of day the display is waking. Like with a timelapse video next to a clock that's synchronized to the machine's clock. That could then be compared to the system log or might spark other ideas. -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset
Thanks. Although they occur after zfs-mount.service, the two best explanations I can think of for what uses PulseAudio and might run as root are vmware.service and virtualbox.service. Also it's possible the unwanted directory is created after /root is unmounted. Not necessarily on startup. -- 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/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: - root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# - Extra details: - Ubuntu release: - root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 - - status of 'zfs-mount.service' is the following: - root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# - - software versions: - root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dumi 2419 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jun 21 19:17:20 2020 InstallationDate: Installed on 2018-09-08 (651 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-24 (57 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
We still don't have any usable information here, sorry. Please follow all the steps in comment #2 again. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/g
[Desktop-packages] [Bug 1884754] Re: Fractional scaling not persisted in VMware Player
Thanks. For this bug, please: 1. Set a fractional scale value and close Settings. 2. Take a copy of ~/.config/monitors.xml and name it 'before.xml'. 3. Reboot and log in. Make sure the bug occurs. 4. Take a copy of ~/.config/monitors.xml and name it 'after.xml'. 4. Run this command: journalctl -b0 > journal.txt 5. Attach all three resulting files here. ** Description changed: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - - The scaling is applied - - VMware Tools (open-vm-tools) appears to break, no more seamless mouse between host and Ubuntu - - After next reboot the setting is reverted to 100% + - The scaling is applied + - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884754 Title: Fractional scaling not persisted in VMware Player Status in mutter package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling not persisted in VMware Player
Thanks. For this bug, please: 1. Set a fractional scale value and close Settings. 2. Take a copy of ~/.config/monitors.xml and name it 'before.xml'. 3. Reboot and log in. Make sure the bug occurs. 4. Take a copy of ~/.config/monitors.xml and name it 'after.xml'. 5. Run this command: journalctl -b0 > journal.txt 6. Attach all three resulting files here. -- 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/1884754 Title: Fractional scaling not persisted in VMware Player Status in mutter package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885026] Re: Fractional scaling contains 175% option twice
** Package changed: gnome-shell (Ubuntu) => gnome-control-center (Ubuntu) ** Tags added: xrandr-scaling -- 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/1885026 Title: Fractional scaling contains 175% option twice Status in gnome-control-center package in Ubuntu: New Bug description: When opening the Settings, select Displays and then enable "Fractional Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250% If you click the first 175% option it will even automatically select the second one instead. The third option should likely be 150% instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 15:21:07 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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-control-center/+bug/1885026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin
Foundations is now subscribed to xxhash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to teckit in Ubuntu. https://bugs.launchpad.net/bugs/1803230 Title: [MIR] teckit & xxhash, new rdeps of texlive-bin Status in teckit package in Ubuntu: Fix Released Status in xxhash package in Ubuntu: Incomplete Bug description: teckit & xxhash, new rdeps of texlive-bin teckit was formerly bundled in texlive-bin (I believe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teckit/+bug/1803230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817662] Re: [SRU] Need to support WWAN module DW5820e
*** This bug is a duplicate of bug 1819615 *** https://bugs.launchpad.net/bugs/1819615 Appears this affects me too. Have Dell Latitude with Fibocom L850 (dw5820e) which works in Windows 10. Does not when I wiped the machine and loaded 20.04 LTS. Loaded Modem Manager and the GUI but device is not found. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1817662 Title: [SRU] Need to support WWAN module DW5820e Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: * Impact New WWAN module like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. 3. Test a few exsting WWAN module and make sure they works. * Regression potential As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player
gnome-shell seems to be the right one, filed https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885026 This bug can continue to be about the missing persistence. ** Summary changed: - Fractional scaling broken in VMware Player + Fractional scaling not persisted in VMware Player -- 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/1884754 Title: Fractional scaling not persisted in VMware Player Status in mutter package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - VMware Tools (open-vm-tools) appears to break, no more seamless mouse between host and Ubuntu - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885026] [NEW] Fractional scaling contains 175% option twice
Public bug reported: When opening the Settings, select Displays and then enable "Fractional Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250% If you click the first 175% option it will even automatically select the second one instead. The third option should likely be 150% instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 15:21:07 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1885026 Title: Fractional scaling contains 175% option twice Status in gnome-shell package in Ubuntu: New Bug description: When opening the Settings, select Displays and then enable "Fractional Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250% If you click the first 175% option it will even automatically select the second one instead. The third option should likely be 150% instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 15:21:07 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1885026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player
I opened https://bugs.launchpad.net/ubuntu/+source/open-vm- tools/+bug/1885025 for the open-vm-tools issue, I don't know for which package I should file the bug with the missing 150% setting. -- 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/1884754 Title: Fractional scaling not persisted in VMware Player Status in mutter package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - VMware Tools (open-vm-tools) appears to break, no more seamless mouse between host and Ubuntu - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers
Thanks @zdohnal for this bug. Thanks to your report, I have uploaded our repackaged 3.20.6+dfsg0 to debian/experimental only, so it won't be auto-sync'ed to Debian. I really wish hplip upstream developement would happen on a public VCS, so that we could better understand the reasons behind such changes (and a place where we could discuss our 74 patches…). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1883898 Title: version 3.20.6 turns off plugin requirement for most printers Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Status in hplip package in Fedora: Confirmed Bug description: Hi, hplip-3.20.6 turns off plugin requirement for most devices which required the plugin at the past. This will make devices which really need it unable to print and most scanning will not work. Would you mind reverting the changes in models.dat? Thank you in advance! Zdenek To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1883898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
Could someone provide a testcase describing a situation that is buggy today and how to trigger it? -- 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/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Expired Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885015] Re: replace gnutls with openssl
Thank you for your bug report, could you give some more detailled reasoning on why openssl would be a better choice? Do you know of any problem caused by the fact that gnutls is being used? Any known security issue or weakness reported? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Wishlist ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1885015 Title: replace gnutls with openssl Status in network-manager package in Ubuntu: Incomplete Bug description: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap
I use it only for github, no special setup was needed (udev rules are already there for PIV). I logged last time some months ago so I don't know when it stopped working exactly. -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885006] Re: Search Service broken on Ubuntu Nightly builds
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1885006 Title: Search Service broken on Ubuntu Nightly builds Status in firefox package in Ubuntu: Confirmed Bug description: Search Service broken on Ubuntu Nightly builds.As reported in the Mozilla bug tracker, the search service has broken on the Ubuntu nightly builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1647576 It is broken due to this patch: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/view/head:/debian/patches /cleanup-old-distribution-search-engines.patch The code surrounding that has changed, however it should not be necessary now anyway, as we fixed the issues with distributions and built-in engines back in 76 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623597). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873084] Re: Seahorse has 100% cpu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1873084 Title: Seahorse has 100% cpu Status in seahorse package in Ubuntu: Confirmed Bug description: Seahorse has 100 % CPU. Submitting Ubuntu-bug. How can i take a performance profile if it happens again? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: seahorse 3.32.2-1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 00:16:42 2020 InstallationDate: Installed on 2020-02-08 (67 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1873084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same issue here (without headset line). Cannot switch to HSP/HFP mode. I have a dual boot Windows 10, the headset (audio output and microphone) works fine there. Ubuntu 18.04.4, kernel 4.15.0-106-generic, pulseaudio 11.1 Card: HDA Intel PCH HD (Dell 200 Series PCH HD) Chip: Realtek ALC3861 Device 98:52:3D:73:D3:5B (public) Name: Soundcore Liberty Air 2 Alias: Soundcore Liberty Air 2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Vendor specific (eb03-d102-11e1-9b23-00025b00a5a5) RSSI: -59 -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884942] Re: Nautilus doesn't provide a way to handle changed SSH key
*** This bug is a duplicate of bug 418192 *** https://bugs.launchpad.net/bugs/418192 Thanks for pointing to the other bug report. Looks like the OP did create a bug in the Gnome bugzilla, https://bugzilla.gnome.org/show_bug.cgi?id=612103, but the last comment on it is from 2014 so I guess they will not be fixing it. ** Bug watch added: bugzilla.gnome.org/ #612103 https://bugzilla.gnome.org/show_bug.cgi?id=612103 -- 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/1884942 Title: Nautilus doesn't provide a way to handle changed SSH key Status in nautilus package in Ubuntu: New Bug description: I rebuilt one of my machines from scratch which means that the ssh key has changed. While I can connect to that machine from the command line via ssh, if I try to connect to it via Nautilus all I get is a "Host key verification failed" error. When using the command line I get notified which line in known_hosts is the offending one so I can remove it if it is legit. Nautilus doesn't report the offending line. Is there a way to force a connect? Or at least get Nautilus to report the offending line in known_hosts? Otherwise I have to remove the known_hosts file but this is not a good solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1884942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885015] [NEW] replace gnutls with openssl
Public bug reported: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: curl gnutls openssl -- 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/1885015 Title: replace gnutls with openssl Status in network-manager package in Ubuntu: New Bug description: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Spotify and Totem working, after modifying the /etc/pulse/daemon.conf file add / modified in: ; default-sample-format = s24le ; default-sample-rate = 192000 YouTube, on the other hand, sometimes works, sometimes not. Most of the time it doesn't work. -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
HP Omen. Ubuntu 19.10. 5.3.0-59-generic #53-Ubuntu + External (bluetooth) input working + External (bluetooth) output working - Internal input not working (nothing shown) - Internal output not working (Dummy shown) Managed to fix internal output by adding "options snd-hda-intel dmic_detect=0" after reading comment #69. Perhaps it was here before because I lost "internal output" couple of months ago after messing with these settings. Internal input still not working. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
No worries - I was under the impression that I should test and send y'all results. I'm happy to wait. Thanks for all of your work on this and other bugs, Marc On Wed, Jun 24, 2020 at 12:20 PM Heather Ellsworth < 1869...@bugs.launchpad.net> wrote: > The fix is released in 6.4.4 which is still in proposed for a few more > days before it makes its way to focal-updates, so please be patient. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1869561 > > Title: > Libreoffice Help does not work > > Status in libreoffice package in Ubuntu: > Fix Released > Status in libreoffice source package in Focal: > Fix Committed > > Bug description: > In the latest PPA release of Libreoffice, the Help does not work. IN > version 6.3.5.2 it is OK. I the version below it returns an error. > > Version: 6.4.2.2 > Build ID: 1:6.4.2-0ubuntu0.19.10.3 > CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; > Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB > Calc: threaded > > > The Error is: > > Object not accessible. > The object cannot be accessed > due to insufficient user rights. > > > The Help used to open the help in a browser window. This latest version > seems to try to open the old type of local help (rather than using a > browser). > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions > -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
if it's not listed it sounds like something worth reporting upstream on https://github.com/linuxwacom/libwacom/issues/ -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is "No stylus found" in the Settings. Stylus itself is working flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu 20.04 (GNOME)? Here is the xsetwacom output: xsetwacom --list Wacom HID 495F Pen stylus id: 9 type: STYLUS Wacom HID 495F Finger touch id: 10 type: TOUCH Wacom HID 495F Pen eraser id: 18 type: ERASER PS: I am currently forced to use these kernel boot parameters: i8042.nopnp=1 pci=nocrs (because of this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 ) Many Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:43:21 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-06-19 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1884746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884942] Re: Nautilus doesn't provide a way to handle changed SSH key
*** This bug is a duplicate of bug 418192 *** https://bugs.launchpad.net/bugs/418192 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 418192, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 418192 Nautilus can't open sftp location if public key is changed -- 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/1884942 Title: Nautilus doesn't provide a way to handle changed SSH key Status in nautilus package in Ubuntu: New Bug description: I rebuilt one of my machines from scratch which means that the ssh key has changed. While I can connect to that machine from the command line via ssh, if I try to connect to it via Nautilus all I get is a "Host key verification failed" error. When using the command line I get notified which line in known_hosts is the offending one so I can remove it if it is legit. Nautilus doesn't report the offending line. Is there a way to force a connect? Or at least get Nautilus to report the offending line in known_hosts? Otherwise I have to remove the known_hosts file but this is not a good solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1884942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884822] Re: nautilus search bar generates high cpu usage - no reaction on 1st double-click
Thanks, reassigning to clamtk then since that's the component creating the issue ** Package changed: nautilus (Ubuntu) => clamtk (Ubuntu) -- 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/1884822 Title: nautilus search bar generates high cpu usage - no reaction on 1st double-click Status in clamtk package in Ubuntu: New Bug description: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.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/clamtk/+bug/1884822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
I have the same issue with Chromium 83.0.4103.106 (Official Build) snap (64-bit). I'm using Kubuntu 20.04 minimal installation. Chromium: 83.0.4103.106 (Official Build) snap (64-bit) Revision: ce7134bb3d95141cd18f1e65772a4247f282d950-refs/branch-heads/4103@{#694} OS: Linux JavaScript: V8 8.3.110.13 Flash: (Disabled) User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36 Command Line: /snap/chromium/1193/usr/lib/chromium-browser/chrome --no-default-browser-check --no-first-run --password-store=basic --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36 --flag-switches-begin --flag-switches-end --disable-webrtc-apm-in-audio-service -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I can confirm that the error persist on Ubuntu 20.04 LTS with headphones LE-Bose AE2 SoundLink. Disabling voice prompts (as Daniel van Vugt mentioned in comment #8) helps a lot, but still there is a whistle but no "call from" voice anymore. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
The fix is released in 6.4.4 which is still in proposed for a few more days before it makes its way to focal-updates, so please be patient. -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
The corresponding issue in JetBrains issue tracker: https://youtrack.jetbrains.com/issue/IDEA-59679 -- 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/1863080 Title: Unable to use dead keys in Java apps Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881007] Re: [SRU] libreoffice 6.4.4 for focal
Upgraded libreoffice from 1:6.4.3-0ubuntu0.20.04.1 to 1:6.4.4-0ubuntu0.20.04.1 from focal-proposed in a clean and up-to-date focal amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- 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/1881007 Title: [SRU] libreoffice 6.4.4 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 6.4.4 is in its fourth bugfix release of the 6.4 line. Version 6.4.4 is currently in focal. For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs (that's a total of 98 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 98 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/1881007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset
I can share the output of "systemd-analyze plot": please see attached file 'systemd_startup_04.svg'. If needed I can provide output of some other commands: just let me know what else might be useful. ** Attachment added: "svg plot of system startup" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884455/+attachment/5386859/+files/systemd_startup_04.svg -- 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/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: - root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# - Extra details: - Ubuntu release: - root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 - - status of 'zfs-mount.service' is the following: - root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# - - software versions: - root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dumi 2419 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jun 21 19:17:20 2020 InstallationDate: Installed on 2018-09-08 (651 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-24 (57 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDe
[Desktop-packages] [Bug 1885006] [NEW] Search Service broken on Ubuntu Nightly builds
Public bug reported: Search Service broken on Ubuntu Nightly builds.As reported in the Mozilla bug tracker, the search service has broken on the Ubuntu nightly builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1647576 It is broken due to this patch: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/view/head:/debian/patches /cleanup-old-distribution-search-engines.patch The code surrounding that has changed, however it should not be necessary now anyway, as we fixed the issues with distributions and built-in engines back in 76 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623597). ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1885006 Title: Search Service broken on Ubuntu Nightly builds Status in firefox package in Ubuntu: New Bug description: Search Service broken on Ubuntu Nightly builds.As reported in the Mozilla bug tracker, the search service has broken on the Ubuntu nightly builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1647576 It is broken due to this patch: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/view/head:/debian/patches /cleanup-old-distribution-search-engines.patch The code surrounding that has changed, however it should not be necessary now anyway, as we fixed the issues with distributions and built-in engines back in 76 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623597). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884942] Re: Nautilus doesn't provide a way to handle changed SSH key
** Package changed: ubuntu => nautilus (Ubuntu) -- 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/1884942 Title: Nautilus doesn't provide a way to handle changed SSH key Status in nautilus package in Ubuntu: New Bug description: I rebuilt one of my machines from scratch which means that the ssh key has changed. While I can connect to that machine from the command line via ssh, if I try to connect to it via Nautilus all I get is a "Host key verification failed" error. When using the command line I get notified which line in known_hosts is the offending one so I can remove it if it is legit. Nautilus doesn't report the offending line. Is there a way to force a connect? Or at least get Nautilus to report the offending line in known_hosts? Otherwise I have to remove the known_hosts file but this is not a good solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1884942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884942] [NEW] Nautilus doesn't provide a way to handle changed SSH key
You have been subscribed to a public bug: I rebuilt one of my machines from scratch which means that the ssh key has changed. While I can connect to that machine from the command line via ssh, if I try to connect to it via Nautilus all I get is a "Host key verification failed" error. When using the command line I get notified which line in known_hosts is the offending one so I can remove it if it is legit. Nautilus doesn't report the offending line. Is there a way to force a connect? Or at least get Nautilus to report the offending line in known_hosts? Otherwise I have to remove the known_hosts file but this is not a good solution. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Nautilus doesn't provide a way to handle changed SSH key https://bugs.launchpad.net/bugs/1884942 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus 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 1884822] Re: nautilus search bar generates high cpu usage - no reaction on 1st double-click
I find a solution: sudo apt remove clamtk-gnome After that, a search in nautilus lasts only fraction of a second, as it should be. -- 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/1884822 Title: nautilus search bar generates high cpu usage - no reaction on 1st double-click Status in nautilus package in Ubuntu: New Bug description: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.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/1884822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Hi slovic. If you see the nvidia-settings you probably can see the second monitor is detected by the Nvidia card. I think this is a problem of Intel, 'cause the second monitor's connected via HDMI, which is connected to Intel GPU. Please click on "this bug affects me too" so we can make see it to more people. -- 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/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884838] Re: woops-logout white page after installation from scratch on old crappy hp
This is a faulty hardware induced crash, and not a bug. I can't quite figure out how to close this. Guess "Invalid" is close enough. ** Changed in: orca (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/orca/+question/691509 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orca in Ubuntu. https://bugs.launchpad.net/bugs/1884838 Title: woops-logout white page after installation from scratch on old crappy hp Status in orca package in Ubuntu: Invalid Bug description: Happened while doing upgrade post vanilla installation from scratch (20.04 desktop). I got a white page that said something went wrong "logout". Could not get back into interactive graphics mode (had to ctrl alt f3 to issue a reboot command) package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: installed orca package post-installation script subprocess returned error exit status 1 lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy orca orca: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 3.36.1-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: orca 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 23 16:37:11 2020 ErrorMessage: installed orca package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: orca Title: package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: installed orca package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1884838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884505] Re: Libreoffice crashes gnome session
Added output after crash and immediate re-login. ** Attachment added: "Journal output" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1884505/+attachment/5386839/+files/journal.txt -- 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/1884505 Title: Libreoffice crashes gnome session Status in libreoffice package in Ubuntu: Incomplete Bug description: After while (1-5 min) using Libreoffice Cals/Writer the program crashes the running gnome session. And login screen pops up. After new login there are issues with audio playback so restart is required. I tested both libreoffice snap and dep packages. Problem occurs with both. My suspicion is that it is related to graphics card or driver. Notebook Dell 7559, GeForce 960M rev a2, driver 440.62, Ububtu 20.04 After each crash I found something like below in dmesg log: [14564.930179] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 [14564.930629] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 full output in attachment. This bug is very annoying and makes the whole system useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:47:12 2020 InstallationDate: Installed on 2020-05-11 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1884505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883705] Re: SRU the current 2.5.25 stable update
I retried gvfs and it passed! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1883705 Title: SRU the current 2.5.25 stable update Status in libgphoto2 package in Ubuntu: Fix Released Status in libgphoto2 source package in Focal: Fix Committed Status in libgphoto2 package in Debian: Fix Released Bug description: * Impact That's a stable update including bugfixes and support for newer cameras The list of changes is available there: https://sourceforge.net/projects/gphoto/files/libgphoto/2.5.25/ * Test case Connect a camera and check that the desktop correctly see it and prompt for an action. Check that the content can be browsed from nautilus and the photos imported from shotwell (unmount the device from nautilus first if needed) * Regression potential Nothing specific to check, the fixes are mostly for hardware that was not working and the change devices specific To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1883705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616994] Re: Firefox should allow showing of a desktop notification when a download is complete
Launchpad has imported 5 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1298077. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-08-25T16:37:13+00:00 U552789 wrote: I think it would be really nice if like with other browsers Firefox would show a desktop notification using the style of the DE/OS when a download has been completed. Currently one is required to install an add-on, but I think such basic functionality should really be built-in. I originally made this request here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1616994 But thought I should also do so upstream. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1616994/comments/1 On 2016-10-31T16:14:24+00:00 Paolo-mozmail wrote: Earlier versions of Firefox used to have a similar functionality, implemented with a small window displayed for a short time on the desktop. This was removed in an effort to avoid these dialogs, that were likely perceived as obtrusive, and it was replaced with the current animation in the Downloads button in the toolbar. Maybe we could consider reintroducing this if we had a different implementation, more integrated with the notifications offered by modern operating systems. However, it's unlikely that someone from design and engineering will be able to look at this in the short term. I'll leave the bug open for future reference, but we need a design decision before we can accept code patches. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1616994/comments/2 On 2018-07-21T17:55:21+00:00 U552789 wrote: Any update on this? Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1616994/comments/3 On 2020-06-24T13:19:28+00:00 Mak-g wrote: *** Bug 1646450 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1616994/comments/4 On 2020-06-24T13:21:40+00:00 Mak-g wrote: This is still open for community pick, if someone would like to try providing a patch to add an optional system notification when downloads take more than a minute (thus it's more likely to miss their completion). Then we could pass that proposal through UX for evaluation. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1616994/comments/5 ** Changed in: firefox Importance: Wishlist => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1616994 Title: Firefox should allow showing of a desktop notification when a download is complete Status in Mozilla Firefox: Confirmed Status in Ubuntu GNOME: New Status in firefox package in Ubuntu: New Bug description: I think it would be really nice if like with other browsers Firefox would show a desktop notification using the style of the DE/OS when a download has been completed. Currently one is required to install an add-on, but I think such basic functionality should really be built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1616994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
there is unfortunately no output from that command :( : $ sudo libwacom-list-local-devices && echo DONE DONE I will have a look into that gitlab issue later on, thanks for now -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is "No stylus found" in the Settings. Stylus itself is working flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu 20.04 (GNOME)? Here is the xsetwacom output: xsetwacom --list Wacom HID 495F Pen stylus id: 9 type: STYLUS Wacom HID 495F Finger touch id: 10 type: TOUCH Wacom HID 495F Pen eraser id: 18 type: ERASER PS: I am currently forced to use these kernel boot parameters: i8042.nopnp=1 pci=nocrs (because of this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 ) Many Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:43:21 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-06-19 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1884746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884536] Re: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
Thank you for your bug report, could you get a screencast or video showing the issue? ** Changed in: gpm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1884536 Title: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04 Status in gpm package in Ubuntu: Incomplete Bug description: I have relatively recently loaded Ubuntu 20.04 to dual-boot on a Packard Bell with Windows 10 Home 64-bit already installed. The mouse- pointer moves and clicks perfectly when the PC has a single-monitor. However, for work as a developer, I should like to use a dual-monitor setup. The problem I have is, if I plug in to the PC tower a second monitor and follow the steps to Connect Another Monitor To My Computer (https://help.ubuntu.com/stable/ubuntu-help/display-dual- monitors.html), and after I confirm "join Display", the mouse-pointer jumps about and a second stationary mouse-pointer appears in the bottom right of my primary screen. This behaviour stops immediately I confirm "Single Display", but now the second screen is now turned blank. $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB Wired Keyboard Consumer Control id=12 [slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB Wired Keyboardid=10 [slave keyboard (3)] ↳ USB Wired Keyboard System Control id=11 [slave keyboard (3)] ↳ USB Wired Keyboard Consumer Control id=14 [slave keyboard (3)] $ sudo dmidecode -t 1 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Packard Bell Product Name: iMedia S2984 Version: Serial Number: DTU96EK00360103D0F3000 UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd Wake-up Type: Power Switch SKU Number: Family: Packard Bell Desktop $ lsb_release -a; uname -a; lsusb No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard Model KBAY211 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I am reporting this as a bug because I am unable to fix it and I have asked around, but no joy. I do need a dual-monitor set p for work. Currently, I can use Windows10 with dual-monitors, on the same machine, without a glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1884536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883694] Autopkgtest regression report (glib2.0/2.64.3-1~ubuntu20.04.1)
All autopkgtests for the newly accepted glib2.0 (2.64.3-1~ubuntu20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd-glib/1.57-0ubuntu3 (armhf) gvfs/1.44.1-1ubuntu1 (arm64) libgepub/unknown (armhf) sbd/1.4.1-3 (amd64) golang-github-ostreedev-ostree-go/0.0+git20190702.759a8c1-3 (arm64, ppc64el) umockdev/0.14.1-1 (armhf) tracker/2.3.4-1 (armhf) 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/focal/update_excuses.html#glib2.0 [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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1883694 Title: [SRU] New upstream release 2.64.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Committed Bug description: [ Description ] Take this new upstrem stable release. +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium + + * No-change backport from unstable / groovy to focal. + + -- Iain Lane Tue, 16 Jun 2020 11:53:34 +0100 + +glib2.0 (2.64.3-1) unstable; urgency=medium + + * Team upload + + [ Laurent Bigonville ] + * Drop the libgio-fam package, and install the fam GIO plugin in +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915) + * Stop building the libgio-fam package on kFreeBSD ports. +It is no longer necessary now that gkqueuefilemonitor is available. + + [ Simon McVittie ] + * Clarify changelog entry regarding Hurd and kFreeBSD + * New upstream stable release + + -- Simon McVittie Fri, 29 May 2020 20:24:33 +0100 The gio-fam related changes do not affect Ubuntu, as they are for hurd/kfreebsd only. Upstream NEWS diff: * Stability improvements for various unit tests * Bugs fixed: - #1954 gdbus-server-auth intermittent failure - #2094 Deprecation warnings when compiling with -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28 - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64 - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64 - !1473 CI: Switch to new Windows runners (2.64) - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64 - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after g_ptr_array_extend_and_steal()” to glib-2-64 - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to glib-2-64 - !1486 Backport !1472 “gthread: ignore deprecated declarations in static inline functions” to glib-2-64 - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to glib-2-64 - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64 * Translation updates: - Chinese (Taiwan) - German [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884336] Re: Erratic ethernet connectivity and icon
** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1884336 Title: Erratic ethernet connectivity and icon Status in network-manager package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS Installed: 1.10.6-2ubuntu1.4 Candidate: 1.10.6-2ubuntu1.4 Version table: *** 1.10.6-2ubuntu1.4 500 Expected behavior is a stable high-speed internet connection when usb tethering with an Android phone. Instead, for the past three months, since covid slowed down internet connectivity on Jio telecom in India, my Ubuntu internet connectivity has become erratic. In the early morning before 6 AM when I tether an Android phone to my laptop the internet connectivity indicator in the upper right-hand corner of the desktop shows the normal three boxes in a triangle and has decent speed. As network traffic increases the indicator turns to three gray boxes with a question mark in the middle and connectivity speed remains decent for a few websites, such as YouTube, Google Search and some others, but connectivity stops for most websites. Chromium, Vivaldi and Firefox browsers show the following error for such sites: “This site can’t be reached. askubuntu.com’s server IP address could not be found.” Oddly, in tri-booted Win 10 all websites open reliably 24/7, though sometimes at slow speeds. In Fedora 31 on the same hardware the behavior is identical to Ubuntu. I’ve tried changing the DNS settings in Ubuntu to use Cloud Flare, Google and even the DNS settings in Windows, but to no avail. On Ask Ubuntu there were no helpful comments except a suggestion to file a bug report. Ideally, connectivity without "unable to connect" errors on most websites should be available always. BTW, when I allowed data to be collected for this bug report it was in the early morning, so the connection was working properly and the network icon was the normal three boxes in a triangle with decent speed. If need be, I can send more information later when the "unable to connect" errors occur from Windows 10, or via email, which always works. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 06:49:22 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-25 (664 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.137.129 dev enp0s20u1 proto dhcp metric 100 169.254.0.0/16 dev enp0s20u1 scope link metric 1000 192.168.137.0/24 dev enp0s20u1 proto kernel scope link src 192.168.137.9 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20u1 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Wired connection 3 d70d6035-59a6-34c1-a00a-d222c65aef1c /org/freedesktop/NetworkManager/ActiveConnection/1 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- enp3s0f2 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884505] Re: Libreoffice crashes gnome session
Thank you for your bug report, could you add your 'journalctl -b 0' log after getting the issue? ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- 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/1884505 Title: Libreoffice crashes gnome session Status in libreoffice package in Ubuntu: Incomplete Bug description: After while (1-5 min) using Libreoffice Cals/Writer the program crashes the running gnome session. And login screen pops up. After new login there are issues with audio playback so restart is required. I tested both libreoffice snap and dep packages. Problem occurs with both. My suspicion is that it is related to graphics card or driver. Notebook Dell 7559, GeForce 960M rev a2, driver 440.62, Ububtu 20.04 After each crash I found something like below in dmesg log: [14564.930179] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 [14564.930629] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 full output in attachment. This bug is very annoying and makes the whole system useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:47:12 2020 InstallationDate: Installed on 2020-05-11 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1884505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Thank you for your bug report. When did it stop working? Was there any update around the time? Could you give some details on how you setup and use the yubikey there? -- 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/1884759 Title: U2f yubikey stopped working in chromium snap Status in chromium-browser package in Ubuntu: New Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881699] Re: No analog output
@Hui, could you check if that's a known issue? J-B mentioned it was an issue Carbon X1 7g users are talking about -- 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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: New Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] should be low at this point To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881603] Re: [snap] Cannot open attached file from e-mail
** 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844453] Re: [upstream] Access to the Google remote account does not work
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low -- 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/1844453 Title: [upstream] Access to the Google remote account does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I have a Google account with 2FA login, from LibreOffice I try to add the remote account, but it doesn't work, it asks me for a 6-digit PIN. Investigating to see if it was just my problem, I discovered that this is a long-standing LibreOffice bug (1) and seems unresolved. The last report confirms this: "2019-07-04 04:44:41 UTC This feature doesn't work with my Google account _w/o_ 2FA. Bug hasn't be resolved for about 3 years and "very soon" we may celebrate 5 years anniversary. %-(" 1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 17 23:00:10 2019 InstallationDate: Installed on 2019-02-18 (210 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
Hello Jo, or anyone else affected, Accepted chromium-browser into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chromium- browser/83.0.4103.97-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: chromium-browser (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Users trying to install chromium-browser with apt in a chroot will see the preinst script hang for 30min, and eventually fail. This use case is important as chroots are used by sysadmins to prepare installers. [Test Case] Create a focal chroot (for example using "pcreate -a amd64 -d focal focal-amd64"), enter the chroot and run "apt install chromium-browser". Expected outcome: the installation succeeds, even though the chromium snap is not being installed because snapd cannot run in the chroot. Incorrect (current) outcome: the installation hangs during 30 minutes while trying to contact the snap store, and eventually fails. [Regression Potential] As this change modifies the chromium-browser preinstallation script, it should be verified that installing the package on systems that are capable of running snapd (e.g. virtual machines or bare metal) still works as expected. [Original Description] Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884924] Re: Chromium Bug that causes the browser to shut down unexpectedly/crash
Thanks for the package is from mint and not Ubuntu and the issue should be reported to them ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/1884924 Title: Chromium Bug that causes the browser to shut down unexpectedly/crash Status in chromium-browser package in Ubuntu: Invalid Bug description: The bug pastebin from the mint report system(ubuntu dervied OS) https://termbin.com/xv63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540110] Re: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available.
** Changed in: gnome-disk-utility (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1540110 Title: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available. Status in GNOME Disks: Expired Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: gnome-disk-utility (show as "Disks" on the desktop environment running Unity) systematically does not acknowledge that disks have SMART capabilities when connected through a USB port; SMART capabilities are grayed. However, 'sudo smartctl -a /dev/' works fine confirming that there is no problem reading SMART data through a USB link. gnome- disk-utility acknowledge SMART capabilities if the same disk is connected through a SATA port. Confirmed for Ubuntu 14.04 LTS Trusty Tahr on 2016-01-26, gnome-disk- utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon. This bug is the same as bug #1092900 which was reported against Ubuntu 10.04 LTS Lucid Lynx. Following user dino99 suggestion, I opened this new bug report to follow the same problem on Ubuntu 14.04 LTS Trusty Tahr. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 31 11:30:03 2016 InstallationDate: Installed on 2014-11-01 (456 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1540110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
Thanks, searching a bit upstream it sounds like the right command is rather $ libwacom-list-local-devices could you get the output from this one? https://gitlab.gnome.org/GNOME /gnome-control-center/-/issues/790 upstream seems similar ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #790 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/790 -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is "No stylus found" in the Settings. Stylus itself is working flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu 20.04 (GNOME)? Here is the xsetwacom output: xsetwacom --list Wacom HID 495F Pen stylus id: 9 type: STYLUS Wacom HID 495F Finger touch id: 10 type: TOUCH Wacom HID 495F Pen eraser id: 18 type: ERASER PS: I am currently forced to use these kernel boot parameters: i8042.nopnp=1 pci=nocrs (because of this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 ) Many Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:43:21 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-06-19 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1884746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
I disabled the color profile of both of my displays and my printer and the displays are still awake in the morning. I did check the PID of gnome-shell and it is the same so there don't appear to be any silent crashes. -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
Many thanks for helping with this, here it is (attached), Sebastian... ** Attachment added: "libinput_list-devices.log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1884746/+attachment/5386795/+files/libinput_list-devices.log.txt -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is "No stylus found" in the Settings. Stylus itself is working flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu 20.04 (GNOME)? Here is the xsetwacom output: xsetwacom --list Wacom HID 495F Pen stylus id: 9 type: STYLUS Wacom HID 495F Finger touch id: 10 type: TOUCH Wacom HID 495F Pen eraser id: 18 type: ERASER PS: I am currently forced to use these kernel boot parameters: i8042.nopnp=1 pci=nocrs (because of this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 ) Many Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:43:21 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-06-19 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1884746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Issue persists on 20.04 on the same Dell XPS 9370. Turning Wifi off still turns airplane mode on. -- 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 1884934] Re: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: libvorbis (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvorbis in Ubuntu. https://bugs.launchpad.net/bugs/1884934 Title: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 Status in libvorbis package in Ubuntu: Invalid Bug description: Getting errors while installing Wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvorbis0a 1.3.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 24 17:18:04 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libvorbis Title: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1884934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881699] Re: No analog output
No improvements with latest version in groovy (1:13.99.1-1ubuntu7) -- 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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884934] [NEW] package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different fro
Public bug reported: Getting errors while installing Wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvorbis0a 1.3.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 24 17:18:04 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libvorbis Title: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libvorbis (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 libvorbis in Ubuntu. https://bugs.launchpad.net/bugs/1884934 Title: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 Status in libvorbis package in Ubuntu: New Bug description: Getting errors while installing Wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvorbis0a 1.3.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 24 17:18:04 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libvorbis Title: package libvorbis0a 1.3.6-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libvorbis0a/changelog.Debian.gz', which is different from other instances of package libvorbis0a:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1884934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
Dell and Ubuntu have certified a few days ago the XPS 2020 9300 for 20.04 I guess I am going to move from 18.04 to 20.04 in a few days, a week at most I hope this problem will be fixed there :/ -- 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/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884932] [NEW] Install pulseaudio-module-gsettings by default
Public bug reported: It provides a very useful settings to switch all running streams when a new output becomes available. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_20200624_142941.png" https://bugs.launchpad.net/bugs/1884932/+attachment/5386777/+files/Screenshot_20200624_142941.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1884932 Title: Install pulseaudio-module-gsettings by default Status in ubuntu-meta package in Ubuntu: New Bug description: It provides a very useful settings to switch all running streams when a new output becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1884932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884924] Re: Chromium Bug that causes the browser to shut down unexpectedly/crash
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu) -- 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/1884924 Title: Chromium Bug that causes the browser to shut down unexpectedly/crash Status in chromium-browser package in Ubuntu: New Bug description: The bug pastebin from the mint report system(ubuntu dervied OS) https://termbin.com/xv63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
done ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 8
[Desktop-packages] [Bug 1884924] [NEW] Chromium Bug that causes the browser to shut down unexpectedly/crash
You have been subscribed to a public bug: The bug pastebin from the mint report system(ubuntu dervied OS) https://termbin.com/xv63 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- Chromium Bug that causes the browser to shut down unexpectedly/crash https://bugs.launchpad.net/bugs/1884924 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser 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 1883920] Re: ubuntu logo in wslfetch needs update
** Changed in: wslu (Ubuntu Groovy) Assignee: (unassigned) => Patrick Wu (callmepk) ** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/386311 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/386311 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
Please try using 'apport-cli' instead of 'ubuntu-bug'. Please also follow all the steps in comment #2. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm
[Desktop-packages] [Bug 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/386311 ** Changed in: wslu (Ubuntu Groovy) Assignee: (unassigned) => Patrick Wu (callmepk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
actually that little error window has a bunch of data in it stack seems to be () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 i'm going to try installing the symbols for that and reproduce again ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
reproduced and got a crash file but... themusicgod1@eva1:~$ ubuntu-bug /var/crash/_usr_bin_gnome- shell.1001.crash consistently results in Sorry, Ubuntu 20.04 has experienced an internal error If you notice further problems, try restarting the computer stack: /usr/bin/gnome-shell -- 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/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0
[Desktop-packages] [Bug 1883177] Re: Double menu-bar in LibreOffice 6.4.3.2 only with installed addon languagetool
Here some new information, just a second after using 'File > last used' (and the double menu appears), I got this from 'journalctl -r': {{{ ... Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.526:7843): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.526:7842): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.526:7841): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct/cpu.shares" pid=29481 comm=564D205> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct/cpu.cfs_period_us" pid=29481 comm=> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/cpu,cpuacct/cpu.cfs_quota_us" pid=29481 comm=5> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.466:7840): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.466:7839): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.442:7838): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.442:7837): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user.slice/user-1000.slice/u...@1000.se> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.418:7836): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.418:7835): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/cgroup/memory/user> Jun 24 10:56:08 matthias-buero kernel: audit: type=1400 audit(1592988968.414:7834): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/matthias/.config/Lan> Jun 24 10:56:08 matthias-buero kernel: kauditd_printk_skb: 198 callbacks suppressed Jun 24 10:56:08 matthias-buero audit[29481]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/matthias/.config/LanguageTool/LibreOffice/Languagetool.> Jun 24 10:56:06 matthias-buero gnome-shell[1693]: Window manager warning: WM_TRANSIENT_FOR window 0x24006c6 for 0x240070b window override-redirect is an override-redirect window and > }}} This 'Window manager warning' seems noticeable. -- 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/1883177 Title: Double menu-bar in LibreOffice 6.4.3.2 only with installed addon languagetool Status in libreoffice package in Ubuntu: New Bug description: Hello, I had the problem already with 18.04. Now I have reinstalled Ubuntu 20.04 64bit, automatically with LibreOffice 6.4.3.2. If I open at first within LO a saved or a recently used document, another menu-bar appears. (This doesn't happen if i open the document from Nautilus.) Te
[Desktop-packages] [Bug 1880191] Re: usb_modeswitch 2.5.2 segfault
Here it is: Starting program: /usr/sbin/usb_modeswitch -W -v 05c6 -p 1000 -K [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Take all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0x1000 StandardEject=1 [New Thread 0x77d58700 (LWP 4900)] Look for default devices ... found USB ID 17ef:481d found USB ID 0781:5567 found USB ID 1d6b:0002 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 05c6:1000 vendor ID matched product ID matched found USB ID 1d6b:0002 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 1d6b:0001 Found devices in default mode (1) Access device 006 on bus 001 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) Error: could not get description string "serial number" - Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: read error - Sending standard EJECT sequence Looking for active drivers ... Thread 1 "usb_modeswitch" received signal SIGSEGV, Segmentation fault. 0x9771 in detachDrivers () at usb_modeswitch.c:1478 1478usb_modeswitch.c: No such file or directory. (gdb) bt #0 0x9771 in detachDrivers () at usb_modeswitch.c:1478 #1 0x7109 in main (argc=, argv=) at usb_modeswitch.c:737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1880191 Title: usb_modeswitch 2.5.2 segfault Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: The version that is shipped with Ubuntu 20.04 x64 segfaults: Starting program: /usr/sbin/usb_modeswitch -W -v 05c6 -p 1000 -K [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Take all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0x1000 StandardEject=1 [New Thread 0x77d58700 (LWP 16370)] Look for default devices ... found USB ID 05ac:8406 found USB ID 1d6b:0003 found USB ID 05ac:0291 found USB ID 05ac:828f found USB ID 0a5c:4500 found USB ID 05c6:1000 vendor ID matched product ID matched found USB ID 0781:5567 found USB ID 1d6b:0002 Found devices in default mode (1) Access device 015 on bus 001 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) Error: could not get description string "serial number" - Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: read error - Sending standard EJECT sequence Looking for active drivers ... libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/1-2/bConfigurationValue failed ret=-1 errno=2 Thread 1 "usb_modeswitch" received signal SIGSEGV, Segmentation fault. 0x9771 in ?? () (gdb) bt #0 0x9771 in ?? () #1 0x7109 in ?? () #2 0x77dd10b3 in __libc_start_main (main=0x6820, argc=7, argv=0x7fffe098, init=, fini=, rtld_fini=, stack_end=0x7fffe088) at ../csu/libc-start.c:308 #3 0x7bde in ?? () I tried to compile latest available version: usb- modeswitch-2.6.0.tar.bz2 (md5: be73dcc84025794081a1d4d4e5a75e4c) and it does not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1880191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Same here: Ubuntu 20.04 Asus ROG GL552V Intel Core i7-6700HQ nvidia GeForce GTX 960M / driver version: 435.21 Monitor shows Asus splashscreen properly (before os starts) Monitor stays black (but is detected by system) It seams to not be detected by graphics card (but not sure now) -- 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/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884822] Re: nautilus search bar generates high cpu usage - no reaction on 1st double-click
** Description changed: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, user) - LANG=de_DE.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, user) + LANG=de_DE.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1884822 Title: nautilus search bar generates high cpu usage - no reaction on 1st double-click Status in nautilus package in Ubuntu: New Bug description: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.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/1884822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1884822] Re: nautilus search bar generates high cpu usage - no reaction on 1st double-click
- issue is independent from the selected folder - 'journalctl -r' shows: {{{ Jun 24 10:17:00 matthias-buero org.gnome.Nautilus[26819]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'str' Jun 24 10:17:00 matthias-buero org.gnome.Nautilus[26819]: tip=_('Scan %s for threats...') % file.get_name(), Jun 24 10:17:00 matthias-buero org.gnome.Nautilus[26819]: File "/usr/share/nautilus-python/extensions/clamtk-gnome.py", line 64, in get_file_items Jun 24 10:17:00 matthias-buero org.gnome.Nautilus[26819]: Traceback (most recent call last): Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'str' Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: tip=_('Scan %s for threats...') % file.get_name(), Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: File "/usr/share/nautilus-python/extensions/clamtk-gnome.py", line 64, in get_file_items Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: Traceback (most recent call last): Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'str' Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: tip=_('Scan %s for threats...') % file.get_name(), Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: File "/usr/share/nautilus-python/extensions/clamtk-gnome.py", line 64, in get_file_items Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: Traceback (most recent call last): Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: sys:1: Warning: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed Jun 24 10:16:58 matthias-buero org.gnome.Nautilus[26819]: sys:1: Warning: Two different plugins tried to register 'NautilusDiscBurn'. }}} - in 'top': nautilus uses for about 5 -10 sec 80% - 100% (one time 208% were shown) Am 24.06.20 um 09:01 schrieb Sebastien Bacher: > ok, if you don't want to register on gitlab it's fine > > please provide some details though > > - is the issue specific to a folder? > - do you get any error displayed in 'journalctl' when you trigger the bug? > - which processes are using the most CPU in 'top'? > -- 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/1884822 Title: nautilus search bar generates high cpu usage - no reaction on 1st double-click Status in nautilus package in Ubuntu: New Bug description: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.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/1884822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884863] Re: nautilus ignores actual mount name
Thanks! ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1537 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1537 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1537 Importance: Unknown Status: Unknown -- 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/1884863 Title: nautilus ignores actual mount name Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: insert USB-drive with name "USB-A" nautilus shows "USB-A" in the sidebar insert another USB-drive with the same name "USB-A" nautilus shows another "USB-A" in the sidebar (see attached) however /media/ shows "USB-A" and "USB-A1" (see attached) nautilus should show "USB-A" and "USB-A1" in the sidebar ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 24 11:58:26 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-31 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1884863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884863] Re: nautilus ignores actual mount name
reported at gitlab: #1537 -- 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/1884863 Title: nautilus ignores actual mount name Status in nautilus package in Ubuntu: New Bug description: insert USB-drive with name "USB-A" nautilus shows "USB-A" in the sidebar insert another USB-drive with the same name "USB-A" nautilus shows another "USB-A" in the sidebar (see attached) however /media/ shows "USB-A" and "USB-A1" (see attached) nautilus should show "USB-A" and "USB-A1" in the sidebar ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 24 11:58:26 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-31 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1884863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Description changed: + [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e + + [Test case] + Test that a proper list of modes is shown with a panel that uses the new EDID. + + [Regression potential] + should be low at this point -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: New Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] should be low at this point To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Daniel, I apologise. We have been talking about different apps. I have been referring to the browser plugin that talks to https://extensions.gnome.org/. This is because it was the first thing I spotted when I searched on the net. I realise that what you have been talking about the is a standalone app that is accessible via the applications panel or the activities search box. Yes, the standalone app works perfectly and is packaged with the shell. The browser plugin does not. I have only tested the Firefox version though. The Chrome one might be better. Thank you for being patient Roger -- 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/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884822] Re: nautilus search bar generates high cpu usage - no reaction on 1st double-click
ok, if you don't want to register on gitlab it's fine please provide some details though - is the issue specific to a folder? - do you get any error displayed in 'journalctl' when you trigger the bug? - which processes are using the most CPU in 'top'? -- 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/1884822 Title: nautilus search bar generates high cpu usage - no reaction on 1st double-click Status in nautilus package in Ubuntu: New Bug description: If I try to find e.g. a certain music file, I browse in nautilus to the folder "music" and start typing "mo": - cpu usage is prompt very high although the correct folder is shown immediatly - mouse pointer shows activity (circle rotates constantly) - if I use a double-click on the requested folder, nothing happens; only on the second try the double-click opens that folder Goal: - the first double-click should open the requested folder - cpu usage shouldn't be so high ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 20:58:45 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.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/1884822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp