[Desktop-packages] [Bug 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
There is no bug in the glibc/expat dependencies here. The libexpat1 in bionic Depends: libc6 (>= 2.25), which is the version that provides this symbol. The problem is that new libexpat1 has been unpacked (but not configured) before the new libc6, so anything which depends on libexpat1 does not have its dependencies satisfied, and the xenial version of gir1.2-ibus-1.0 appears to invoke python3 in its prerm script, which fails. I'm not sure if it's possible for apt to fix this, or if it would need to be fixed in the gir1.2-ibus-1.0 maintainer script to handle the case where py3clean is executable but fails. Of course this maintainer script is also generated by dh_python3, so fixing it might take a bit of effort. -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862704] Re: some times no respond many applications and take very much time to start SO
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1862704 Title: some times no respond many applications and take very much time to start SO Status in gnome-shell package in Ubuntu: Expired Bug description: Hardware SSD Kingston 12 GB Ram Disk change to only read and another storage device connected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 18:28:28 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-13 (242 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-24 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
Not reproducible on fresh install on same hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu Status in xorg package in Ubuntu: New Bug description: Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect x.org drivers for RX 5500 XT. Those drivers appear to be missing features like multi-monitor support. On the other hand live- usb of 20.04 beta did manage to utilize all 3 connected monitors (before crashing), so the issue may also be related to upgrading process (used do-release-upgrade since update-managed does not scale down to 800x600 fallback which 18.04 used with unsupported hardware). Yes, this report is in need of some triaging, unless it happens to be a clear duplicate of another bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 22:01:36 2020 DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-46-generic, x86_64: installed nvidia, 390.132, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2016-09-25 (1292 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) XorgConf: Section "Device" Identifier "AMD" Driver "amdgpu" EndSection dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Apr 9 04:46:16 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.7-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings
This bug seems still to be present in Xubuntu 20.04 To be able to switch keyboard layouts after reboot (or logout), I need to go to keyboard settings, change the keyboard layout switch key to something else (and then back again, though that's not absolutely necessary). It's not so bad on my main machine, because that tends to be left running for days at a time, but on a laptop I imagine it would be really frustrating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/1805197 Title: cannot switching keyboard layout with xfce4-keyboard-settings Status in Xfce4 Settings: Confirmed Status in libxklavier package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Confirmed Bug description: This is on xubuntu 18.04: With xfce4-keyboard-settings I have loaded the keyboard layouts "English (US)" and "German". Both are listed in the "Keybord layout" table. When I change the order with [key up] or [key down] nothing happens, I still have the old keyboard layout active. To switch the layout I have to DELETE the other one! This was not the case with xubuntu 16.04: just changing the order was sufficent there. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Changed in: libxml2
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
New
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797791] Re: nvidia-440 installation issues need to be resolved and the package marked as 'tested'
I can also confirm that the nvidia-340 package in 20.04 builds usable kernel modules and works fine on the same 2008 MacPro with Mac rom'd GTX680. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1797791 Title: nvidia-440 installation issues need to be resolved and the package marked as 'tested' Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: The nvidia-graphics-drivers-340 is essential to many users. For example, on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version graphic card, the nvidia 360, 390 and 396 drivers all fail due to issues with the new nvidia_drm module resulting in no video output on DVI and HDMI. https://devtalk.nvidia.com/default/topic/1042691/linux/black-screen- with-mac-version-of-gtx-680/1 Similiar issues exist for a number of PC users as well... https://devtalk.nvidia.com/default/topic/1037997/xid-61-black-screen- on-startup-ubuntu-18-04-gtx-1060-mobile/ of which only some have been resolved. The nvidia-340 drivers are the recommended fall back according to the Nvidia linux developers. Unfortunately, the installation of the current nvidia-340 340.107-0ubuntu2 packaging is in really bad shape. The first error one sees while attempting to install it are dpkg-divert errors like those described in https://askubuntu.com/questions/419304/dpkg-divert-error- rename-involves-overwriting-usr-lib-xorg-protocol-txt-wit but for the files... /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib. /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib Currently one has to manually move these aside under a .bak suffix to get past these post-removal script errors. I believe these issues may be already addressed in the current nvidia-340 packaging residing on the ppa:graphics-drivers/ppa repo. The second installation issue that occurs is the same as that described in https://askubuntu.com/questions/969352/uninstalling-and- then-reinstalling-nvidia-384-kills-colord where currently the fix is the same. One has to edit the installed nvidia-340.postinst file and change NEWEST_KERNEL=$(get_newest_kernel "$(KERNEL") to NEWEST_KERNEL=$(get_newest_kernel "$CURRENT_KERNEL") following executing sudo dpkg-reconfigure nvidia-340 to allow the installation to cleanly complete. Lastly, there seems to be a missing dependency on the nvidia-340-dev that prevents akmods from building the kernel modules which should be fixed. The nvidia-340 drivers are supported until the end of 2019 by which time hopefully Nvidia will finally clean up their current issues with the newer drivers on problematic hardware. https://nvidia.custhelp.com/app/answers/detail/a_id/3142 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-340 340.107-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 12:41:21 2018 InstallationDate: Installed on 2018-04-26 (170 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1797791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871961] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871961 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in gnome-shell package in Ubuntu: Confirmed Bug description: send me news thanks ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:09:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f2b2e6e4494 : movsbl (%rdi),%eax PC (0x7f2b2e6e4494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Changed in: libxml2
Remote watch: bugzilla.gnome.org/ #789714 =>
gitlab.gnome.org/GNOME/libxml2/issues #64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
Unknown
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Also affects: libxml2 via
https://bugzilla.gnome.org/show_bug.cgi?id=789714
Importance: Unknown
Status: Unknown
** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/-/issues #12
https://gitlab.gnome.org/GNOME/libxml2/-/issues/12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
Unknown
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871715] Re: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart
It indeed sounds very resembling to what I had, but not the exact thing. I will open a new ticket with the details once (or if) it happens again. Thanks for reviewing. -- 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/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart Status in gnome-control-center package in Ubuntu: Triaged Bug description: After alsa force-reload the Sounds in the Settings crashed. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 00:17:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-05 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-control-center sound SegvAnalysis: Segfault happened at: 0x7fd52df10daf:mov%esi,(%rdx) PC (0x7fd52df10daf) ok source "%esi" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 pa_context_set_sink_volume_by_index () from /lib/x86_64-linux-gnu/libpulse.so.0 ?? () gvc_mixer_stream_push_volume () ?? () Title: gnome-control-center crashed with SIGSEGV in pa_context_set_sink_volume_by_index() UpgradeStatus: Upgraded to focal on 2020-04-05 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871296] Re: Activities not showing some files in search in overview
This bug was fixed in the package nautilus - 1:3.36.1.1-1ubuntu2 --- nautilus (1:3.36.1.1-1ubuntu2) focal; urgency=medium * debian/patches/gitlab_tracker_fixes.patch: - backport upstream candidate fixes to resolve files not being listed anymore in the GNOME activity screen (lp: #1871296) -- Sebastien Bacher Fri, 10 Apr 2020 16:08:10 +0200 ** Changed in: nautilus (Ubuntu) Status: In Progress => Fix Released -- 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/1871296 Title: Activities not showing some files in search in overview Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: I am facing an issue with the new version of Gnome (3.36) in Ubuntu 20.04. The problem is as follows: I copied files inside home folder (e.g., documents, images, videos) and subfolders, then waited for tracker to index, then do a search trough overview and in Nautilus. The result: Nautilus shows all the files when searched, but these files are not showed in Activities view (search in Activities). I have checked that the respective tracker options are appropriately configured. Also, this is happening (at least for me) only with Nautilus 3.36. I have not found this behavior with the previous 3.34.x version. There is a bug issue in Gnome: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1412 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 02:27:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-05 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-04-05T20:36:45.617982 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1871296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** No longer affects: itstool (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871324] Re: Merge gvfs 1.44.1-1 (main) from Debian unstable (main)
** Changed in: gvfs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1871324 Title: Merge gvfs 1.44.1-1 (main) from Debian unstable (main) Status in gvfs package in Ubuntu: New Bug description: Please merge gvfs 1.44.1-1 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. It's a bug-fix release. https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS Major changes in 1.44.1 === * udisks2: Fix several memory leaks * Translation updates Explanation of the Ubuntu delta: * Resynchronize on Debian, the remaining changes - Revert upstream changes to port to fuse 3. This is in universe in Ubuntu and we'll need to work out how to move over. * debian/patches/gitlab_updated_certificate.patch: - update the test certificate, fix the tests with the new libssl * Revert the hacks from the previous upload * No-change upload with strops.h and sys/strops.h removed in glibc. Changelog entries since current focal version 1.44.0-1ubuntu1: gvfs (1.44.1-1) unstable; urgency=medium * New upstream release -- Jeremy Bicha Sun, 29 Mar 2020 00:09:58 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1871324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871882] Re: gnome-session-bin package cannot function without gnome-session
Autologin is not in use. The only unusual aspect of this login is that it is via xrdp, and because no argument is passed to the initial /etc/X11/Xsession invocation, it uses the default x-session-manager -> gnome-session . If the user logs in via the console, xfce4-session is used instead, masking the problem. (I tested with an empty user home directory, so there is no user config to confound the problem.) On an Ubuntu desktop system, gnome-session-binary loads /usr/share /gnome-session/sessions/gnome-login.session which is provided by gdm3. So the dependency for gnome-session-bin could be stated as "gnome- session | gdm3". The problem can be reproduced by using /usr/bin/gnome-session as the session manager, with neither the gnome-session nor gdm3 packages installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: gnome-session-bin package cannot function without gnome-session Status in gnome-session package in Ubuntu: Incomplete Bug description: This concerns gnome-session-bin 3.36.0-2ubuntu1 in Ubuntu focal. When I log into a Xubuntu desktop via xrdp, an error occurs, and the session terminates before the desktop is even drawn on the screen. I looked in syslog, and saw this: Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:12:23 test-ubuntu64 gnome-session[1900]: gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 systemd[1760]: gnome-session-manager@gnome.service: Main process exited, code=exited, status=1/FAILURE I edited /usr/lib/systemd/user/gnome-session-manager@.service to add the --debug option to the gnome-session-binary invocation, and tried again. Now I saw this: Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818#012 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]:
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
** Summary changed: - super key does not work in Persian keyboard layout + super key does not work with secondary keyboard layout -- 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/1871913 Title: super key does not work with secondary keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872142] Re: gnome-calendar crashed with SIGSEGV in g_list_length()
*** This bug is a duplicate of bug 1871188 *** https://bugs.launchpad.net/bugs/1871188 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1871188, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872142/+attachment/5351568/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351570/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351574/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351575/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351576/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351577/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872142/+attachment/5351578/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1871188 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1872142 Title: gnome-calendar crashed with SIGSEGV in g_list_length() Status in gnome-calendar package in Ubuntu: New Bug description: I just open up calendar and look around and then it shuts down. I have synchronized a couple of google calendar and they did appear correctly and I was able to change views and look at the settings menu some time - something that did not happen two weeks ago when I tried this out last time. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 23:40:05 2020 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2020-03-28 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f0aa74d0b40 : mov 0x8(%rdi),%rdi PC (0x7f0aa74d0b40) ok source "0x8(%rdi)" (0x2000a) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_list_length () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () gcal_week_header_add_event () ?? () ?? () Title: gnome-calendar crashed with SIGSEGV in g_list_length() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1872142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872141] evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch()
StacktraceTop: ?? () invoke_set_property_in_idle_cb (_data=0x7f9f34012820) at ../../../gio/gdbusconnection.c:4225 g_main_context_dispatch () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 g_main_context_iterate.isra () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 g_main_loop_run () from /tmp/apport_sandbox_ax_n61ir/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872141] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351566/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872141] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351567/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872141/+attachment/5351556/+files/CoreDump.gz ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Medium ** Summary changed: - evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() + evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872141] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872141/+attachment/5351565/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872141] [NEW] evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb()
Public bug reported: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0:Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en_US SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-crash focal ** Information type changed from Private to Public ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete ** Description changed: + [Joshua Peisach] + I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Fri Apr 10 16:34:34 2020 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/libexec/evolution-source-registry InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcCmdline: /usr/libexec/evolution-source-registry ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= - LANGUAGE=en_US + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= + LANGUAGE=en_US SegvAnalysis: - Segfault happened at: 0x0: Cannot access memory at address 0x0 - PC (0x) not located in a known VMA region (needed executable region)! + Segfault happened at: 0x0: Cannot access memory at address 0x0 + PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: - ?? () - ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 - g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () + ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872141 Title: evolution-source-registry crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: [Joshua Peisach] I was just installing: ubuntu-mate-desktop and ubuntu-mate-* Then for some reason it just crashed, I have no idea what happened. I was trying to add an addition to python code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evolution-data-server 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64
[Desktop-packages] [Bug 1871913] Re: super key does not work in Persian keyboard layout
That's exactly right. When I change the order, it will work only in Persian. -- 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/1871913 Title: super key does not work in Persian keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872110] Re: sonido
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872110 Title: sonido Status in xorg package in Ubuntu: New Bug description: tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y no hay forma, necesito una ayuda para poder quedarme con este sistema operativo, muchas gracias. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18 Uname: Linux 4.15.0-97-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 10 14:00:24 2020 DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 seconds (printer-driver-foo2zjs (i386) instalado) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx Integrated Graphics Controller [144d:c664] InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 00OT dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Intel powered classmate PC dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.board.version: 0.1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1: dmi.product.family: CedarTrail System dmi.product.name: 100NZA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Apr 10 13:45:55 2020 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872110] [NEW] sonido
You have been subscribed to a public bug: tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y no hay forma, necesito una ayuda para poder quedarme con este sistema operativo, muchas gracias. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18 Uname: Linux 4.15.0-97-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 10 14:00:24 2020 DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 seconds (printer-driver-foo2zjs (i386) instalado) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx Integrated Graphics Controller [144d:c664] InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 00OT dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Intel powered classmate PC dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.board.version: 0.1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1: dmi.product.family: CedarTrail System dmi.product.name: 100NZA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Apr 10 13:45:55 2020 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 ubuntu -- sonido https://bugs.launchpad.net/bugs/1872110 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1871148] Re: services start before apparmor profiles are loaded
Adding a snapd Ubuntu task, marking as In Progress and assigning to mvo since he is preparing a 20.04 upload. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu Focal) Assignee: (unassigned) => Michael Vogt (mvo) ** Changed in: snapd (Ubuntu Focal) Status: New => In Progress ** Changed in: snapd (Ubuntu Focal) Importance: Undecided => High ** Changed in: snapd (Ubuntu Focal) Milestone: None => ubuntu-20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: In Progress Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
keep having the same modinfo error on all kernels 5.6.x , running Ubuntu 20.04. modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory On kernel 5.5.16 this modinfo error does not appear. Since the report also have this same message, maybe someone knows something ? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
To the sponsor:
libxml2 2.9.10+dfsg-5, including the patch, is now available in Debian
unstable. So please sync libxml2.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872126] [NEW] focal: Firefox YouTube videos full screen motion glitch/tearing
Public bug reported: https://www.youtube.com/watch?v=MfL_JkcEFbE Intel® Core™ i7-8700 CPU @ 3.20GHz × 12 Mesa Intel® UHD Graphics 630 (CFL GT2) HDMI to Sony TV 1920x1080 Playing YouTube video full screen in Firefox there is some fast motion glitch/tearing. The problem does not show in chromium on same machine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi9241 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 22:05:40 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) IpRoute: default via 192.168.88.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.88.0/24 dev wlo1 proto kernel scope link src 192.168.88.109 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872126 Title: focal: Firefox YouTube videos full screen motion glitch/tearing Status in firefox package in Ubuntu: New Bug description: https://www.youtube.com/watch?v=MfL_JkcEFbE Intel® Core™ i7-8700 CPU @ 3.20GHz × 12 Mesa Intel® UHD Graphics 630 (CFL GT2) HDMI to Sony TV 1920x1080 Playing YouTube video full screen in Firefox there is some fast motion glitch/tearing. The problem does not show in chromium on same machine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi9241 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 22:05:40 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) IpRoute: default via 192.168.88.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.88.0/24 dev wlo1
[Desktop-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871961] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871961 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in gnome-shell package in Ubuntu: New Bug description: send me news thanks ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:09:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f2b2e6e4494 : movsbl (%rdi),%eax PC (0x7f2b2e6e4494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
I can reliably reproduce this bug: 1) Boot into Ubuntu 20.04 Beta - But will not trigger if you are signed into Ubuntu One already - I am booting the ISO using grml-liveboot 2) Open Settings 3) Click About (bottom of left pane) 4) Click Software Updates (bottom of right pane) 5) In the Software & Updates dialog click the Livepatch tab (last tab) 6) Wait for Livepatch to tell you that you need to sign into Ubuntu One 7) Click the Sign in... button 8) Click the Sign in / Register... button >> bug triggered << -- 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871715] Re: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart
the other issue sounds like https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832 ** Bug watch added: PulseAudio #832 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832 -- 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/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart Status in gnome-control-center package in Ubuntu: Triaged Bug description: After alsa force-reload the Sounds in the Settings crashed. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 00:17:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-05 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-control-center sound SegvAnalysis: Segfault happened at: 0x7fd52df10daf:mov%esi,(%rdx) PC (0x7fd52df10daf) ok source "%esi" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 pa_context_set_sink_volume_by_index () from /lib/x86_64-linux-gnu/libpulse.so.0 ?? () gvc_mixer_stream_push_volume () ?? () Title: gnome-control-center crashed with SIGSEGV in pa_context_set_sink_volume_by_index() UpgradeStatus: Upgraded to focal on 2020-04-05 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
@Gunnar, thanks for testing! The sleep is a workaround, not a proper fix though. I would guess that something in the gtk widgets used is taking a grab which prevents the shell to be able to displays it's dialog so the proper fix would be to try to understand if that's an event or something we need to wait on before doing the call to polkit. If I don't success to find a better fix I will upload the sleep workaround -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871519] Re: Cannot Adjust for TV and Scale at same time (simultaneously)
Attached is the output of `journalctl -b 0` as requested. I had a terminal open and ran `logger [LP1871519] ...` as I interacted with the settings dialog to help you track down what is going wrong. I will answer your other questions in another comment as I cant see them when attaching files ** Attachment added: "journalctl as requested" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871519/+attachment/5351482/+files/journalctl_-b_0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871519 Title: Cannot Adjust for TV and Scale at same time (simultaneously) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: ## Version tested: Ubuntu 20.04 Beta ## Reproduction steps: Boot Ubuntu 20.04 Beta ISO Launch Settings window Open the Display settings Click the button to set scale to 200% Push green apply button at top right of window (screen resize) Push Keep Changes button Click the button to set scale to 100% AND click the Adjust for TV slider Push green apply button at top right of window Push Keep Changes button >>> Adjust for TV is complete but scale is NOT 100% <<< >>> Adjust for TV slider is turned off still <<< Click the button to set scale to 100% Push green apply button at top right of window >>> Adjust for TV is turned off now (properly reflecting the slider value) <<< Click the button to set scale to 100% Push green apply button at top right of window Screen is finally adjust back to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 02:15:56 2020 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871519] Re: Cannot Adjust for TV and Scale at same time (simultaneously)
> Could you add a screenshot to the bug showing the control UI? image is attached. > What monitors config do you use? I have one monitor, a Viewsonic 23" VS14880 (https://www.viewsonic.com/us/vx2370smh-led.html) ** Attachment added: "display control ui" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871519/+attachment/5351493/+files/Screenshot%20from%202020-04-10%2018-15-35.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871519 Title: Cannot Adjust for TV and Scale at same time (simultaneously) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: ## Version tested: Ubuntu 20.04 Beta ## Reproduction steps: Boot Ubuntu 20.04 Beta ISO Launch Settings window Open the Display settings Click the button to set scale to 200% Push green apply button at top right of window (screen resize) Push Keep Changes button Click the button to set scale to 100% AND click the Adjust for TV slider Push green apply button at top right of window Push Keep Changes button >>> Adjust for TV is complete but scale is NOT 100% <<< >>> Adjust for TV slider is turned off still <<< Click the button to set scale to 100% Push green apply button at top right of window >>> Adjust for TV is turned off now (properly reflecting the slider value) <<< Click the button to set scale to 100% Push green apply button at top right of window Screen is finally adjust back to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 02:15:56 2020 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871715] Re: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart
Thanks for reviewing. The need to force restart arisen due to another issue - no connectivity through Bluetooth of my Sony headphones. It was recognized through the Sound setting, but the sound itself still came through another source (my screen for this matter). I think it might be a good idea to open a separate bug ticket for the not connectivity of the headphones. Kind regards, DS. -- 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/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart Status in gnome-control-center package in Ubuntu: Triaged Bug description: After alsa force-reload the Sounds in the Settings crashed. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 00:17:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-05 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-control-center sound SegvAnalysis: Segfault happened at: 0x7fd52df10daf:mov%esi,(%rdx) PC (0x7fd52df10daf) ok source "%esi" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 pa_context_set_sink_volume_by_index () from /lib/x86_64-linux-gnu/libpulse.so.0 ?? () gvc_mixer_stream_push_volume () ?? () Title: gnome-control-center crashed with SIGSEGV in pa_context_set_sink_volume_by_index() UpgradeStatus: Upgraded to focal on 2020-04-05 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work in Persian keyboard layout
After more testing, if I change the order of the input sources, the problem only exists if I'm on any source that's not the first one. After changing the order, now the problem exists in the portuguese layout but not in the english one. @dani.behzi, can you also test that this is the same with you? -- 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/1871913 Title: super key does not work in Persian keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work in Persian keyboard layout
Well, this bug affects me but in a slightly different way: it works in portuguese layout, but not in english layout (more precisely using the english international with AltGr + dead keys). But the other shortcuts using the left Super key work fine. I'm also on the Ubuntu 20.04 and the problem only appear after today updates. -- 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/1871913 Title: super key does not work in Persian keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Sorry, I didn't know where to open this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work in Persian keyboard layout
Looking at my upgrade history, I found this entry: Start-Date: 2020-04-10 11:02:49 Commandline: /usr/bin/unattended-upgrade Upgrade: gnome-shell-extension-prefs:amd64 (3.36.0-2ubuntu2, 3.36.1-4ubuntu1), gnome-shell-common:amd64 (3.36.0-2ubuntu2, 3.36.1-4ubuntu1), gnome-shell:amd64 (3.36.0-2ubuntu2, 3.36.1-4ubuntu1) End-Date: 2020-04-10 11:02:52 I'll look into how to find the change log from gnome-shell-common, which is the package I suspect is the culprit of this error... -- 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/1871913 Title: super key does not work in Persian keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872111] [NEW] gnome-software should not provide ubuntu-software
Public bug reported: The gnome-software deb provides an ubuntu-software desktop file. This is now provided by the snap-store snap so should be removed from the deb to prevent confusion ** Affects: gnome-software (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Triaged ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu) Status: New => Triaged ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872111 Title: gnome-software should not provide ubuntu-software Status in gnome-software package in Ubuntu: Triaged Bug description: The gnome-software deb provides an ubuntu-software desktop file. This is now provided by the snap-store snap so should be removed from the deb to prevent confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work in Persian keyboard layout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work in Persian keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821953] Re: warty-final-ubuntu.png is overwritten in revision 269
OK, then this is not a bug, but a feature. Thanks for clarification. ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1821953 Title: warty-final-ubuntu.png is overwritten in revision 269 Status in ubuntu-wallpapers package in Ubuntu: Invalid Bug description: I've just noticed that warty-final-ubuntu.png is overwritten in https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu- wallpapers/ubuntu/revision/269 by what should be disco-final- ubuntu.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
@Sebastien: I can confirm that your workaround fixes it for me. (Race condition?) Would be nice if it could be uploaded to focal to start with... -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852254] Re: Dock stays ontop of Xscreensaver
*** This bug is a duplicate of bug 1849787 *** https://bugs.launchpad.net/bugs/1849787 My problem is that whenever I go fullscreen in Firefox (F11) or clicking in Youtube Fullscreen icon, after some 5 seconds or so, the dock starts showing and hiding itself really quick. I see a decrease in performance. I have a 4k display, and I use fractional scaling. Pointer is not near the dock. Dock is set to auto hide. Firefox Developer Edition 75. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1852254 Title: Dock stays ontop of Xscreensaver Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date at 12/11/2019 As requested on bug: https://bugs.launchpad.net/ubuntu/+source/gnome- shell-extension-ubuntu-dock/+bug/1849787 I am creating a new bug for gnome-shell as several users experience the dock to be ontop My case the dock stays ontop of Xscreensaver, but only at random times i cannot reproduce when ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 14:49:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-25 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-10-25T10:03:18.026469 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1852254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872105] Re: nautilus crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1857736 *** https://bugs.launchpad.net/bugs/1857736 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1857736, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872105/+attachment/5351435/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351437/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351441/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351442/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351443/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351444/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872105/+attachment/5351445/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1857736 nautilus crashed with SIGABRT ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1872105 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() Status in nautilus package in Ubuntu: New Bug description: Nautilus crashed when trying to access iPhone storage. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 10 21:34:24 2020 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'type', 'date_modified']" b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" 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-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
It is really, really not the terminal emulator's job to set basic environment variables. It should either be done by the environment in which gnome-terminal is started (e.g. systemd --user), so that the terminal just transparently passes this on; or should be done by the shell initialization files, as in your workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872103] [NEW] After update to 6.4.2.2: Split database only accessible while running in Safe Mode
Public bug reported: I updated LibreOffice from 6.0.7 to 6.4.2.2 via ppa:libreoffice/libreoffice-6-4. Now I get an error when trying to open a form in a HSQLDB 2.3.2 split database: “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When running in Safe Mode, I can access the database. But even when using a new, clean profile, I can't access the database! When starting LibreOffice with LC_ALL=C libreoffice I can open a form within the database but then an error like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. I tried installing the DEB packages provided on https://www.libreoffice.org/download/download/ , same version 6.4.2.2, and there the split database is working as expected. I reported this bug wrongly first here: https://bugs.documentfoundation.org/show_bug.cgi?id=132009 Steps to Reproduce: 1. Update LibreOffice from 6.0.7 to 6.4.2.2 on Ubuntu 18.04.4 using https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-4 2. Start LO and open a split database (Use this test database: http://bugs.documentfoundation.org/attachment.cgi?id=159465 ) 3. Click on a table Actual Results: Seeing following error message (when using German localization as normally) “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When starting LO with LC_ALL=C libreoffice I can open a form within the database but then an error message like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. So the database is not usable at all. Expected Results: The split database should be accessible. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: de Module: OfficeDatabaseDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.18.04.3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (C); UI-Language: en-US Calc: threaded Ubuntu 18.04.4 LTS ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: packaging ppa -- 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/1872103 Title: After update to 6.4.2.2: Split database only accessible while running in Safe Mode Status in libreoffice package in Ubuntu: New Bug description: I updated LibreOffice from 6.0.7 to 6.4.2.2 via ppa:libreoffice/libreoffice-6-4. Now I get an error when trying to open a form in a HSQLDB 2.3.2 split database: “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When running in Safe Mode, I can access the database. But even when using a new, clean profile, I can't access the database! When starting LibreOffice with LC_ALL=C libreoffice I can open a form within the database but then an error like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. I tried installing the DEB packages provided on https://www.libreoffice.org/download/download/ , same version 6.4.2.2, and there the split database is working as expected. I reported this bug wrongly first here: https://bugs.documentfoundation.org/show_bug.cgi?id=132009 Steps to Reproduce: 1. Update LibreOffice from 6.0.7 to 6.4.2.2 on Ubuntu 18.04.4 using https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-4 2. Start LO and open a split database (Use this test database: http://bugs.documentfoundation.org/attachment.cgi?id=159465 ) 3. Click on a table Actual Results: Seeing following error message (when using German localization as normally) “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When starting LO with LC_ALL=C libreoffice I can open a form within the database but then an error message like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. So the database is not usable at all. Expected Results: The split database should be accessible. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: de Module: OfficeDatabaseDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.18.04.3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (C); UI-Language: en-US Calc: threaded Ubuntu 18.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1872103/+subscriptions --
[Desktop-packages] [Bug 1868872] Re: Nautilus Cant open files in shared folders
could be the same issue than https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1447 -- 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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: Incomplete Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first
Thank you for the bug report, I can confirm the issue. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871320 Title: Switching alert sound will not take effect unless you switch to Default alert first Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I installed April 5th's nightly build, of Ubuntu Focal Fossa (development branch). Description: Ubuntu Focal Fossa (development branch) Release: 20.04 The issue is, Whichever the notification sound we choose after default, only that sound will take effect. Directly changing to another type of alert sound will not take effect. To reproduce the problem, 1. Open terminal, 2. Open sound settings, initially it will be "default". Change that to some other alert sound, say, "Drip". 3. Switch to terminal and press backspace, you will hear "Drip". 4. Switch to sound settings, this time select "Glass". 5. Switch to terminal and press backspace, here is the issue. You will not hear "Glass". You will still hear "Drip". 6. Switch to sound settings, now select default first and then select "Glass". 7. Switch to terminal and press backspace, now you will hear "Glass". So to summarize, if you want to change the alert sound, first you have to switch back to "Default" and then only whichever other alert sound you select, will take effect. Since the release time is near, I thought it would be helpful to fix this before release. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872071 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: New Bug description: This happened at start up after software updater requested a restart.I attached unattended-upgrades.log unattended-upgrades-dpkg.log dpkg.log to show what packages were installed before the restart. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 07:16:32 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-03-14 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f6b2b2919f6) ok source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITI
Fixed for me as the reporter of the bug - Thus it can be closed. Thanks! ** Changed in: gnome-calendar (Ubuntu) Status: New => Fix Released -- 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/1867302 Title: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed Segmentation fault (core dumped) Status in gnome-calendar package in Ubuntu: Fix Released Bug description: It core dumped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 Uname: Linux 5.5.8-xanmod6 x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 21:08:46 2020 InstallationDate: Installed on 2019-02-23 (383 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions -- Mailing list: https://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 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-C
Hi, Evolution Calendar is working fine on my end. Just a data point in case you don't have the latest updates installed. I haven't tested Gnome-Calendar yet - I'll do that next and report back. On Fri, Apr 10, 2020 at 11:25 AM Bicet <1867...@bugs.launchpad.net> wrote: > Same happening here with an exchange calendar and multi-day events > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867302 > > Title: > gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: > gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed > (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: > gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed > Segmentation fault (core dumped) > > Status in gnome-calendar package in Ubuntu: > New > > Bug description: > It core dumped. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-calendar 3.36.0-1 > Uname: Linux 5.5.8-xanmod6 x86_64 > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 12 21:08:46 2020 > InstallationDate: Installed on 2019-02-23 (383 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > SourcePackage: gnome-calendar > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions > -- "It is through science that we prove, but through intuition that we discover." - Henri Poincare -- 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/1867302 Title: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed Segmentation fault (core dumped) Status in gnome-calendar package in Ubuntu: Fix Released Bug description: It core dumped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 Uname: Linux 5.5.8-xanmod6 x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 21:08:46 2020 InstallationDate: Installed on 2019-02-23 (383 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872101] [NEW] Can't start VNC server from Sharing window in Gnome
Public bug reported: After upgrading to Focal, I'm (mostly) unable to start screen sharing from the Sharing window in Settings. Unfortunately it's "mostly", as I managed to do it a couple of times, unfortunately usually it's not possible. The toggle in the title bar of the window is inactive and doesn't flip. I can start all the other shares no problem (files, multimedia, ssh). Manually starting /usr/lib/vino/vino-server works fine. ProblemType: Bug 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: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Apr 10 17:21:30 2020 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-12 (911 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-26 (15 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872101 Title: Can't start VNC server from Sharing window in Gnome Status in gnome-control-center package in Ubuntu: New Bug description: After upgrading to Focal, I'm (mostly) unable to start screen sharing from the Sharing window in Settings. Unfortunately it's "mostly", as I managed to do it a couple of times, unfortunately usually it's not possible. The toggle in the title bar of the window is inactive and doesn't flip. I can start all the other shares no problem (files, multimedia, ssh). Manually starting /usr/lib/vino/vino-server works fine. ProblemType: Bug 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: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Apr 10 17:21:30 2020 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-12 (911 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-26 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITI
Same happening here with an exchange calendar and multi-day events -- 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/1867302 Title: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed Segmentation fault (core dumped) Status in gnome-calendar package in Ubuntu: New Bug description: It core dumped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 Uname: Linux 5.5.8-xanmod6 x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 21:08:46 2020 InstallationDate: Installed on 2019-02-23 (383 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz
I've been at it for just about one year now. I can only hope you guys now have the information it takes to solve this. I'm done swapping components, wracked a B450 motherboard and or Ryzen 2200g in the process. I was thinking about that ryzen 7 3700X anyways, so not that big of a disaster. But i hate the thought of maybe having to switch from 19.04 to 18.04 instead of 20.04. Good luck, Paul Webmaster https://starthemel.nl -- 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/1870637 Title: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: When i do get it to work, on reboot it'll be back to fullhd. this happens on nvidia 440, 435 and 390. On X.Org X server it does work. Graphics card: nVidia GT1030 Amp: Onkyo TX-NR646 On 19.10 there are no problems. A couple of weeks ago i tested a daily build and there were no troubles also, so this is new. My favourite setting: 3840x2160 200% 60hz. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/:10:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 01:02:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Micro-Star International Co., Ltd. MS-7B84 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.D0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-M2 (MS-7B84) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B84 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870805] Re: pas de son
toujour rien pa de pilote je pensse -- 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/1870805 Title: pas de son Status in pulseaudio package in Ubuntu: Incomplete Bug description: je n'ai pas de son qui sort de l'ordinateur, pas de sortie audio ni d'applications pour le son avec Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 17:25:31 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2018 dmi.bios.version: HQ-BI-14.1-Y116CR600-CC34I-014-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHQ-BI-14.1-Y116CR600-CC34I-014-D:bd01/08/2018:svnSCHNEIDER:pnSCL141CTP:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SCL141CTP dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: SCHNEIDER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871715] Re: gnome-control-center crashed with SIGSEGV in pa_context_set_error()
Thank you for your bug report, instead force stopping alsa/pulseaudio and playing with the settings while it restarts sometime leads to this error, force restarting the service isn't really a common usecase/something that should be normally done though so setting as low priority ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Summary changed: - gnome-control-center crashed with SIGSEGV in pa_context_set_error() + gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart -- 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/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart Status in gnome-control-center package in Ubuntu: Triaged Bug description: After alsa force-reload the Sounds in the Settings crashed. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 00:17:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-05 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: gnome-control-center sound SegvAnalysis: Segfault happened at: 0x7fd52df10daf:mov%esi,(%rdx) PC (0x7fd52df10daf) ok source "%esi" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 pa_context_set_sink_volume_by_index () from /lib/x86_64-linux-gnu/libpulse.so.0 ?? () gvc_mixer_stream_push_volume () ?? () Title: gnome-control-center crashed with SIGSEGV in pa_context_set_sink_volume_by_index() UpgradeStatus: Upgraded to focal on 2020-04-05 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872066] Re: ibus-x11 crashed with SIGSEGV
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: ibus (Ubuntu) Importance: Undecided => Low ** Changed in: ibus (Ubuntu) Status: New => Incomplete ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872066 Title: ibus-x11 crashed with SIGSEGV Status in ibus package in Ubuntu: Incomplete Bug description: Problema con el IBus ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:15:34 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=es_VE.UTF-8 LANGUAGE=es_VE:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f053a3079f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f053a3079f6) ok source "0x10(%rax)" (0x1036daa0e28aa0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () ?? () Title: ibus-x11 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871844] Re: [Snap] xdg-open not working
*** This bug is a duplicate of bug 1776873 *** https://bugs.launchpad.net/bugs/1776873 Thanks for referring! -- 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/1871844 Title: [Snap] xdg-open not working Status in chromium-browser package in Ubuntu: New Bug description: Several services register handlers for opening links in their external applications (examples: zoom.us, Microsoft Teams). Following a link to the respective content makes chromium display a box asking if xdg-open should be called. When I choose yes, nothing happens at all. Example content: https://t1p.de/WebinarZSL (That's a webinar for schools using MS Teams. The Teams app can be downloaded from their page.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 14:54:39 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (1579 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-19 (173 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821953] Re: warty-final-ubuntu.png is overwritten in revision 269
Thank you for your bug report. I'm not sure what the report is about, the fact that the name 'warty' is misleading there? It has been kept that way since we don't have a good way to migrate users upgrading, the content is changing every cycle but the name isn't ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1821953 Title: warty-final-ubuntu.png is overwritten in revision 269 Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: I've just noticed that warty-final-ubuntu.png is overwritten in https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu- wallpapers/ubuntu/revision/269 by what should be disco-final- ubuntu.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1821953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872088] Re: Latest wallpaper misleadingly named warty-final-ubuntu.png
Thank you for the report. We have been keepting the original name because we don't have a good way to migrate existing user configurations and upgraded systems would end up without a wallpaper if we changed the name. We could provide a new name and symlink to the old name though, that would probably be less confusing for new installations... ** Changed in: ubuntu-wallpapers (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1872088 Title: Latest wallpaper misleadingly named warty-final-ubuntu.png Status in ubuntu-wallpapers package in Ubuntu: Confirmed Bug description: This might be "normal" for new releases, but when poking around GNOME Tweaks I noticed that my wallpaper was called "warty-final- ubuntu.png". Whilst I appreciate the throwback, it's a bit misleading for people. If it has to be a set name between releases, couldn't it be renamed something like "ubuntu-default-wallpaper.png" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1872088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872088] [NEW] Latest wallpaper misleadingly named warty-final-ubuntu.png
Public bug reported: This might be "normal" for new releases, but when poking around GNOME Tweaks I noticed that my wallpaper was called "warty-final-ubuntu.png". Whilst I appreciate the throwback, it's a bit misleading for people. If it has to be a set name between releases, couldn't it be renamed something like "ubuntu-default-wallpaper.png" instead? ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Low Status: Confirmed ** Tags: focal ** Attachment added: "Screenshot from 2020-04-10 14-47-44.png" https://bugs.launchpad.net/bugs/1872088/+attachment/5351369/+files/Screenshot%20from%202020-04-10%2014-47-44.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1872088 Title: Latest wallpaper misleadingly named warty-final-ubuntu.png Status in ubuntu-wallpapers package in Ubuntu: Confirmed Bug description: This might be "normal" for new releases, but when poking around GNOME Tweaks I noticed that my wallpaper was called "warty-final- ubuntu.png". Whilst I appreciate the throwback, it's a bit misleading for people. If it has to be a set name between releases, couldn't it be renamed something like "ubuntu-default-wallpaper.png" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1872088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Seb Sorry for the inconvenience, I will be more careful next time, thank you! -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872076] [NEW] Multitouch gestures do not work on touchscreen in 20.04 X session
Public bug reported: Installed the latest 20.04 yesterday. Completely new install. All works fine except fingerprint reader (ok) and multitouch gestures on the touchscreen of my laptop. Mind that multi-touch gestures do work as intended on the touchpad. Expected: It should be easy to scroll a webpage using fingers on the touchscreen (in tablet mode for example). Observation: Using touch on the touchscreen, text is selected and the webpage does not scroll. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 14:22:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872076 Title: Multitouch gestures do not work on touchscreen in 20.04 X session Status in gnome-shell package in Ubuntu: New Bug description: Installed the latest 20.04 yesterday. Completely new install. All works fine except fingerprint reader (ok) and multitouch gestures on the touchscreen of my laptop. Mind that multi-touch gestures do work as intended on the touchpad. Expected: It should be easy to scroll a webpage using fingers on the touchscreen (in tablet mode for example). Observation: Using touch on the touchscreen, text is selected and the webpage does not scroll. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 14:22:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Thanks for the bionic patch, please read https://packaging.ubuntu.com/html/fixing-a-bug.html for next time though and provide a proper debdiff I'm fixing your changes and uploaded now, what was missing is - only the patch to the upstream code should be in debian/patches, the changelog needs to be directly updates - the patch should be listed in the serie - the bug reference should be listed as 'lp: #...' in the changelog (especially important for a SRU since the bug is what ensure the testing process can be followed) ** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Oh, also there was already a 1:11.1-1ubuntu7.5 in bionic-proposed so the update needed to be rebased on this one and become ubuntu7.6, I did that as well now -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
The focal fix landed now (but didn't autoclose since the bug was not mentioned in the changelog) ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized
Done. Thanks, Sebastien! ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2616 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616 Importance: Unknown Status: Unknown -- 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/1871868 Title: Keyboard shortcut restoring shortcut cut short when localized Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: Boxes wants to inhibit shortcuts You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:29:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869881] Re: html file detected as unknown application/octet-stream
The file opening issue is another one, it has also been fixed upstream now https://gitlab.gnome.org/GNOME/glib/-/commit/35953b5 which is in 2.64.2 -- 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/1869881 Title: html file detected as unknown application/octet-stream Status in nautilus package in Ubuntu: Fix Released Bug description: On ubuntu 20.04, when I mount an sftp or ftp share with nautilus (1:3.36.1-1ubuntu1), html files are not detected. The properties dialog shows "Unknown (application/octet-stream)". Php, css and js files are right detected. It is a known bug? No problem with pcmanfm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:59:58 2020 InstallationDate: Installed on 2019-12-18 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-03-20 (10 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
** Description changed: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: - Installed: 3.34.2-1ubuntu1 - Candidate: 3.34.2-1ubuntu1 + Installed: 3.34.2-1ubuntu1 + Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. - What happens instead : + What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. - Workaround ? : - Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc - So I have no idea. + Workaround : + Put + export MAIL=/var/mail/$USER + in ~/.bashrc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
thank you for your bug report, the error is a libexpact/glibc missing symbol, reassigning ** Package changed: ibus (Ubuntu) => glibc (Ubuntu) -- 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/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in glibc package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1872016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868319] Re: PCI/internal sound card not detected
@Hui "And from -42, it enabled the dmic_detect by default. And it introduced a regression from stable patches. It is fixed in the -46." As per my post #6 - it's not fixed in -46 kernel. So I deleted dmic_detect=0 from alsa-base.conf and created a symbolic link as per post #10. Rebooted. I did get sound, but it feels like it's very quiet comparing with the legacy driver (I can't hear anything below 40% volume setting and barely can hear sound at 50% setting). Also I found that microphone was enabled by default after reboot and I don't like that. So overall I'm not happy with this solution and will get back to legacy driver (dmic_detect=0 in alsa-base.config). Output of dmesg is attached and here is also an aplay output: user@G3:~$ aplay -l List of PLAYBACK Hardware Devices card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofsklhdacard [sof-skl_hda_card], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ** Attachment added: "dmesg_output_v46_with_symbLink.csv" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+attachment/5351257/+files/dmesg_output_v46_with_symbLink.csv -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized
Thank you for your bug report, indeed that looks like a gnome-shell, could you report it upstream on https://gitlab.gnome.org/GNOME/gnome- shell/-/issues ? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Keyboard shortcut restoring shortcut cut short when localized Status in gnome-shell package in Ubuntu: New Bug description: When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: Boxes wants to inhibit shortcuts You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:29:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871864] Re: Toggle "Fractional Scaling" does nothing on wayland
Thanks, indeed we should either hide the option under wayland or make change the other key. Unsure if the backend would deal correctly with the fractional scaling or if there is more work than just toggle the other key. It might be safe as this point to just not list the control there ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1871864 Title: Toggle "Fractional Scaling" does nothing on wayland Status in gnome-control-center package in Ubuntu: Confirmed Bug description: System: Ubuntu Focal Fossa (Development Branch) 20.04 Version of "gnome-control-center": 1:3.36.1-1ubuntu4 In the setting there is option called "Fractional Scaling" but this option only works for X11. What is the problem: Enabling "Fractional Scaling" adds only ['x11-randr-fractional-scaling'] but ['scale-monitor-framebuffer'] What it should be: Enabling "Fractional Scaling" in the setting adds parameter for both X11 and wayland: ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer'] ProblemType: Bug 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 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 23:43:57 2020 InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] [NEW] Local mail is never checked
Public bug reported: Description:Ubuntu 19.10 Release:19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround ? : Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc So I have no idea. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround ? : Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc So I have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870794] Re: missing some emojis
Historically, Google tends to release its annual Unicode/Emoji update for this font around the time it releases the next major version of Android. Android 11 is expected in the 3rd quarter of 2020. We probably will push the update to Ubuntu 20.04 LTS then. ** Summary changed: - missing some emojis + Update for Unicode 13 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1870794 Title: Update for Unicode 13 Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Bug description: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Still reproducible with Ubuntu 20.04 beta with gnome-control-center 1:3.36.1-1ubuntu4 and gnome-3.36.1, where the option to enable fractional scaling is exposed in the GUI -- 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/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
Yes, only 20.04. ** Description changed: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ - Pango is used by many apps (particularly GTK apps) to display emoji. - - By doing this update for Ubuntu 18.04 LTS now, it will be easier to get + By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts-noto- color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. - References - =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 - https://emojipedia.org/emoji-13.0/ - https://github.com/googlefonts/noto-emoji/releases -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: Fix Committed Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ By doing this update for Ubuntu 20.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871882] Re: gnome-session-bin package cannot function without gnome-session
Thank you for your bug report, 'gnome-session' isn't installed by default on Ubuntu and there is no problem so that's not the issue. Do you use autologin? The user maybe has a local config pointing to a gnome session? ** Changed in: gnome-session (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: gnome-session-bin package cannot function without gnome-session Status in gnome-session package in Ubuntu: Incomplete Bug description: This concerns gnome-session-bin 3.36.0-2ubuntu1 in Ubuntu focal. When I log into a Xubuntu desktop via xrdp, an error occurs, and the session terminates before the desktop is even drawn on the screen. I looked in syslog, and saw this: Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:12:23 test-ubuntu64 gnome-session[1900]: gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 systemd[1760]: gnome-session-manager@gnome.service: Main process exited, code=exited, status=1/FAILURE I edited /usr/lib/systemd/user/gnome-session-manager@.service to add the --debug option to the gnome-session-binary invocation, and tried again. Now I saw this: Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818#012 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]:
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
Same annoying bug here, on ubuntu 19.10 64 bit. Gnome 3.34.2. Very frequently on libreoffice, but sometimes on other programs too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in codeblocks package in Ubuntu: Confirmed Status in codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in codeblocks source package in Eoan: Confirmed Status in codelite source package in Eoan: Confirmed Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in codeblocks source package in Focal: Confirmed Status in codelite source package in Focal: Confirmed Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872041] Re: cupsd assert failure: free(): invalid pointer while printing
*** This bug is a duplicate of bug 1846334 *** https://bugs.launchpad.net/bugs/1846334 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1846334, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872041/+attachment/5351187/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351190/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351203/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351205/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351206/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351207/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872041/+attachment/5351208/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1846334 cupsd assert failure: free(): invalid pointer ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1872041 Title: cupsd assert failure: free(): invalid pointer while printing Status in cups package in Ubuntu: New Bug description: Starting a job to a printer through Wifi network, cupsd failed, and network printers discovery (and availability) stopped. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: skip CupsErrorLog: E [10/Apr/2020:00:00:21 +0200] Missing value on line 1204 of /var/cache/cups/job.cache. W [10/Apr/2020:09:16:17 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'C48x-Series-Gray..\' already exists W [10/Apr/2020:09:16:17 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'C48x-Series-CMYK..\' already exists E [10/Apr/2020:11:31:51 +0200] [Job 196] File \'\' not found E [10/Apr/2020:11:34:57 +0200] [Job 197] No destination host name supplied by cups-browsed for printer \"Samsung_C48x_Series_SEC8425199A158D_\", is cups-browsed running? Date: Fri Apr 10 11:32:38 2020 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-21 (413 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for C48x-Series: usb://Samsung/C48x%20Series?serial=08GMB8GM5E0076E=1 device for Samsung_C48x_Series_SEC8425199A158D_: implicitclass://Samsung_C48x_Series_SEC8425199A158D_/ device for toshiba3505_fernbach1_MacBook_Pro_6_: ///dev/null device for TOSHIBA_e_STUDIO2000AC_11689878: dnssd://TOSHIBA%20e-STUDIO2000AC-11689878._ipp._tcp.local/?uuid=1a657c0f-8d51-4514-8e3b-c1c5fffbc672 device for TOSHIBA_e_STUDIO257_11225681: ipp://MFP11225681.local:631/Print MachineType: HP HP ProBook 430 G5 Papersize: a4 PpdFiles: Samsung_C48x_Series_SEC8425199A158D_: Samsung C48x Series, driverless, cups-filters 1.27.3 C48x-Series: Samsung C48x Series PS TOSHIBA_e_STUDIO257_11225681: TOSHIBA e-STUDIO257, driverless, cups-filters 1.20.2 TOSHIBA_e_STUDIO2000AC_11689878: e-STUDIO2000AC ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffbc76c8285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7ffbc76c64ae "free(): invalid pointer") at malloc.c:5347 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /usr/lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: Upgraded to focal on 2020-03-20 (20 days ago)
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Ok, I'm a machine where I get the issue now editing /usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py l853 in def on_isv_source_toggled to add (before the try) import time time.sleep(0.1) seems enough to workaround the bug ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Invalid Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872044] [NEW] package lirc 0.10.1-6.1 failed to install/upgrade: »installiertes lirc-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Public bug reported:
new installation focal desktop beta and updates +zim and synaptic
grep -i ttyacm0 /var/log/syslog
Apr 9 17:36:47 troubadix kernel: [2.535769] cdc_acm 3-6:1.0: ttyACM0: USB
ACM device
Apr 9 17:43:28 troubadix kernel: [2.217191] cdc_acm 3-6:1.0: ttyACM0: USB
ACM device
cat /usr/lib/udev/rules.d/atric.rules
SUBSYSTEM=="tty", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f844",
SYMLINK+="ttyatric", ENV{ID_MM_DEVICE_IGNORE}="1"
reboot
ls -l /dev/ttyatric
lrwxrwxrwx 1 root root 7 Apr 9 18:26 /dev/ttyatric -> ttyACM0
no further actions
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lirc 0.10.1-6.1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
Date: Thu Apr 9 18:34:35 2020
ErrorMessage: »installiertes lirc-Skript des Paketes
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2020-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.1ubuntu1
SourcePackage: lirc
Title: package lirc 0.10.1-6.1 failed to install/upgrade: »installiertes
lirc-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1
zurück
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1872044
Title:
package lirc 0.10.1-6.1 failed to install/upgrade: »installiertes
lirc-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 1 zurück
Status in lirc package in Ubuntu:
New
Bug description:
new installation focal desktop beta and updates +zim and synaptic
grep -i ttyacm0 /var/log/syslog
Apr 9 17:36:47 troubadix kernel: [2.535769] cdc_acm 3-6:1.0: ttyACM0:
USB ACM device
Apr 9 17:43:28 troubadix kernel: [2.217191] cdc_acm 3-6:1.0: ttyACM0:
USB ACM device
cat /usr/lib/udev/rules.d/atric.rules
SUBSYSTEM=="tty", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f844",
SYMLINK+="ttyatric", ENV{ID_MM_DEVICE_IGNORE}="1"
reboot
ls -l /dev/ttyatric
lrwxrwxrwx 1 root root 7 Apr 9 18:26 /dev/ttyatric -> ttyACM0
no further actions
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lirc 0.10.1-6.1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
Date: Thu Apr 9 18:34:35 2020
ErrorMessage: »installiertes lirc-Skript des Paketes
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2020-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.1ubuntu1
SourcePackage: lirc
Title: package lirc 0.10.1-6.1 failed to install/upgrade: »installiertes
lirc-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1
zurück
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1872044/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Same problem on Lenovo IdeaPad 310-15IKB, ubuntu 19.10 with kernel 5.3.0-46. Muting the right channel solved the problem tempuraly. -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869750] Re: [nvidia] Screens turn off when setting display scaling to 200%
I can confirm that this issue has been resolved with today's (2020-04-10) update in Focal Fossa. -- 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/1869750 Title: [nvidia] Screens turn off when setting display scaling to 200% Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: Issue: When setting display scaling to 200% in GNOME settings with proprietary nvidia drivers installed displays go to sleep until settings automatically revert to previous settings. Steps to reproduce: - Install proprietary nvidia drivers - Open GNOME settings - Navigate to Display settings - Set display scaling to 200% NOTE: This issue has been solved in upstream mutter git master branch. Confirmed on both Arch and Fedora packages that have been created from mutter master branch. GPU: GeForce GTX 1080 Ti Driver: 440.64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 11:01:56 2020 InstallationDate: Installed on 2020-03-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1869750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868319] Re: PCI/internal sound card not detected
@David, No need to change alsa-base.conf after every update. And from -42, it enabled the dmic_detect by default. And it introduced a regression from stable patches. It is fixed in the -46. Even in 18.04, you could still try with the symbollink. Please edit alsa-base.conf to remove the dmic_detect=0, then generate link as #10, please test it and upload the dmesg. After that, you could delete that symbollink and restore the dmic_detect=0 in the alsa-base.conf. thx -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871890] Re: The link given by ubuntu-bug is not always well marked
*** This bug is a duplicate of bug 1871185 *** https://bugs.launchpad.net/bugs/1871185 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1871185, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1871185 urls in ubuntu-bugs dialog not really clickable -- 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/1871890 Title: The link given by ubuntu-bug is not always well marked Status in gnome-shell package in Ubuntu: New Bug description: when running ubuntu-bug on some snap applications it only marks a part of the link to click and it doesn't take to the right page to open a bug. It seems that this only happens with snaps that add launchpad as contact. Tested with libreoffice.snap and took me to https://bugs.launchpad.ne/ubuntu/ instead of https://bugs.launchpad.net/ubuntu/+source/libreoffice/-bugs?-field.tag=snap ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 19:18:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-07 (2 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=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871943] Re: Gnome Fonts viewer freezes and then crashes whenever I launch the app and scroll downwards
Thank you for your bug report, could you look at the cpu and memory usage while it's showing the issue? ** Changed in: gnome-font-viewer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1871943 Title: Gnome Fonts viewer freezes and then crashes whenever I launch the app and scroll downwards Status in gnome-font-viewer package in Ubuntu: Incomplete Bug description: Whenever I open gnome-fonts-viewer in Focal, or Eoan, and then scroll downwards, even if I did not install any fonts and am only using the fonts supplied with the system, Gnome-fonts will freeze, and in some cases render the entire system unusable because of its freezes. To reproduce: Simply Launch Gnome-Fonts-Viewer and scroll downwards. Focal-Fossa Beta. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-font-viewer 3.34.0-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Thu Apr 9 17:35:13 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 DistroRelease: Ubuntu 20.04 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-font-viewer 3.34.0-2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-font-viewer 3.34.0-2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Tags: focal Uname: Linux 5.4.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1871943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868319] Re: PCI/internal sound card not detected
@Hui, First of all thanks for the response - the trick with alsa-base.conf worked fine. Sound is restored. I'm guessing I'll have to edit alsa-base.conf after every update? If so, is there a more permanent solution? Also I'm not on 19.10, I'm on 18.04. And what happened with sof-firmware between kernels -40 and -42 (that's when sound disappeared)? -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872034] [NEW] [Focal] No HDMI output through thunderbolt docking station
Public bug reported: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in xorg package in Ubuntu: New Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
[Desktop-packages] [Bug 1870479] Re: .desktop files were open by gedit
Upstream isn't interested in keeping that feature so marking wontfix. @Rex, what's the requirement? ** Changed in: nautilus (Ubuntu) Status: New => Won't Fix -- 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/1870479 Title: .desktop files were open by gedit Status in OEM Priority Project: Invalid Status in nautilus package in Ubuntu: Won't Fix Bug description: On 20.04,the .desktop file could not show correct icons and open by correct applications. It only show a 'setting' icon, and when you double click it, it will use gedit to open it. nautilus 1:3.36.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1870479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871972] Re: Update pango for Unicode 13.0
Jeremy, you mean 20.04 when you wrote 18.04 there right? I also saw an update in the queue from you with what looks like the patch described there so I'm going to mark the bug as fix commit and assign to you to reflect the status ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: pango1.0 (Ubuntu) Status: New => Fix Committed ** Changed in: pango1.0 (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871972 Title: Update pango for Unicode 13.0 Status in pango1.0 package in Ubuntu: Fix Committed Bug description: Unicode 13 was released a month ago. The Pango library needs to be updated for the new emoji sequences for emoji that are implemented by multiple emoji in sequence to appear as a single character instead of as separate parts. For instance, https://emojipedia.org/black-cat/ Pango is used by many apps (particularly GTK apps) to display emoji. By doing this update for Ubuntu 18.04 LTS now, it will be easier to get full Unicode 13 support once Ubuntu's color emoji font (fonts- noto-color-emoji) is released with Unicode 13 support in a few months. I don't believe a freeze exception is necessary for this improvement now. References =- https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539 https://emojipedia.org/emoji-13.0/ https://github.com/googlefonts/noto-emoji/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872031] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1869510 *** https://bugs.launchpad.net/bugs/1869510 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1869510, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872031/+attachment/5351119/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351122/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351133/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351135/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351136/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351137/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872031/+attachment/5351138/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1869510 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1872031 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: New Bug description: It happened when you opened an image in the image viewer from nautilus ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 10:31:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=UUID=92c81122-8f7e-4b05-8edd-00c0ff7fce6c ro Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/libglamoregl.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo www-data dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
Thank you for the fix! After having my mutter updated, I can finally watch the fullscreen videos while having the fractional scaling enabled However, there is one minor issue. Whenever I switch to the fullscreen mode, the scaling factor is changed from 150% to 200%, so all the widgets are unnecessarily large. This isn't a deal breaker for me, because I use the fullscreen mode only for watching the videos; I just wanted to confirm that it's the intended behavior -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Fix Released Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
It seems to me that fix https://gitlab.freedesktop.org/xorg/xserver/-/commit/cfc5e5040c934 is the correct one. Is it possible to reproduce the crash with that one patch applied even without all the other proposed fixes? -- 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/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. This actually seems to happen most frequently in VirtualBox. WORKAROUND: Select "Ubuntu on Wayland" from the login screen before logging in. --- It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage
[Desktop-packages] [Bug 1871984] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow()
** Information type changed from Private to Public -- 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/1871984 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() Status in gnome-shell package in Ubuntu: New Bug description: I can't really pinpoint the cause because I've had lots of gnome-shell crashes during normal use and I can't very well tell them apart. One more-common factor is clicking the top-bar, either when logged in or when the screen is locked. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 19:22:24 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fa819f2 : mov(%rax),%rdi PC (0x7fa819f2) ok source "(%rax)" (0x223d657079742000) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_lookup_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
