[Desktop-packages] [Bug 1897995] Re: Internal speaker not working because it's treated as headphone and muted by default
** Package changed: ubuntu => alsa-utils (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1897995 Title: Internal speaker not working because it's treated as headphone and muted by default Status in alsa-utils package in Ubuntu: New Bug description: I am using Ubuntu Focal in HP Pavilion g4, the internal speaker not working, no sound at all. However it works if I run alsamixer and unmute the headphone. It's strange that the internal speaker is assumed as headphone. For your information, it happens after upgrading to Focal, it was good in the previous LTS version. For additional information, I upgraded to Focal while using external monitor that has speaker by using HDMI cable. The HDMI was connected before and after upgrade process. I don't know if this is related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-utils 1.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 09:23:53 2020 InstallationDate: Installed on 2018-12-23 (647 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: alsa-utils UpgradeStatus: Upgraded to focal on 2020-05-30 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1897995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897995] [NEW] Internal speaker not working because it's treated as headphone and muted by default
You have been subscribed to a public bug: I am using Ubuntu Focal in HP Pavilion g4, the internal speaker not working, no sound at all. However it works if I run alsamixer and unmute the headphone. It's strange that the internal speaker is assumed as headphone. For your information, it happens after upgrading to Focal, it was good in the previous LTS version. For additional information, I upgraded to Focal while using external monitor that has speaker by using HDMI cable. The HDMI was connected before and after upgrade process. I don't know if this is related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-utils 1.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 09:23:53 2020 InstallationDate: Installed on 2018-12-23 (647 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: alsa-utils UpgradeStatus: Upgraded to focal on 2020-05-30 (124 days ago) ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Internal speaker not working because it's treated as headphone and muted by default https://bugs.launchpad.net/bugs/1897995 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils 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 1895199] Re: web apps no longer launch into separate windows
For step 5 above I also sometimes deleted the app from chrome://apps and re-created it. SO the actual bug on this issue seems to be some discontinuity with my old webapp definitions because I have been able to make them work again by recreating them again. -- 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/1895199 Title: web apps no longer launch into separate windows Status in chromium-browser package in Ubuntu: New Bug description: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card"
It looks like 'pipewire' has stolen the audio devices so pulseaudio may not work properly. Please try uninstalling or reconfiguring 'pipewire'. -- 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/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" Status in pulseaudio package in Ubuntu: New Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897959] Re: Audio Shuts Down with Screen Blanking
First, can we assume your sound is not going through HDMI or DisplayPort? If it is then this is expected. What kind of sound connection are you using? Second, please follow these instructions to report the crash: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** 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/1897959 Title: Audio Shuts Down with Screen Blanking Status in gnome-shell package in Ubuntu: Incomplete Bug description: Noticed that in the last week or so when my system is playing audio when the screen timer expires the screen blanks but also the audio stops playing. Starting up as soon as the screen returns (moving the mouse). Was setting up a trial run to document by playing audio and setting the screen to blank after 1 minute. When the minute expired the screen start the blank but I got a crash in gnome-shell. The screen was returned to normal and I got a bug report notification which I sent. After another minute (did nothing else on the system) and the screen started to blank and this time completed the process. As soon as the blanking process was complete the sound turned off. Moving the mouse returned the screen and the sound. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 30 15:18:19 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-09-29 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 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/1897959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897830] Re: 20.04.1 goes fully blank (screens) after replugging 2nd monitor
Also, after the problem happens next and immediately after restarting, please run: journalctl -b-1 > prevboot.txt lspci -kv > lspci.txt and attach the resulting text files here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1897830 Title: 20.04.1 goes fully blank (screens) after replugging 2nd monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using 20.04.1-latest and using 2x monitors, 1x using DVI and 1x using HDMI, if I unplug the HDMI one while the system is running, displays will fallback to 1 screen and that is good. But while this system is still running, if/when I replug that same 2nd screen that I took out and using the same HDMI port both screens turn blank and system goes into lala land requiring a manual/hard restart is required to fix this. While the screens are blank, the system is not hung it simply lost it's displays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897830] Re: 20.04.1 goes fully blank (screens) after replugging 2nd monitor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1897830 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal multimonitor ** 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/1897830 Title: 20.04.1 goes fully blank (screens) after replugging 2nd monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using 20.04.1-latest and using 2x monitors, 1x using DVI and 1x using HDMI, if I unplug the HDMI one while the system is running, displays will fallback to 1 screen and that is good. But while this system is still running, if/when I replug that same 2nd screen that I took out and using the same HDMI port both screens turn blank and system goes into lala land requiring a manual/hard restart is required to fix this. While the screens are blank, the system is not hung it simply lost it's displays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897917] Re: Ubuntu 20.04 does not boot to GDM forever spining wheel
Do you have an external monitor connected when the problem happens? I am reminded of bug 1872159. ** Package changed: xorg-server (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Status: New => Incomplete -- 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/1897917 Title: Ubuntu 20.04 does not boot to GDM forever spining wheel Status in plymouth package in Ubuntu: Incomplete Bug description: On a basic Intel laptop : once every 2 boot , the spining whell runs forever and GDM does not show ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-common 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip Date: Wed Sep 30 17:29:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: tuxedo_keyboard, 2.0.0, 5.4.0-47-generic, x86_64: installed tuxedo_keyboard, 2.0.0, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:40c1] InstallationDate: Installed on 2020-08-13 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook NL40_50CU PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=13c54f9c-8969-4e49-822c-24d6f69ac07d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09:bd09/14/2019:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1897917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
This bug is closed so please open new bugs from now on. -- 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/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1868519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896774] Re: [ASUS UX430UQ] Headphone output stopped working after perfoming dist-upgrade
Hello, In AlsaInfo.txt, under `!!Amixer output`, the Master and Headphone audio output controls are set to off, a possible starting point for debugging this issue may be looking into trying to unset those. The file contents are just writing the output of `/usr/sbin/alsa-info.sh --stdout --no- upload`. For reference, this is part of the output from a Xenial system with working audio: https://pastebin.ubuntu.com/p/2nzBjfpC6C/ Thanks! -- 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/1896774 Title: [ASUS UX430UQ] Headphone output stopped working after perfoming dist- upgrade Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: # What happened: - Upgraded packages using: sudo apt-get update && sudo apt-get dist- upgrade - Following packages were installed: pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-bluetooth:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 - Find the complete update log attached (dpkg.log written to update_log_23_09_20.txt) # Bug description: - Loudspeaker works fine. Inserting headphones is detected correctly in sound settings but no physical output is generated on the headphone port. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 15:32:02 2020 InstallationDate: Installed on 2018-01-11 (986 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago) dmi.bios.date: 07/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897784]
The only relatively recent commit related to QMimeData handling (i.e. mostly copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in 6.4.4 already. I'm wondering whether the increase of reported crashes is actually due to some change in LibreOffice qt5/kf5 code or rather the side-effect of something completely different (like more users having installed Kubuntu 20.04 since then, or some completely different commit that changed timing in some place, ...). @jmux: Any ideas? -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897784]
No. (In reply to Michael Weghorn from comment #2)
> The only relatively recent commit related to QMimeData handling (i.e. mostly
> copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in
> 6.4.4 already.
>
> @jmux: Any ideas?
We know the fix for tdf#131533 is rather fishy and more of a workaround,
then a real fix. But if we have the same backtraces before 6.4.4 (and I
checked that libreoffice_6.3.3-0ubuntu1.debian.tar.xz doesn't carry that
fix), we can - kind of - rule that out. Also all the backtraces just
indicate Calc (ScSelectionTransferObj), not any other LO modules (at
least Writer), which is strange. Maybe an active selection in Calc is
just more common on shutdown, then in other applications? OTOH a copy in
Calc keeps the selection, even if you move the "cursor rectangle". There
is also nothing suspicious new on
https://crashreport.libreoffice.org/stats/version/6.4.6.2
And the only "fix" in vcl/qt5 between 6.4.2 and 6.4.3 is commit
1000169ebca79478a05b4c23e760d99bd77e739e ("Qt5 unify font attribute
conversions"), which I would also rule out as the origin of any bug
(famous last words).
There is also no other fix in vcl/ or sc/ since commit
cbac26c52ccbe59c51c6631cb8c4b0a314a9848a / 6.4.0, which looks suspicious
at all w.r.t. the backtrace at a first glance. And the whole lazy
clipboard stuff was already in 6.3. And your fix for tdf#129809 was
already in 6.4.2.
Still nothing would explain the current peak, I can see in
https://errors.ubuntu.com since
https://errors.ubuntu.com/?release=Ubuntu%2020.04=libreoffice-
core=2020-08-24=2020-09-25, which matches the publishing date
from
https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1
.
So I checked the diff of the 6.4.6 fix range for sc and interestingly it
contains commit 8718d243edc9400b0e0131b096702af8d33df327 (rhbz#1847031
null-deref), which fixes a null-deref in ~ScTransferOb. That should
really just fix a bug, not cause one, but eventually this just papers-
over some real bug in the other fixes, which now hits Qt in some way.
Because ScTransferObj is part of libsclo, which can't exists with
"pScMod == nullptr".
$ git log --pretty=oneline
f2e448175cee92fc695413e7281223e9f23e30ee~1..origin/libreoffice-6-4-6 | wc -l
123
Now I really would like to have a reproducer, which eventually should
also happen on master... and tdf#130559 is the only additional thing in
sc that looks strange, but that's just 17 out of the 123 patches.
Someone from Kubuntu could "mine" the crash reports, if there is
anything reproducible in it. And I have to get the RHEL bug report from
someone (Caolan, eventually).
So while I first suspected something non-LO, it now smells like a LO
bug, independent of VCL, evetually.
--
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/1897784
Title:
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData
Status in LibreOffice:
New
Status in libreoffice package in Ubuntu:
Triaged
Status in libreoffice source package in Focal:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
libreoffice. This problem was most recently seen with package version
1:6.4.6-0ubuntu0.20.04.1, the problem page at
https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897784]
Created attachment 165978 Kubuntu shutdown crash bt It appears that one can just DL the text with a Launchpad login. So this is just a copy from the BT as reference. For whatever reason the clipboard object is still active, while the module is already gone, which is causing the crash. An other question is, what other packages were published that day, just in the case it's eventually no LO bug (I still think it is). -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897784]
It's hard to pin down what other new packages could have made it onto the users system because of the way Ubuntu rolls out releases in a "phased" manner: https://wiki.ubuntu.com/StableReleaseUpdates#Phasing This is happening simultaneously for all sorts of packages too, at various stages in the phasing process. So unfortunately, there's no way to really get a sense of other new packages that might be causing the issue. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897784]
Created attachment 165976 rhbz#1847031 cleaned crash bt That whole bt looks broken. RH has no reproducer either, so the fix is just a guess. Version was libreoffice-6.4.4.2-2.fc32.x86_64, as you can see in the bt paths. The bt itself looks "wrong". The user did a right-click on a Calc cell, that would open the context menu, but at that point, when the Gtk event is processed, a lot more stuff is already "gone", like all the aGuard objects have nullptr, so no mutex in them. So I guess this is just for reference, but won't help. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
I have some further details about this bug! Not super positive, but
still.
First, I'm going to mark bug #676767 a duplicate of this. That's a
slightly older bug with the same symptom, and a workaround (of deleting
the cache) that doesn't seem to work in all cases. But ultimately, it's
indistinguishable from this, so I'll dup it.
Second, I was recently helping a user that was affected by this. They
were on Ubuntu 14.04 moving to 16.04 (meaning a backup made with
duplicity 0.6.23-1ubuntu4.1 and deja-dup 30.0-0ubuntu4.1, trying to
restore with duplicity 0.7.06-2ubuntu2 and deja-dup 34.2-0ubuntu1.1).
After investigating it with them, we found that many (100s!) of their
volume files (size 50mb) were all zeros. That is, not valid gzip files
but just a file full of zero-bytes.
Other files seemed corrupted in a different way (not valid gzip, but not
all zeros either). There were less of these.
They did not use encryption. They stopped and resumed the backup a few
times. It was altogether a single full backup.
I don't know what to do with this information. But there it is.
I note that we don't see this often anymore? The latest report here is
from 18.04, which would be duplicity 0.7.17-0ubuntu1.1. It may be too
optimistic to hope that it's solved now. But certainly less common than
it used to be, I think?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), )
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://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 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
For me, as far I remember, to fix the issue on my local machine, I have to remove python and reinstalled it.It seems that after upgrading ubuntu18 to ubuntu focal, some python 2 footprints still remains, I am not sure if it was the cause of issue but after removing python and purging both python2 and the newly installed python 3, and reinstalled python3, It works. On Thu, 1 Oct 2020 at 00:25, Foobar <1891...@bugs.launchpad.net> wrote: > To be clear, I have since successfully upgraded but done so by: > > 0. (running apt-get update, dist-upgrade, etc to prepare) > 1. deinstalling (via apt-get) gdm3 > 2. booting into recovery mode & initiating networking > 3. running do-release-upgrade > 4. restarting the system. > > I don't think I can exactly 'recommend' this way of doing it, but for me > it was successful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891165 > > Title: > gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but > 3.28.4-0ubuntu18.04.2 is to be installed > > Status in gsettings-desktop-schemas package in Ubuntu: > Confirmed > > Bug description: > I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 > install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run > sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in > https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. > But i got more errors > > > The following packages have unmet dependencies: >gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but > 3.28.4-0ubuntu18.04.2 is to be installed >libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but > 3.26.1-2ubuntu1 is to be installed > E: Error, pkgProblemResolver::Resolve generated breaks, this may be > caused by held packages. > > sudo ln -sf /usr/bin/python2.7 /usr/bin/python > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: mutter 3.28.4-0ubuntu18.04.2 > ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Aug 11 20:38:08 2020 > InstallationDate: Installed on 2020-02-08 (184 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: mutter > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895199] Re: web apps no longer launch into separate windows
OK I have been digging around. I was reading https://askubuntu.com/questions/31427 hoping it would give me some clues, and it didn't HOWEVER another web search or two and I found https://askubuntu.com/questions/910494 and here's what I came up with that seems to work: 1) Open Chromium 2) navigate to chrome://apps 3) right-click on icon for the created application 4) choose "Open as Window" 5) If the window doesn't behave properly in the favorites bar, delete it from Favorites and open it again and re-add it to favorites. -- 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/1895199 Title: web apps no longer launch into separate windows Status in chromium-browser package in Ubuntu: New Bug description: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894715] Re: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1894715 Title: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist Status in sane-backends package in Ubuntu: Confirmed Bug description: Following warning displayed during install Setting up sane-utils (1.0.29-0ubuntu5.1) ... update-inetd: warning: cannot add service, /etc/inetd.conf does not exist ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 09:31:24 2020 InstallationDate: Installed on 2019-03-30 (526 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190318) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sane-backends UpgradeStatus: Upgraded to focal on 2020-05-15 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1894715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895199] Re: web apps no longer launch into separate windows
On the above, I have discovered that if I double-click the weird .desktop file, I get a message asking if I should trust and launch it, and when I agree to trust and launch, the name changes to the intended name AND the icon of the file changes to reflect the proper "webapp." For example, messages.google.com gains the messages icon and renames to "Messages." HOWEVER it STILL doesn't open in a separate window in my old user account. I presume there's still some cruft somewhere. -- 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/1895199 Title: web apps no longer launch into separate windows Status in chromium-browser package in Ubuntu: New Bug description: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card"
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+attachment/5415818/+files/dmesg -- 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/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" Status in pulseaudio package in Ubuntu: New Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card"
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+attachment/5415820/+files/syslog ** Description changed: No sound after login. - $ LC_ALL=C systemctl --user status pulseaudio.service + $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service - Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) - Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago + Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) + Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket -Main PID: 1088 (pulseaudio) - CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service - |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal - `-1126 /usr/libexec/pulse/gsettings-helper + Main PID: 1088 (pulseaudio) + CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service + |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal + `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) - Workaround found: 'pulseaudio -k' solves the problem. + Workaround found: 'pulseaudio -k' seems solves the problem: + + $ LC_ALL=C systemctl --user status pulseaudio.service + * pulseaudio.service - Sound Service + Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) + Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago + TriggeredBy: * pulseaudio.socket +Main PID: 12198 (pulseaudio) + CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service + |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal + `-12212 /usr/libexec/pulse/gsettings-helper + + Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... + Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 + Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 + Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. + Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. + ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: eugene 1088 F pulseaudio - eugene 1092 F pipewire-media- - /dev/snd/controlC1: eugene 1092 F pipewire-media- - /dev/snd/seq:eugene 1087 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: eugene 1088 F pulseaudio + eugene 1092 F pipewire-media- + /dev/snd/controlC1: eugene 1092 F pipewire-media- + /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: - LANGUAGE= - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=uk_UA.UTF-8 - SHELL=/bin/bash + LANGUAGE= + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=uk_UA.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1897965] [NEW] pulseaudio: Failed to load module "module-alsa-card"
Public bug reported: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" Status in pulseaudio package in Ubuntu: New Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio
[Desktop-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card"
-- 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/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" Status in pulseaudio package in Ubuntu: New Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897962] Re: Out of Memory Error with Brother DCP-J7720W
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1897962 Title: Out of Memory Error with Brother DCP-J7720W Status in sane-backends package in Ubuntu: Confirmed Bug description: Installed XSane from the repository but when I scan the viewer screen is blank and if I try to save I get "Error during save: out of memory" I believe that escl driver in 20.04 sane-backends is a problem and it is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962539 sane-backends 1.0.31 should be considered for focal-backports and that if possible, escl driver could be individually SRU (Stable release update) in focal-updates. ppa:sane-project/sane-git fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1897962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897962] [NEW] Out of Memory Error with Brother DCP-J7720W
Public bug reported: Installed XSane from the repository but when I scan the viewer screen is blank and if I try to save I get "Error during save: out of memory" I believe that escl driver in 20.04 sane-backends is a problem and it is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962539 sane-backends 1.0.31 should be considered for focal-backports and that if possible, escl driver could be individually SRU (Stable release update) in focal-updates. ppa:sane-project/sane-git fixes the issue. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1897962 Title: Out of Memory Error with Brother DCP-J7720W Status in sane-backends package in Ubuntu: Confirmed Bug description: Installed XSane from the repository but when I scan the viewer screen is blank and if I try to save I get "Error during save: out of memory" I believe that escl driver in 20.04 sane-backends is a problem and it is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962539 sane-backends 1.0.31 should be considered for focal-backports and that if possible, escl driver could be individually SRU (Stable release update) in focal-updates. ppa:sane-project/sane-git fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1897962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897959] [NEW] Audio Shuts Down with Screen Blanking
Public bug reported: Noticed that in the last week or so when my system is playing audio when the screen timer expires the screen blanks but also the audio stops playing. Starting up as soon as the screen returns (moving the mouse). Was setting up a trial run to document by playing audio and setting the screen to blank after 1 minute. When the minute expired the screen start the blank but I got a crash in gnome-shell. The screen was returned to normal and I got a bug report notification which I sent. After another minute (did nothing else on the system) and the screen started to blank and this time completed the process. As soon as the blanking process was complete the sound turned off. Moving the mouse returned the screen and the sound. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 30 15:18:19 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-09-29 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Snippet of the journal at the time of the failures. About 15:11 and 15:12" https://bugs.launchpad.net/bugs/1897959/+attachment/5415798/+files/PowerOffAudio.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1897959 Title: Audio Shuts Down with Screen Blanking Status in gnome-shell package in Ubuntu: New Bug description: Noticed that in the last week or so when my system is playing audio when the screen timer expires the screen blanks but also the audio stops playing. Starting up as soon as the screen returns (moving the mouse). Was setting up a trial run to document by playing audio and setting the screen to blank after 1 minute. When the minute expired the screen start the blank but I got a crash in gnome-shell. The screen was returned to normal and I got a bug report notification which I sent. After another minute (did nothing else on the system) and the screen started to blank and this time completed the process. As soon as the blanking process was complete the sound turned off. Moving the mouse returned the screen and the sound. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 30 15:18:19 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-09-29 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 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/1897959/+subscriptions -- Mailing list: https://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 1883174] Re: Some desktop icons disappear
Yes, I understand. But it seems that the ubuntu session blocks new versions from extensions.gnome.org. AFAIK, they did that to avoid a new version from the repository to overwrite the official, tested one. So it seems that you will need to use the gnome shell session instead. But the other extensions will work in both sessions, at most you will only have to enable them again. El 30/9/20 a las 20:36, John Hoff escribió: > I am not sure I am following. To be clearer, I have multiple other > extensions installed and they all work fine... specifically unite, > walkpaper, user themes and workspace indicator. It is just the desktop > icons one that I can't install or work with. I do already have gnome- > shell-extensions installed... > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897830] Re: 20.04.1 goes fully blank (screens) after replugging 2nd monitor
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1897830 Title: 20.04.1 goes fully blank (screens) after replugging 2nd monitor Status in gnome-shell package in Ubuntu: New Bug description: Using 20.04.1-latest and using 2x monitors, 1x using DVI and 1x using HDMI, if I unplug the HDMI one while the system is running, displays will fallback to 1 screen and that is good. But while this system is still running, if/when I replug that same 2nd screen that I took out and using the same HDMI port both screens turn blank and system goes into lala land requiring a manual/hard restart is required to fix this. While the screens are blank, the system is not hung it simply lost it's displays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892635] Re: mysql-direct-connector not working
Already tried. Too time wasted. You say: it is not our fault. LibreOffice say: it is not our fault. Apechefriends say: it is not our fault. Now it turns out it's the users fault. What a nightmare! We were never asked to jump through hoops to get mysql-direct-connector to work. Why we are being asked now? Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892635 Title: mysql-direct-connector not working Status in libreoffice package in Ubuntu: New Bug description: After upgrading to (k)ubuntu 20.04.1, both with LibreOffice 6.4. and LibreOffice 7, mysql direct connector doesn't work any more (unlike in (k)ubuntu 18.04 and LO 6.0). Mysql (mariadb, installed with lampp) is perfectly working in browsers: I can see php+mysql pages in localhost, without any problem. But if I try to open a database odb connected with mysql I get an error message [code] Code: SQL Status: HY000 Error code: 2003 Can't connect to MySQL server on 'localhost' (111) /build/libreoffice-ron9it/libreoffice-7.0.0~rc3/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:119 [/code] I believe that is a problem of mysql-connector provided with Ubuntu, in the past so useful (because LO extension are not working). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897830] [NEW] 20.04.1 goes fully blank (screens) after replugging 2nd monitor
You have been subscribed to a public bug: Using 20.04.1-latest and using 2x monitors, 1x using DVI and 1x using HDMI, if I unplug the HDMI one while the system is running, displays will fallback to 1 screen and that is good. But while this system is still running, if/when I replug that same 2nd screen that I took out and using the same HDMI port both screens turn blank and system goes into lala land requiring a manual/hard restart is required to fix this. While the screens are blank, the system is not hung it simply lost it's displays. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 20.04.1 goes fully blank (screens) after replugging 2nd monitor https://bugs.launchpad.net/bugs/1897830 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1883174] Re: Some desktop icons disappear
I am not sure I am following. To be clearer, I have multiple other extensions installed and they all work fine... specifically unite, walkpaper, user themes and workspace indicator. It is just the desktop icons one that I can't install or work with. I do already have gnome- shell-extensions installed... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://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 1883174] Re: Some desktop icons disappear
Oh, ok... Now I understand. You simply can't install the official desktop icons in the Ubuntu session. You must install gnome-session, choose gnome shell session instead of Ubuntu session when logging, and there you can use the extensions. Of course, you may want to also install dash-to-dock, that gives you the left dock, and kstatusNotifier. El mié., 30 sept. 2020 20:11, John Hoff <1883...@bugs.launchpad.net> escribió: > I rebooted multiple times and no luck. > > Here are the steps I followed : > > - Used sudo apt remove gnome-shell-extension-desktop-icons to uninstall > > - Deleted the folder $HOME/.local/share/gnome-shell/extensions/desktop- > icons@csoriano > > - Rebooted and verified it is gone all together from tweaks > > - Downloaded the .zip patch file and placed in a local directory > > - Rerean the Meson/Ninja commands and verified that the .local folder > was recreated (I did not get any errors) > > - Rebooted again. > > At this point I still do not have desktop icons as a choice at all in > Tweaks -> extensions. If I go to the website > (https://extensions.gnome.org/) then it is not listed in the installed > extensions list. If I search for it and try to turn it on with the web > page I get a message that says "Can't install "desktop-icons@csoriano" : > This is an extension enabled by your current mode, you can't install > manually any update in that session" > > So basically I am stuck with no option to turn it back on. I suspect I > can just run sudo apt install and readd that way, but it will be the > same /usr install.Am I missing something? > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1883174 > > Title: > Some desktop icons disappear > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I was hit by this issue, when for some reason the left clicks (but not the right ones) on the touchpad were occasionally blocked (Ubuntu 18.04 kernel 5.4.0-48). Disabling the extensions (I had two: appindicators and dock) solved the issue. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
I rebooted multiple times and no luck. Here are the steps I followed : - Used sudo apt remove gnome-shell-extension-desktop-icons to uninstall - Deleted the folder $HOME/.local/share/gnome-shell/extensions/desktop- icons@csoriano - Rebooted and verified it is gone all together from tweaks - Downloaded the .zip patch file and placed in a local directory - Rerean the Meson/Ninja commands and verified that the .local folder was recreated (I did not get any errors) - Rebooted again. At this point I still do not have desktop icons as a choice at all in Tweaks -> extensions. If I go to the website (https://extensions.gnome.org/) then it is not listed in the installed extensions list. If I search for it and try to turn it on with the web page I get a message that says "Can't install "desktop-icons@csoriano" : This is an extension enabled by your current mode, you can't install manually any update in that session" So basically I am stuck with no option to turn it back on. I suspect I can just run sudo apt install and readd that way, but it will be the same /usr install.Am I missing something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from groovy
Why would we stop providing those packages before Adobe's EOL date? Please note that the packages exist and are (usually) updated on all stable releases. How would it make sense to not ship them with groovy? I would suggest that they are shipped with groovy as usual, and that the packages are replaced with dummies in all stable releases once EOL has been reached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from groovy Status in adobe-flashplugin package in Ubuntu: New Status in flashplugin-nonfree package in Ubuntu: New Status in pepperflashplugin-nonfree package in Ubuntu: New Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in groovy. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in groovy? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897934] Re: The initial sound level is set to zero (mute)
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1897934 ** Tags added: iso-testing -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in pulseaudio package in Ubuntu: New Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892635] Re: mysql-direct-connector not working
Hmm I read through the comment history in the upstream bug you pointed to and I'm not convinced it is a problem in Ubuntu either because of the final two comments. Alex set it up in Linux Mint (which a previous comment correctly pointed out that it pulls the relevant packages from Ubuntu) and it worked just fine. Could you try some of the suggestions the upstream developers recommended? -- 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/1892635 Title: mysql-direct-connector not working Status in libreoffice package in Ubuntu: New Bug description: After upgrading to (k)ubuntu 20.04.1, both with LibreOffice 6.4. and LibreOffice 7, mysql direct connector doesn't work any more (unlike in (k)ubuntu 18.04 and LO 6.0). Mysql (mariadb, installed with lampp) is perfectly working in browsers: I can see php+mysql pages in localhost, without any problem. But if I try to open a database odb connected with mysql I get an error message [code] Code: SQL Status: HY000 Error code: 2003 Can't connect to MySQL server on 'localhost' (111) /build/libreoffice-ron9it/libreoffice-7.0.0~rc3/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:119 [/code] I believe that is a problem of mysql-connector provided with Ubuntu, in the past so useful (because LO extension are not working). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
To be clear, I have since successfully upgraded but done so by: 0. (running apt-get update, dist-upgrade, etc to prepare) 1. deinstalling (via apt-get) gdm3 2. booting into recovery mode & initiating networking 3. running do-release-upgrade 4. restarting the system. I don't think I can exactly 'recommend' this way of doing it, but for me it was successful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897934] [NEW] The initial sound level is set to zero (mute)
Public bug reported: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in pulseaudio package in Ubuntu: New Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer
** Bug watch added: Red Hat Bugzilla #1413858 https://bugzilla.redhat.com/show_bug.cgi?id=1413858 ** Also affects: wayland-protocols (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1413858 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/1857655 Title: gdkselection-wayland.c:275: error reading selection buffer Status in nautilus package in Ubuntu: Expired Status in wayland-protocols package in Fedora: Unknown Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No error. 4) Error in Logs app. 6:41:01 PM nautilus: ../../../../../gdk/wayland/gdkselection- wayland.c:275: error reading selection buffer: Operation was cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857655/+subscriptions -- Mailing list: https://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 1883174] Re: Some desktop icons disappear
Don't forget to exit and enter again from gnome shell El mié., 30 sept. 2020 17:41, John Hoff <1883...@bugs.launchpad.net> escribió: > Nevermind, I figured out its just sudo apt remove gnome-shell-extension- > desktop-icons. > > I did that and its completely gone from /usr now. However, I no longer > have the extension at all. I reran the steps to install the patch > version and I don't see the extension, so I must be missing a step > somewhere... > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1883174 > > Title: > Some desktop icons disappear > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw()
freon doesn't seem to work with 3.36, wsmatrix I've disabled now and the
shell still crashes, also when starting firefox
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw()
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
Nevermind, I figured out its just sudo apt remove gnome-shell-extension- desktop-icons. I did that and its completely gone from /usr now. However, I no longer have the extension at all. I reran the steps to install the patch version and I don't see the extension, so I must be missing a step somewhere... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897917] [NEW] Ubuntu 20.04 does not boot to GDM forever spining wheel
Public bug reported: On a basic Intel laptop : once every 2 boot , the spining whell runs forever and GDM does not show ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-common 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip Date: Wed Sep 30 17:29:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: tuxedo_keyboard, 2.0.0, 5.4.0-47-generic, x86_64: installed tuxedo_keyboard, 2.0.0, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:40c1] InstallationDate: Installed on 2020-08-13 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook NL40_50CU PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=13c54f9c-8969-4e49-822c-24d6f69ac07d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09:bd09/14/2019:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Ubuntu 20.04 does not boot to GDM forver spining + Ubuntu 20.04 does not boot to GDM forever spining wheel -- 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/1897917 Title: Ubuntu 20.04 does not boot to GDM forever spining wheel Status in xorg-server package in Ubuntu: New Bug description: On a basic Intel laptop : once every 2 boot , the spining whell runs forever and GDM does not show ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-common 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip Date: Wed Sep 30 17:29:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: tuxedo_keyboard, 2.0.0, 5.4.0-47-generic, x86_64: installed tuxedo_keyboard, 2.0.0, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:40c1] InstallationDate: Installed on 2020-08-13 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook NL40_50CU PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=13c54f9c-8969-4e49-822c-24d6f69ac07d ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.vendor: INSYDE Corp.
[Desktop-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
Looks ok to me from a Feature Freeze perspective (but it would be nice to have an answer to Yuan-Chen's concern, from a technical perspective). Aside, on ubuntu-drivers-common: +Files: share/hybrid/json-parser/* +Copyright: Copyright (c) 2012, 2013 James McLaughlin et al. +License: BSD + Please don't use 'BSD' as a license descriptor, it's ambiguous. https://www.debian.org/doc/packaging-manuals/copyright-format/1.0 /#license-specification (also, is there a reason you're embedding a json parser instead of building against json-c which is supported in main?) On nvidia-prime: > +self._nvidia_runtimepm_file = '/lib/modprobe.d/nvidia- runtimepm.conf' Why are you managing files under /lib instead of under /etc? (this is a preexisting pattern so not a blocker, but it would be nice if this could be corrected at some point) ** Changed in: nvidia-prime (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-prime package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- Mailing list: https://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 1883174] Re: Some desktop icons disappear
The package is "gnome-shell-extension-desktop-icons" El mié., 30 sept. 2020 17:26, John Hoff <1883...@bugs.launchpad.net> escribió: > How do you uninstall it properly? I enabled it through the > https://extensions.gnome.org/ page, but there is not an uninstall option > there. It does not show up as an installed .deb in ubuntu software, so > I am assuming we need to do a sudo apt remove, but not sure what package > is called > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1883174 > > Title: > Some desktop icons disappear > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
How do you uninstall it properly? I enabled it through the https://extensions.gnome.org/ page, but there is not an uninstall option there. It does not show up as an installed .deb in ubuntu software, so I am assuming we need to do a sudo apt remove, but not sure what package is called -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://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 1883174] Re: Some desktop icons disappear
That's the problem: the package isn't installed in the local folder, but in /usr. You must uninstall it. El mié., 30 sept. 2020 16:26, John Hoff <1883...@bugs.launchpad.net> escribió: > The editor I am using is just gedit 3.36.2, just fyi... > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1883174 > > Title: > Some desktop icons disappear > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
On my video, we can see: start the commands > I switch to marco adaptive compositor in Mate tweaks > the whole system is broken, mouse and keyboard freeze > after 37s the system reboot > we can see my grub menu at the end (dual boot). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1869444] Re: Task Manager tab: File systems completely wrong
Sorry udiskSctl my error, see log annex ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+attachment/5415692/+files/log -- 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/1869444 Title: Task Manager tab: File systems completely wrong Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: See the screenshot in the annex with system monitor and disk utility display: With respect to the display of the file systems tab in Ubuntu 20.04 booted from zfs, we could say: "All similarity to reality is purely coincidental" :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869444] Re: Task Manager tab: File systems completely wrong
See annex for df and udiskctl not working and uninstallable. See: bertadmin@Host-R3:~$ udiskctl dump Command 'udiskctl' not found, did you mean: command 'udisksctl' from deb udisks2 (2.8.4-1ubuntu1) Try: sudo apt install bertadmin@Host-R3:~$ sudo apt install udisks2 Reading package lists... Done Building dependency tree Reading state information... Done udisks2 is already the newest version (2.8.4-1ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ** Attachment added: "output of: df" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+attachment/5415690/+files/df -- 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/1869444 Title: Task Manager tab: File systems completely wrong Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: See the screenshot in the annex with system monitor and disk utility display: With respect to the display of the file systems tab in Ubuntu 20.04 booted from zfs, we could say: "All similarity to reality is purely coincidental" :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
As promised, here attached my video screencast. What I did in the video : I execute the following command then immediately, I switch to marco adaptive compositor, in order to show you this issue. The commands begin with a sleep of 7s, then switch to compiz (installed on my system), then sleep 7s and finally reboot. I use this command because my system is half freeze while this issue is coming, without display, mouse and keyboard freeze too. As you can see, with the kernel 5,8 and the amdgpu driver mesa 20,3 this issue is worst ! Let me what I can do to help. I insist, I can do some tests for you, tell me what to do. $ sleep 7s ; compiz --replace & sleep 7s ; reboot ** Attachment added: "issue with amd mesa 20.3" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1873895/+attachment/5415691/+files/20200930_163449.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 @dgoosens I updated my kernel to 5.6.10-050610-generic but still not working. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
I did not uninstall per say, I just deleted the .local directory as mentioned in the readme... i.e. Deleted the folder ($HOME/.local/share/gnome-shell/extensions /desktop-icons@csoriano) If there is a better way to clear and reinstall then let me know and I will be happy to try it out... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
The editor I am using is just gedit 3.36.2, just fyi... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801205] Re: Can't mount veracrypt volumes
Thank you for your bug report, it sounds similar to what is discussed on https://github.com/storaged-project/udisks/issues/589 Did you try to create a /etc/udisks2/tcrypt.conf ? ** Bug watch added: github.com/storaged-project/udisks/issues #589 https://github.com/storaged-project/udisks/issues/589 ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low -- 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/1801205 Title: Can't mount veracrypt volumes Status in gnome-disk-utility package in Ubuntu: New Bug description: Using mount from nautilus (open with) or right from Gnome Disk, the file in question is "mounted" as a loop device. Therefore, no opening of that container nor questions about how to open the file. This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live session) and Gnome on Xorg & Wayland. Also tryed Tail in order to see the Veracrypt property working. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-disk-utility 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 1 18:35:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (146 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1801205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
Thank you for your bug report, that was reported upstream in https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/178 and is fixed in git master now (should be in Ubuntu next cycle) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #178 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/178 ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Fix Committed -- 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/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: Fix Committed Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
My guess. “/home/ion420/Desktop/.goutputstream-0LONR0” is a temporary file, probably the editor is saving a new file to then move over the original one when you save. The extension notices the new file but when trying to get more info about it, it's gone (race condition). It probably does not recover well from this scenario. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869444] Re: Task Manager tab: File systems completely wrong
Thank you for your bug report, could you include the log from those commands? $ udiskctl dump > log $ df -h ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Incomplete -- 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/1869444 Title: Task Manager tab: File systems completely wrong Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: See the screenshot in the annex with system monitor and disk utility display: With respect to the display of the file systems tab in Ubuntu 20.04 booted from zfs, we could say: "All similarity to reality is purely coincidental" :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
Your guess is correct. The problem is that the line numbers in your log doesn't match my line numbers... Did you uninstall the gnome-shell- extensions-desktop-icons.deb package before installing the branch from gitlab? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826391] Re: UI allows dangerous mistakes
Thank you for your bug report, I'm not going to try to format my system partition but if there is no warning in the case one user try to do that it's an issue. Could ypu perhaps report it upstream as well on https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues ? ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => High ** Summary changed: - UI allows dangerous mistakes + Doesn't warn before formatting the system partition -- 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/1826391 Title: Doesn't warn before formatting the system partition Status in gnome-disk-utility package in Ubuntu: New Bug description: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1826391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I have raised a bug with LibreOffice which I believe may be related. https://bugs.documentfoundation.org/show_bug.cgi?id=137142 To summarise, with a scaling factor of 1.25 and GNOME Desktop Environment Universal Access accessibility Large Print set to on I am unable to see fully the LibreOffice Print dialogue. Setting Large Print to off cures the problem BUT my low vision means I really need to squint. Setting the scaling factor to 1.0 also succeeds but rather bizarrely also automatically switches off GNOME Desktop Environment Universal Access accessibility Large Print. Is all this related? And will the forthcoming fix correct everything including the LibreOffice and Universal Access accessibility Large Print? ** Bug watch added: Document Foundation Bugzilla #137142 https://bugs.documentfoundation.org/show_bug.cgi?id=137142 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
Sure, it must be some sort of interaction or missing dependency because I get it every single time I save a file that is on the desktop. I reproduced the error then immediately pulled the tail of the log you proposed. I do see a javascript error related to this extension... Here is the full tail... (hard to read) Sep 30 09:25:03 iP4o20Kn gnome-shell[1611]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 48 failed: Permission denied Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: GNOME Shell started at Wed Sep 30 2020 09:25:02 GMT-0400 (EDT) Sep 30 09:25:04 iP4o20Kn gnome-shell[3617]: Registering session with GDM Sep 30 09:25:18 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 5236: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 5236 does not exist. Sep 30 09:25:33 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 5312: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 5312 does not exist. Sep 30 09:25:35 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 5316: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 5316 does not exist. Sep 30 09:25:36 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 5320: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 5320 does not exist. Sep 30 09:26:06 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 5400: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 5400 does not exist. Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Sep 30 09:26:08 iP4o20Kn gnome-shell[3617]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Sep 30 09:26:18 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 6526: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 6526 does not exist. Sep 30 09:26:34 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 6527: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 6527 does not exist. Sep 30 09:26:41 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 6533: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 6533 does not exist. Sep 30 09:26:44 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 6538: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 6538 does not exist. Sep 30 09:26:45 iP4o20Kn gnome-shell[3617]: Could not create transient scope for PID 6539:
[Desktop-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
My desktop is still being re-logged randomly. How do I know if this is a problem or not? -- 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/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1868519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
7 days have passed. I'm waiting the package be released to "-updates". LoL -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
Re-opening since this is a reasonable request. Binding shortcuts/actions to additional mouse buttons seems reasonable. Even if there's no explicit Qt support (is this still true?) we could still implement it ourselves on the KDE side. -- 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/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
*** Bug 424369 has been marked as a duplicate of this bug. *** -- 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/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
*** Bug 272728 has been marked as a duplicate of this bug. *** -- 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/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949]
*** Bug 386670 has been marked as a duplicate of this bug. *** -- 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/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62949] Re: No way to configure mouse button number
** Changed in: kdelibs Status: Won't Fix => Unknown -- 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/62949 Title: No way to configure mouse button number Status in kdelibs: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog
** Changed in: rtkit Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in Rtkit: New Status in rtkit package in Ubuntu: Confirmed Status in rtkit package in Debian: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rtkit/+bug/1547589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897754] Re: The icon does not appear in the GNOME bar
Mh, so... I've just tried with the flameshot snap and the latest extension version, but it works correctly here. Please, try to do as follow: - Start a session without flameshot started In a terminal run: journalctl -b0 /usr/bin/gnome-shell -ef Launch flameshot Tell me what debug output do you get while running it. If none, we may need to raise the debugging level, you can add it by editing /usr/lib/systemd/user/gnome-shell-x11.service (or wayland) so that it contains a line Environment=G_MESSAGES_DEBUG=all In the [Service] stanza. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: https://github.com/flameshot-org/flameshot/issues/1009 --- When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
Verified on focal using 1:13.99.1-1ubuntu3.7 ** Tags removed: 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Selected audio output device in Settings is ignored after upgrading to Ubuntu 20.04. [Test Case] Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to 20.04. When done, attempt to connect a Bluetooth or USB audio device and use it via Settings. [Regression Potential] Unknown/low. The fix is from upstream and has already been released to Ubuntu 20.10 without any problems. Only worth noting it works by detecting and removing audio configurations made via older versions of PulseAudio. So upon upgrading some old settings may be reset to defaults, but the idea is that's less bad than audio devices being unusable (this bug). [Original Bug Report] Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
Well, I've now spent a couple of hours starting from 19.10, upgrading to 20.04, trying to reproduce this bug and then testing the proposed package. Somewhat predictably I cannot reproduce the bug. But I can confirm the focal-proposed package works well. So that's probably as good a verification as we can get. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Selected audio output device in Settings is ignored after upgrading to Ubuntu 20.04. [Test Case] Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to 20.04. When done, attempt to connect a Bluetooth or USB audio device and use it via Settings. [Regression Potential] Unknown/low. The fix is from upstream and has already been released to Ubuntu 20.10 without any problems. Only worth noting it works by detecting and removing audio configurations made via older versions of PulseAudio. So upon upgrading some old settings may be reset to defaults, but the idea is that's less bad than audio devices being unusable (this bug). [Original Bug Report] Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892635] Re: mysql-direct-connector not working
any news? I have reported this bug here (https://bugs.documentfoundation.org/show_bug.cgi?id=134982), but the coclusion is that this is not their fault, but yours. Are you doing something to resolve this bug? Thanks ** Bug watch added: Document Foundation Bugzilla #134982 https://bugs.documentfoundation.org/show_bug.cgi?id=134982 -- 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/1892635 Title: mysql-direct-connector not working Status in libreoffice package in Ubuntu: New Bug description: After upgrading to (k)ubuntu 20.04.1, both with LibreOffice 6.4. and LibreOffice 7, mysql direct connector doesn't work any more (unlike in (k)ubuntu 18.04 and LO 6.0). Mysql (mariadb, installed with lampp) is perfectly working in browsers: I can see php+mysql pages in localhost, without any problem. But if I try to open a database odb connected with mysql I get an error message [code] Code: SQL Status: HY000 Error code: 2003 Can't connect to MySQL server on 'localhost' (111) /build/libreoffice-ron9it/libreoffice-7.0.0~rc3/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:119 [/code] I believe that is a problem of mysql-connector provided with Ubuntu, in the past so useful (because LO extension are not working). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font
Verified the test case using language-selector-{common,gnome} 0.204.2
from focal-proposed.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1896397
Title:
[UIFe] Tweak Arabic font
Status in language-selector package in Ubuntu:
Fix Released
Status in language-selector source package in Focal:
Fix Committed
Bug description:
[Impact]
This is a follow-up of bug #1891733. After the new default font for
Arabic had made it to focal, we got some additional feedback at
. After further discussion,
trial and error, and multiple changes in groovy it has landed in a
consensus to make these adjustments:
* Rename the .conf file from 69- to 56-
* Drop binding="strong"
* Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace
The significance of the changes, which motivates the proposed SRU, is
made up of:
1. Use DejaVu Sans Mono as default Arabic font for monospace
instead of the previous non-mono font
2. No longer conflicts with Kubuntu's custom font configuration
[Test case]
* Install the language-selector-{gnome,common} packages
from focal-proposed.
* Open the Language Support tool and install Arabic.
* Open a terminal window, run the below commands and confirm
that you get the same output:
$ LC_CTYPE=ar_EG.UTF-8 fc-match
NotoSansArabicUI-Regular.ttf: "Noto Sans Arabic UI" "Regular"
$ LC_CTYPE=ar_EG.UTF-8 fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
[Regression risk]
For some users this will change the default monospace font for
rendering Arabic. That's the point. :)
The change will only affect users with an Arabic locale. The risk that
other users would be affected by the change is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
I've just updated from 18.04.5 to 20.04.1 and the calendar stopped working - none of my calendars are showing up. This seems to be another snap-related issue, as the apt installation (version 3.36.2) works fine. I tried removing and reinstalling the snap (version 3.30.0) but it didn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897873] [NEW] nautilus doesn't display thumbnails on NFS network share
Public bug reported: Nautilus is set to show thumbnails in all locations. When viewing a NAS share, it will not display thumbnails for a NFS mount. Just generic image icon is displayed for both jpg and movies. If I view the same folder in Nautilus via samba, the thumbnails will generate and display OK. Thunar will generate and display thumbnails OK on NFS and samba. Permissions are sound. Works on 18.04 as expected, and NAS has not changed since 18.04 in use. I just replicated this on a VM build of Ubuntu desktop 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 09:55:52 2020 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-09-29 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Nautilus is set to show thumbnails in all locations. When viewing a NAS share, it will not display thumbnails for a NFS mount. Just generic image icon is displayed for both jpg and movies. - If I view the same folder via samba, the thumbnails will generate and display OK. + If I view the same folder in Nautilus via samba, the thumbnails will + generate and display OK. + + Thunar will generate and display thumbnails OK on NFS and samba. + + Permissions are sound. Works on 18.04 as expected, and NAS has not changed since 18.04 in use. I just replicated this on a VM build of Ubuntu desktop 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 09:55:52 2020 ExecutablePath: /usr/bin/nautilus GsettingsChanges: - b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" - b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" + b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" + b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-09-29 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=en_GB:en - LANG=en_GB.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=en_GB:en + LANG=en_GB.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/1897873 Title: nautilus doesn't display thumbnails on NFS network share Status in nautilus package in Ubuntu: New Bug description: Nautilus is set to show thumbnails in all locations. When viewing a NAS share, it will not display thumbnails for a NFS mount. Just generic image icon is displayed for both jpg and movies. If I view the same folder in Nautilus via samba, the thumbnails will generate and display OK. Thunar will generate and display thumbnails OK on NFS and samba. Permissions are sound. Works on 18.04 as expected, and NAS has not changed since 18.04 in use. I just replicated this on a VM build of Ubuntu desktop 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64
[Desktop-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog
** Bug watch added: github.com/heftig/rtkit/issues #22 https://github.com/heftig/rtkit/issues/22 ** Also affects: rtkit via https://github.com/heftig/rtkit/issues/22 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in Rtkit: Unknown Status in rtkit package in Ubuntu: Confirmed Status in rtkit package in Debian: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rtkit/+bug/1547589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849162] Re: Lightning extension should be installed and enabled by default
Thunderbird 78 is now in groovy, and in the process of being backported to focal, and later bionic and xenial. ** Changed in: thunderbird (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1849162 Title: Lightning extension should be installed and enabled by default Status in thunderbird package in Ubuntu: Fix Released Bug description: Upstream builds of thunderbird are now shipping lightning, and it is enabled by default. In contrast, lightning in Ubuntu is a separate binary package (xul- ext-lightning), and it’s neither installed by default nor even recommended by thunderbird. This results in confusion for users who don't know where to get lightning from. The extension should be bundled with the thunderbird package, i.e. installed and enabled by default (as was done for the wetransfer file link provider, see bug #1823361). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)
Resolving hosts in Chromium stopped working after applying the changes as described in: https://bugs.launchpad.net/ubuntu/+source/network- manager-strongswan/+bug/1864256/comments/3 Firefox and Chrome still could resolve host names. -- 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/1876083 Title: chromium snap from focal fails DNS lookups, or delays them (ipv6) Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: When working with the chromium snap included in focal, it sometimes takes a few seconds to lookup an URL, sometimes it cannot resolve the hostname of the URL at all. Doing the same browsing using firefox doesn't show such behavior, no timeouts, no failed lookups, no delays. Any way how to debug that? That is using IPv6 only. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1876083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
I tried that, but I'm unable to reproduce that bug. Can you check if there is any error message in the gnome shell logs? (you can see them from a terminal with "sudo journalctl /usr/bin/gnome- shell", and pressing the "END" key to go to the end of the file). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11
** Description changed: - Mesa 20.2.0 has been delayed by upstream, but we still want it in 20.10. - It's currrently at rc4, final was supposed to be out a month ago. It's - been in debian experimental since rc1. + Mesa 20.2.0 was released on Sep 28th a month late, but we still want it + in 20.10. It's been in debian experimental since rc1. The packaging in + debian also migrates to use llvm 11. - The packaging in debian also migrates to use llvm 11. + The risks involve graphical issues or even crashes when running more + intense OpenGL/Vulkan apps like games. Running a desktop is a simple + use-case and should work fine across the board. Upstream gitlab has a + fairly extensive CI for various drivers, while Intel tests on their own + CI. This means that any showstoppers should be shaken out already. + + We will be able to pull maybe two point-releases before groovy is + frozen, and then push more as an SRU. + + I've tested 20.2.0 on Intel and AMD (RX 5700) and the latter too with + some games, all good. packages for groovy are available on ppa:canonical-x/x-staging -- 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/1896577 Title: FFE: new upstream release 20.2 and migrate to llvm 11 Status in mesa package in Ubuntu: New Bug description: Mesa 20.2.0 was released on Sep 28th a month late, but we still want it in 20.10. It's been in debian experimental since rc1. The packaging in debian also migrates to use llvm 11. The risks involve graphical issues or even crashes when running more intense OpenGL/Vulkan apps like games. Running a desktop is a simple use-case and should work fine across the board. Upstream gitlab has a fairly extensive CI for various drivers, while Intel tests on their own CI. This means that any showstoppers should be shaken out already. We will be able to pull maybe two point-releases before groovy is frozen, and then push more as an SRU. I've tested 20.2.0 on Intel and AMD (RX 5700) and the latter too with some games, all good. packages for groovy are available on ppa:canonical-x/x-staging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1896577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873378] Re: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873378 Title: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact The user panel hits a segfault sometimes * Test case Check that reports stop on https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca * Regression potential The change is in the user panel's user initial avatar generation, check that the default image for profiles without an avatar is still generated --- Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Package version: 1:3.36.1-1ubuntu4 The application was running in the background, with only Chrome running at the same time. It's a mid-2014 MacBook Pro, so some drivers are not very stable and can cause this kind of issues. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 23:41:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-10 (250 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d PC (0x7f303176e6e4) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%r15d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 generate_default_avatar () ?? () ?? () Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize() UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897281] Re: evince suicides in 20.04 but not in 18.04
> Would it not be easier for you, if you downloaded this CBR file and tried to open it in Ubuntu 20.04 yourself? I did and it works fine, maybe the issue is the resource usage, how much free memory do you have avaible? could you check with top if maybe that's the issue and that opening it exhause the available resources for you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 Status in evince package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897856] Re: snap launch fails: symbol lookup error
Thanks, indeed it requires a newer gdk-pixbuf, you can workaround by doing $ sudo snap refresh --candidate gnome-3-34-1804 ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => Confirmed ** Changed in: evince (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897856 Title: snap launch fails: symbol lookup error Status in evince package in Ubuntu: Confirmed Bug description: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
3.36.4-0ubuntu2 fixes the issue Thanks! ** Tags removed: 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Status in gnome-control-center source package in Groovy: Fix Released Bug description: * Impact The details of the connection settings sometime overlap * Test case Connect the computer to a wired ethernet, go to settings and check the connection details, the items should be displayed separated and not overlapping * Regression potential Check that the connection details dialog is correctly displayed on different typo of connections, the change is in the layout of the elements so it could impact the layout in other cases To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log_structured_array() from g_log_default_handler() from ?? from g_logv() from g_log("Error in freeze/thaw accounting") from
** Summary changed:
- gnome-shell crashed with signal 5 in g_log_structured_array() from
g_log_default_handler() from ?? from g_logv() from g_log() from
meta_window_actor_thaw()
+ gnome-shell crashed with signal 5 in g_log_structured_array() from
g_log_default_handler() from ?? from g_logv() from g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw()
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1431
https://gitlab.gnome.org/GNOME/mutter/-/issues/1431
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1431
Importance: Unknown
Status: Unknown
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- gnome-shell crashed with signal 5 in g_log_structured_array() from
g_log_default_handler() from ?? from g_logv() from g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw()
+ gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting")
from meta_window_actor_thaw()
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw()
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log_structured_array() from g_log_default_handler() from ?? from g_logv() from g_log() from meta_window_actor_thaw()
Just launching `terminator` does not seem to cause a crash for me. Can you check if removing your extensions avoids the issue? 'wsmat...@martin.zurowietz.de', 'freon@UshakovVasilii_Github.yahoo.com' ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1897765 Title: gnome-shell crashed with signal 5 in g_log_structured_array() from g_log_default_handler() from ?? from g_logv() from g_log() from meta_window_actor_thaw() Status in gnome-shell package in Ubuntu: Incomplete Bug description: Launching terminator crashes gnome-shell, happens on two separate machines. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 18:05:57 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1600706451 InstallationDate: Installed on 2019-10-14 (350 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/tjaalton ProcEnviron: LANG=fi_FI.UTF-8 PATH=(custom, user) SHELL=/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897858] [NEW] [UIFe] IBus 1.5.23
Public bug reported: Do we want IBus 1.5.23 in groovy? I built it successfully here: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus and it seems to run smoothly. debian/ is from Debian's repo and only modified with the patch adjustments necessary to apply to the new upstream. Upstream's release notes: https://github.com/ibus/ibus/releases/tag/1.5.23 The biggest change is that /usr/share/ibus/component/simple.xml, with the XKB keyboard layouts, is significantly larger than before. The UI for adding input methods seems to handle it fine. But the additional layouts should be seen as a bug fix IMO, in response to the bugs mentioned at bug #1835541. Otherwise it's mostly bug fixes (and insignificant low risk improvements). The UIFe request is due to some new translatable strings. I will notify the documentation and translation teams if this is approved. ** Affects: ibus (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1897858 Title: [UIFe] IBus 1.5.23 Status in ibus package in Ubuntu: New Bug description: Do we want IBus 1.5.23 in groovy? I built it successfully here: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus and it seems to run smoothly. debian/ is from Debian's repo and only modified with the patch adjustments necessary to apply to the new upstream. Upstream's release notes: https://github.com/ibus/ibus/releases/tag/1.5.23 The biggest change is that /usr/share/ibus/component/simple.xml, with the XKB keyboard layouts, is significantly larger than before. The UI for adding input methods seems to handle it fine. But the additional layouts should be seen as a bug fix IMO, in response to the bugs mentioned at bug #1835541. Otherwise it's mostly bug fixes (and insignificant low risk improvements). The UIFe request is due to some new translatable strings. I will notify the documentation and translation teams if this is approved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1897858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897856] [NEW] snap launch fails: symbol lookup error
Public bug reported: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897856 Title: snap launch fails: symbol lookup error Status in evince package in Ubuntu: New Bug description: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589147] Re: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem
** Changed in: alsa-driver (Ubuntu) Assignee: Kirill (kir0179) => (unassigned) -- 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/1589147 Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Haven't sound at front output and have sound only rear side In mixer stand mute at headphones for default and no save, after changes and reboot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kirill 1684 F pulseaudio /dev/snd/controlC0: kirill 1684 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 4 23:51:09 2016 InstallationDate: Installed on 2016-06-04 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7817 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1589147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
