[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
This is to confirm that kubuntu-21.04-beta-desktop-amd64.iso fails as an installation media on my PC. I have nvidia graphics, amd m/board and am using 'safe graphics' when attempting to boot up the installation media from a thumb drive. The usual "Installation failed" message is displayed. If more info would help please give me any further instructions. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922317] [NEW] package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: I cannot seem to get my bluetooth to work. When I go to bluetooth settings the "switch" is grayed out and I cannot turn it off or on. I'm trying to install bluez and I am getting an error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 1 20:17:40 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-15 (443 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b509 Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 009: ID :3100 MacAlly Macally ECOMouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=93ef3a52-1422-4313-abac-a02f96bcecc3 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.vendor: HP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd03/06/2018:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn:rvr:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N5Z06UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922317 Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: I cannot seem to get my bluetooth to work. When I go to bluetooth settings the "switch" is grayed out and I cannot turn it off or on. I'm trying to install bluez and I am getting an error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 1 20:17:40 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-15 (443 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b509 Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 009: ID :3100 MacAlly Macally ECOMouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=93ef3a52-1422-4313-abac-a02f96bcecc3 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-p
[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Changed in: hplip (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Confirmed Status in hplip package in Debian: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install hplip-gui 3. Launch GNOME session. 4. Get error message window with header "HPLIP Status Service" and text "No system tray detected on this system. Unable to start, exiting." Expected results: hp-systray is compatible with modern GNOME Actual results: hp-systray is not compatible with modern GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 (dbus://) went away, retrying! CurrentDesktop: GNOME Date: Sat Sep 2 14:10:19 2017 InstallationDate: Installed on 2017-08-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. UX32A PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A 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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi
I'm running Ubuntu 20.10. But I think I can answer my own question. It just happened again, and this time all I needed to run was run `apt update`. I didn't even install anything! A quick google search found this page: https://www.linuxuprising.com/2020/07/how-to-restart-gnome-shell-from- command.html. I pressed Alt-F2 and then r, and that stopped the logging without a reboot! I'd still like to know why this suddenly keeps happening. 21.04 is due out in a few weeks and I'm hoping that will fix it. -- 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/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: Fix Released Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Changed in: mate-desktop Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: New Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up
Yes, the fix is in the focal queue for some days now, once SRU team will approve it will be available in proposed repositories for user verification. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1905370 Title: Qt-based tray icons not displayed on start-up Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Confirmed Status in gnome-shell-extension-appindicator source package in Groovy: Won't Fix Status in gnome-shell-extension-appindicator source package in Hirsute: Fix Released Bug description: [ Impact ] My system version is 20.10. I upgraded from 20.04. I found such a problem, the tray icon cannot be displayed when the system is turned on or restarted, but if I kill the process and restart it, it will be fine. I searched on Google and didn't see a similar problem.This is my hardware configuration: CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56 GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 [GeForce 1060] https://i.stack.imgur.com/ybiVj.png [ Test case ] - Install a Qt app with a tray icon that should show on startup - At login the icon should be visible. An example is hp-systray, from the package hplip-gui: - Add it to the autostart (if you don't have HP printers just add the command `hp-systray -x`). Expect the icon to show [ Regression Potential ] No status icon service is ever initialized by the shell and so no app indicator is visible. ProblemType: BugDistroRelease: Ubuntu 20.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 16:34:31 2020 InstallationDate: Installed on 2020-10-24 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-generic linux-baseSourcePackage: meta-gnome3 UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922298] [NEW] Activities panel on wrong display
Public bug reported: The activities panel is showing up on the wrong display. Selecting the "primary display" as 3 in the display settings puts the top bar on display 3 , but the activities bar on screen 2. Screenshot attached Similarly, selecting primary display = 2 then activities bar ends up on 1 primary display = 1 then activities bar ends up on 3 I'm hoping this is just an off by one error somewhere. I think gnome-shell is the correct package. Feel free to move to the correct package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 17:16:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (293 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-04-01 17-05-08.png" https://bugs.launchpad.net/bugs/1922298/+attachment/5483269/+files/Screenshot%20from%202021-04-01%2017-05-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922298 Title: Activities panel on wrong display Status in gnome-shell package in Ubuntu: New Bug description: The activities panel is showing up on the wrong display. Selecting the "primary display" as 3 in the display settings puts the top bar on display 3 , but the activities bar on screen 2. Screenshot attached Similarly, selecting primary display = 2 then activities bar ends up on 1 primary display = 1 then activities bar ends up on 3 I'm hoping this is just an off by one error somewhere. I think gnome-shell is the correct package. Feel free to move to the correct package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 17:16:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (293 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up
Any update on its status on Focal? Will it be back ported? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1905370 Title: Qt-based tray icons not displayed on start-up Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Confirmed Status in gnome-shell-extension-appindicator source package in Groovy: Won't Fix Status in gnome-shell-extension-appindicator source package in Hirsute: Fix Released Bug description: [ Impact ] My system version is 20.10. I upgraded from 20.04. I found such a problem, the tray icon cannot be displayed when the system is turned on or restarted, but if I kill the process and restart it, it will be fine. I searched on Google and didn't see a similar problem.This is my hardware configuration: CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56 GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 [GeForce 1060] https://i.stack.imgur.com/ybiVj.png [ Test case ] - Install a Qt app with a tray icon that should show on startup - At login the icon should be visible. An example is hp-systray, from the package hplip-gui: - Add it to the autostart (if you don't have HP printers just add the command `hp-systray -x`). Expect the icon to show [ Regression Potential ] No status icon service is ever initialized by the shell and so no app indicator is visible. ProblemType: BugDistroRelease: Ubuntu 20.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 16:34:31 2020 InstallationDate: Installed on 2020-10-24 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-generic linux-baseSourcePackage: meta-gnome3 UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Also affects: hplip (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793675 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Confirmed Status in hplip package in Debian: Unknown Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install hplip-gui 3. Launch GNOME session. 4. Get error message window with header "HPLIP Status Service" and text "No system tray detected on this system. Unable to start, exiting." Expected results: hp-systray is compatible with modern GNOME Actual results: hp-systray is not compatible with modern GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 (dbus://) went away, retrying! CurrentDesktop: GNOME Date: Sat Sep 2 14:10:19 2017 InstallationDate: Installed on 2017-08-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. UX32A PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A 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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922291] Re: day of the week is missing
** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483255/+files/Dependencies.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483259/+files/ShellJournal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483258/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483257/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "GsettingsChanges.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483256/+files/GsettingsChanges.txt ** Summary changed: - day of the week is missing + Day of the week is missing -- 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/1922291 Title: Day of the week is missing Status in gnome-shell package in Ubuntu: New Bug description: For several days now, the day of the week is not displayed on the time sub-menu like the screenshot in the attachment, it seems to be a bug from the last update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:51:53 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922291] [NEW] Day of the week is missing
Public bug reported: For several days now, the day of the week is not displayed on the time sub-menu like the screenshot in the attachment, it seems to be a bug from the last update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:51:53 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Capture d’écran de 2021-03-30 20-57-24.png" https://bugs.launchpad.net/bugs/1922291/+attachment/5483254/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-03-30%2020-57-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922291 Title: Day of the week is missing Status in gnome-shell package in Ubuntu: New Bug description: For several days now, the day of the week is not displayed on the time sub-menu like the screenshot in the attachment, it seems to be a bug from the last update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:51:53 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922290] Re: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
** 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/1922290 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() Status in nautilus package in Ubuntu: New Bug description: Immediately after booting and log-in ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:25:47 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2021-01-23 (68 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200720) ProcCmdline: nautilus --version ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f972063b414:mov0x20(%rdi),%rax PC (0x7f972063b414) ok source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 update_dbus_opened_locations () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() UpgradeStatus: Upgraded to hirsute on 2021-01-23 (68 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1922290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922290] Re: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
executing the command nautilus --version in a terminal window also crashes. ** Information type changed from Private to Public -- 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/1922290 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() Status in nautilus package in Ubuntu: New Bug description: Immediately after booting and log-in ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:25:47 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2021-01-23 (68 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200720) ProcCmdline: nautilus --version ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f972063b414:mov0x20(%rdi),%rax PC (0x7f972063b414) ok source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 update_dbus_opened_locations () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() UpgradeStatus: Upgraded to hirsute on 2021-01-23 (68 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1922290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921963] Re: SRU 3.36.9
Amr, Thanks for pointing it out! I've uploaded a yaru package as well! -- 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/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: New Status in gnome-shell source package in Focal: In Progress Status in yaru-theme source package in Focal: New Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922267] Re: this program cannot be set as the default program (rhythmbox)
1. Right click an audio file and select "Properties" menu item. 2. Select "Open With" Tab in Properties Window. 3. Select "Rhythmbox" from the below application list and click "Set as default". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1922267 Title: this program cannot be set as the default program (rhythmbox) Status in rhythmbox package in Ubuntu: New Bug description: I can't set 'Rhythmbox' as a default for listening to music. When I try to set 'Rhythmbox' as the default program (for music playback) this setting is not accepted. You cannot set this up, as the 'Movies' program is automatically set as the default program immediately. I have tried many ways, but no changes to this topic. I will be grateful for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 18:35:20 2021 InstallationDate: Installed on 2021-01-31 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1922267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 676042] Update bug:, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmHRQACgkQH1G0ZBEH M/E/AAf+MZaZWPdkBWLx6pZV/wxe6uj8ONurmdDQokXiXWyCflydf9gJxCUX1FKb M51L4nlApghWR9uYf5lX0JYb8oaSsspIu8JMz5IS/7l29MeGS6b0wt0shPmQM6fY c2gcLdq9cbuLGw98ZonZf8Q2hCfYjtBI4SL2VxWSXZ3mcEWY4YP140iv053DmLnp BFtdQpgFX+1V5a7TC5B8UwzQ+i6eW7B7OIUM2J4KJrVcqdp9AOsYkWXKfiNVVCjj 0cB3PE4jsk/S+Q4DvJJR4A8FE7uJnfZGv0r01ugC0JMcxbRqOsOnv3VfNHKpPvCT PwsSlp9CfJKLto64SymqJU3SWIUTWw== =CdqP -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/676042 Title: duplicity falsely reports succeeded backup, empty manifest file Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: New Bug description: duplicity version duplicity 0.6.09 Python 2.5.2 Distributor ID: Debian Description: Debian GNU/Linux 5.0.6 (lenny) Release: 5.0.6 Codename: lenny ==backup log snip== ionice -c 3 nice -n 9 duplicity incremental --full-if-older-than 2W --asynchronous-upload --no-encryption --asynchronous-upload --no-encryption --exclude '/tmp/**' --exclude '/proc/**' --exclude '/dev/**' --exclude '/sys/**' --exclude '/root/.cache/**' --exclude '/var/cache/duplicity/**' --exclude '/var/marsnet/duplicity/**' --exclude '/var/alternc/mnt/**' --exclude '/var/lib/mysql/**' --exclude '/var/alternc/db/**' --exclude '/var/log/mysql/**' / ssh://backup@mybckhost//opt/marsnet/backups/ Local and Remote metadata are synchronized, no sync needed. Last full backup date: Thu Oct 28 01:13:25 2010 Last full backup is too old, forcing full backup --[ Backup Statistics ]-- StartTime 1289607215.28 (Sat Nov 13 01:13:35 2010) EndTime 1289636885.88 (Sat Nov 13 09:28:05 2010) ElapsedTime 29670.59 (8 hours 14 minutes 30.59 seconds) SourceFiles 1730868 SourceFileSize 106161258939 (98.9 GB) NewFiles 1730868 NewFileSize 106161244989 (98.9 GB) DeletedFiles 0 ChangedFiles 0 ChangedFileSize 0 (0 bytes) ChangedDeltaSize 0 (0 bytes) DeltaEntries 1730868 RawDeltaSize 105419449446 (98.2 GB) TotalDestinationSizeChange 65491887291 (61.0 GB) Errors 0 - ++ hostname --fqdn + ionice -c 3 nice -n 9 duplicity remove-all-but-n-full 1 --force --no-encryption ssh://backup@mybckhost//opt/marsnet/backups/ Local and Remote metadata are synchronized, no sync needed. Last full backup date: Sat Nov 13 01:13:30 2010 Deleting backup set at time: Thu Oct 28 01:13:25 2010 Deleting this file from backend: duplicity-full-signatures.20101027T231325Z.sigtar.gz ==end snip== This is the log from the backup that failed. Ihave conditional execution so backups aren't removed if duplicity fails. In this case there was no error, but I found an empty manifest file in the destination directory. Sorry, i don't use extra verbose output in my backup scripts. All the restore scripts fail silently: they see the archive as empty, this could be the reason why duplicity reported success on exit? (very annoying, i just had to restore a file, i'm trying to recover at least a part of it using simple gunzip and tar..) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/676042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists
** Changed in: duplicity Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: Fix Released Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Triaged Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576051] Update bug #1576051, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFfMACgkQH1G0ZBEH M/FnDQgAhImWqh76T9WUH4NzzfarEEZsdLKXg6lspkK14v3nEV0J1kd4PnsgxmL0 k0c2q3vcUOuB0QTyydWb5Jzf4C6JzmIRZEkJaHNojU7oFgyzu+AFq3r56/UdVFh/ yw84Ly3vaxN25BlR+T5kHENHtzmp9sMS8KdcECwh7EfxtxluItF/bkXk8kYukhlO WhnEkiyw/Fb6+5sQ0tl73t+V9zLOn2WrTLpSxaAsiZMel33aOBYgoPOic0v+Wpsv B407MFxAen5Z4EKHWwpQ2HLHik6OXiir6ZVX400+6inSJflqBCobJM0Lm/NH8OKu NacHNc7wXXHVGI9vKMliwg36OTJvCg== =/NIB -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576051 Title: Duplicity cannot handle sparse files efficiently Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: Confirmed Bug description: When running backup with duplicity, it cannot handle sparse files efficiently. I have a virtual machine image on my home dir, 26G -rw-r--r-- 1 libvirt-qemu kvm 33G huhti 28 08:59 dev02.img And duplicity is backing it up 33G, when it should only back up 26G. Steps to reproduce 1. Use qemu-image to create a sparse file 2. Run duplicity 3. Observe duplicity back it up whole instead of very small size To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1576051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652410] Update bug #1652410, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
status confirmed
importance medium
done
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFc0ACgkQH1G0ZBEH
M/GUCwgAoXIyBDb6kUITjvrIJVhKO8CXv/94R1PxitsoYebTWK1D8TUkOWFmy+mS
2NFM/IsMk5XbIrMgPvaJCyp/CuGzehzIV6hBaQVyhOg9VcuAKSNJ4bSNeABmXqrM
dh7GoiuY7ECn6gybCUznONyDvMJXbhR6/hqZgfOqDZGeNHNMtFpa+72qgcdpnuQh
+ymv+CO9ZyVMqv2Zuh53U53AuBpB9O3NWKhTbYTB3uS8C546jvAzfUEApuSFVYS8
yerauyOPF+BoX6Kcvv2zT52exvrVjTFD6Nmrr3W1SItGP8ayg0lVgdgez3UDaZ/0
W0Euv6sOx6i5LUFmPkgVoJ9pfw6VbQ==
=HUg5
-END PGP SIGNATURE-
** Changed in: duplicity
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
directory contains two volumes with different file names and same
volume number in the same backup set
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
[System]
Ubuntu 16.04
deja-dup 34.2-0ubuntu1.1
duplicity 0.7.06-2ubuntu2
[Symptoms]
When the backup location unfortunately contains two backup volumes
with different file names and same volume number in the same backup
set, for instance:
duplicity-full.20161129T015237Z.vol1.difftar
duplicity-full.20161129T015237Z.vol1.difftar.gz
this confuses duplicity collection-status, which ends up returning an
undescriptive Python assertion error, as seen in this Déjà-Dup log
file:
DUPLICITY: INFO 1
DUPLICITY: . Args: /usr/bin/duplicity collection-status [...]
[...]
DUPLICITY: DEBUG 1
DUPLICITY: . 12 files exist on backend
DUPLICITY: DEBUG 1
DUPLICITY: . Extracting backup chains from list of files:
[u'duplicity-full.20161129T015237Z.vol1.difftar',
u'duplicity-full.20161129T015237Z.manifest',
u'duplicity-full.20161129T015237Z.vol1.difftar.gz',
u'duplicity-full-signatures.20161129T015237Z.sigtar.gz',
u'duplicity-full-signatures.20161129T015237Z.sigtar',
[...]
DUPLICITY: DEBUG 1
DUPLICITY: . File duplicity-full.20161129T015237Z.vol1.difftar is not
part of a known set; creating new set
DUPLICITY: DEBUG 1
DUPLICITY: . File duplicity-full.20161129T015237Z.manifest is part of
known set
DUPLICITY: ERROR 30 AssertionError
[...]
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.
py", line 105, in add_filename(self.volume_name_dict, filename)
DUPLICITY: . AssertionError:
({1: 'duplicity-full.20161129T015237Z.vol1.difftar'},
'duplicity-full.20161129T015237Z.vol1.difftar.gz')
What happens is that duplicity collection-status takes the
uncompressed duplicity-full.20161129T015237Z.vol1.difftar for the
start of a backup set, then tries to add the compressed duplicity-
full.20161129T015237Z.vol1.difftar.gz to this set, and fails because
the volume number of this file has already been added to the set.
Otherwise there would be two backup volumes with the same volume
number in the backup set.
Note that a similar issue may also happen for file signatures instead
of backup volumes, e.g.:
duplicity-full-signatures.20161129T015237Z.sigtar
duplicity-full-signatures.20161129T015237Z.sigtar.gz
but backup volumes appear to be tripped on first, perhaps because of
alphabetic order.
Note also that under normal operation, the backup location isn't
supposed to contain a mixed of compressed and uncompressed files (or
encrypted and unencrypted files), but this situation was still
reported by the bug reporter in the original bug report.
[Test case]
See comment 19, written for Déjà-Dup, but easily adaptable to pure
duplicity I think.
[Ideas for fixing]
Duplicity already has checks to avoid considering files whose names
don't look like they could be part of a backup set (see comment 19,
point 4). Perhaps this filename filter could be improved on so that
duplicity doesn't burp so hard when a backup volume is present in both
compressed and uncompressed forms? Perhaps it could have duplicity
prefer a particular filename when there are two volumes with the same
number in the same backup set? But then which one and on what grounds?
Please also see comment 23.
[Easier fix]
Worst case, if this situation can't be handled automatically and the
situation requires a human to examine the contents of the backup
repository to take adequate action, then it would be helpful that
duplicity return a more descriptive message than the current terse
assertion error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1652410/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: Unknown Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
In focal, the 'native systemd unit' log is not present so the only message to check for is the 'legacy directory' message. root@lp1915887-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.5 amd64system and service manager root@lp1915887-f:~# journalctl -b --grep legacy --no-pager -- Logs begin at Thu 2021-04-01 17:09:33 UTC, end at Thu 2021-04-01 17:11:46 UTC. -- Apr 01 17:09:45 lp1915887-f systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Apr 01 17:09:46 lp1915887-f systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. root@lp1915887-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.6 amd64system and service manager root@lp1915887-f:~# journalctl -b --grep legacy --no-pager -- Logs begin at Thu 2021-04-01 17:09:33 UTC, end at Thu 2021-04-01 17:16:09 UTC. -- -- No entries -- ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 4
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
In Groovy for 'legacy directory' logs, with /lib/systemd/system/dbus.socket manually edited to use /var/run... path to reproduce error, with current version logs seen e.g.: Apr 01 17:02:34 lp1915887-g systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. with -proposed version, those logs are not present. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automati
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
ubuntu@lp1915887-g:~$ dpkg -l systemd|grep systemd ii systemd246.6-1ubuntu1.2 amd64system and service manager ubuntu@lp1915887-g:~$ /lib/systemd/system-generators/systemd-sysv-generator SysV service '/etc/init.d/grub-common' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. ubuntu@lp1915887-g:~$ dpkg -l systemd|grep systemd ii systemd246.6-1ubuntu1.3 amd64system and service manager ubuntu@lp1915887-g:~$ /lib/systemd/system-generators/systemd-sysv-generator ubuntu@lp1915887-g:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below; specifically messages containing text with "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel
[Desktop-packages] [Bug 1922241] Re: [Wayland] Dash to dock don't show all applications
Probably related to bug 1872796 too -- 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/1922241 Title: [Wayland] Dash to dock don't show all applications Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This extension has been updated these days and the "All" button (next to "Frequent" button) has crash and no longer shows all applications. Disabling Ubuntu-Dock via Extensions Panel this function works perfectly again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 09:56:04 2021 InstallationDate: Installed on 2020-11-12 (139 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1922241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922267] [NEW] this program cannot be set as the default program (rhythmbox)
Public bug reported: I can't set 'Rhythmbox' as a default for listening to music. When I try to set 'Rhythmbox' as the default program (for music playback) this setting is not accepted. You cannot set this up, as the 'Movies' program is automatically set as the default program immediately. I have tried many ways, but no changes to this topic. I will be grateful for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 18:35:20 2021 InstallationDate: Installed on 2021-01-31 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Assignee: Queen (queen8387) Status: New ** Tags: amd64 apport-bug focal ** Changed in: rhythmbox (Ubuntu) Assignee: (unassigned) => Queen (queen8387) ** Summary changed: - this program cannot be set as the default program + this program cannot be set as the default program (rhythmbox) ** Description changed: - I can't set 'Rhythmbox' as a default for listening to music. + I can't set 'Rhythmbox' as a default for listening to music. When I try to set 'Rhythmbox' as the default program (for music playback) this setting is not accepted. You cannot set this up, as the 'Movies' program is automatically set as the default program immediately. I have tried many ways, but no changes to this topic. + I will be grateful for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 18:35:20 2021 InstallationDate: Installed on 2021-01-31 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '/var/log/Xorg.0.log' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1922267 Title: this program cannot be set as the default program (rhythmbox) Status in rhythmbox package in Ubuntu: New Bug description: I can't set 'Rhythmbox' as a default for listening to music. When I try to set 'Rhythmbox' as the default program (for music playback) this setting is not accepted. You cannot set this up, as the 'Movies' program is automatically set as the default program immediately. I have tried many ways, but no changes to this topic. I will be grateful for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 18:35:20 2021 InstallationDate: Installed on 2021-01-31 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1922267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922266] [NEW] eth0 interface name change fails on Pi 3/3+
Public bug reported: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud- init, and simply handle this via a networkd .link file in ubuntu-raspi- settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop-raspi, not ubuntu- server-raspi. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918327] Re: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build on hirsute 21.04
** No longer affects: ubuntu-mate -- 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/1918327 Title: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build on hirsute 21.04 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed 2a. Launch Software & Updates, go to Additional Drivers tab, select nvidia-340 to install 2b. Open terminal and execute `sudo apt-get install nvidia-340` Expected results: * nvidia-340 driver is installed Actual results: * nvidia-340 driver is not installed: $ dpkg -l | grep -i nvidia ii libcuda1-340 340.108-0ubuntu7 amd64NVIDIA CUDA runtime library ii mate-optimus 20.10.0-1ubuntu2 all MATE Desktop applet for controlling NVIDIA Optimus graphics cards iF nvidia-340 340.108-0ubuntu7 amd64NVIDIA binary driver - version 340.108 ii nvidia-opencl-icd-340340.108-0ubuntu7 amd64NVIDIA OpenCL ICD ii nvidia-prime 0.8.16 all Tools to enable NVIDIA's Prime ii nvidia-settings 460.39-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driver ii screen-resolution-extra 0.18build2 all Extension for the nvidia-settings control panel ^^^ note "iF nvidia-340" above. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: nvidia-340 340.108-0ubuntu7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 5.10.0-14-generic Date: Tue Mar 9 23:43:06 2021 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu7:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:368:40: error: passing argument 1 of ‘drm_prime_pages_to_sg’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-09 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210309) PackageVersion: 340.108-0ubuntu7 Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.7.1ubuntu3 apt 2.2.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1918327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922186] Re: ibus very difficult to restart
On 2021-04-01 16:23, DarkTrick wrote: > 1) It has a "Quit" option. If you should not quit it, there should be > no "Quit" option in the menu. That confuses me. I see that you use an XFCE desktop, and the only icon you should have AFAIK is "IBus Preferences" which starts a GUI for certain settings. Quitting that should only quit "IBus Preferences" while ibus-daemon should keep running. If you have something else, can you please take a screenshot to show us what it looks like. ibus-daemon is not an application. It's a background process, and on Debian/Ubuntu it's started silently at login while a few related environment variables are set. If you want to use some other IM framework, e.g. Fcitx or uim, you can tell the system so in "Language Support", and after next reboot it will start Fcitx or uim at login instead and assign other values to the related variables. > However, in crashes in 18.xx I remember that `ibus restart` would > simply tell me "there is no running instance" and do nothing. Right, if the ibus-daemon process is not running, "ibus restart" won't help. But there are 'crashes' which don't kill ibus-daemon, and then "ibus restart" often helps. -- 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/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: Incomplete Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Tags added: rls-hh-incoming -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Another user affected on 20.04. here, I don't know how or why, but doing the Alt+F2 r made it go away too. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922186] Re: ibus very difficult to restart
> It's not clear to me why you would want to kill the ibus-daemon process in the first place I would say that's no valid argument because: 1) It has a "Quit" option. If you should not quit it, there should be no "Quit" option in the menu. 2) ibus is not system critical. Non-system critical processes should be restartable > it differs depending on the desktop environment. I appreciate the commands, but why should I as user need to care about that? > In situations where ibus crashes somehow, and IM inputting stops working, you > normally can do: > ibus restart 1) I did not have crashes since 20.04. However, in crashes in 18.xx I remember that `ibus restart` would simply tell me "there is no running instance" and do nothing. 2) Why can't this happen, when I call ibus from application menu? -- 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/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: Incomplete Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
** Description changed: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in - original description below + original description below; specifically messages containing text with + "below legacy directory /var/run/" or "lacks a native systemd unit file" [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. -- You received
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
Łukasz: this change makes firefox (and thunderbird) a native Wayland client application when run under Wayland, as opposed to using XWayland. Functionally, there shouldn't be any difference, but visual/perceived performance should be better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Committed Status in vlc package in Ubuntu: Invalid Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921794] Re: connection to scanner very slow
** Attachment added: "simple scan log from $HOME/.cache/simple-scan" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+attachment/5483197/+files/simple-scan.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921794 Title: connection to scanner very slow Status in simple-scan package in Ubuntu: Incomplete Bug description: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description: HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921794] Re: connection to scanner very slow
** Attachment added: "pdf of scan" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+attachment/5483196/+files/ScanTest.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921794 Title: connection to scanner very slow Status in simple-scan package in Ubuntu: Incomplete Bug description: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description: HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921794] Re: connection to scanner very slow
I did as requested. The konsole output is attached as simple-scan-output.txt. (also the scan as pdf). Not all output was saved - the konsole seems to retain only a certain amount of text. ** Attachment added: "output log" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+attachment/5483195/+files/simple-scan-output.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921794 Title: connection to scanner very slow Status in simple-scan package in Ubuntu: Incomplete Bug description: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description: HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
Olivier: what does this change imply? I'm asking since it's past FF, and it's hard for me to say if this falls under the brackets of a feature or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Committed Status in vlc package in Ubuntu: Invalid Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922241] [NEW] [Wayland] Dash to dock don't show all applications
Public bug reported: This extension has been updated these days and the "All" button (next to "Frequent" button) has crash and no longer shows all applications. Disabling Ubuntu-Dock via Extensions Panel this function works perfectly again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 09:56:04 2021 InstallationDate: Installed on 2020-11-12 (139 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1922241 Title: [Wayland] Dash to dock don't show all applications Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This extension has been updated these days and the "All" button (next to "Frequent" button) has crash and no longer shows all applications. Disabling Ubuntu-Dock via Extensions Panel this function works perfectly again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 09:56:04 2021 InstallationDate: Installed on 2020-11-12 (139 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1922241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922112] Re: libreoffice (var. versions under v.7.x) on arm64, terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' \ Fatal exception: Signal
I've tried compiling from latest Git source of LibreOffice as to their instructions; everything else seems to compile pretty much OK, but alas; the same 'com::sun::star::uno::Sequence' is there to haunt during the compile -- it registers as a "warning" rather than an "error", so that's why it's probably passed on to pre-compiled binaries. Details during 'make -j4': [CXX] codemaker/source/codemaker/exceptiontree.cxx /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:65: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:76: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:86: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:96: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:106: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:116: warning: unexpected command endverbatim /home/ubuntu/builds/core/instdir/sdk/include/rtl/uri.h:124: warning: unexpected command endverbatim warning: Included by graph for 'config.h' not generated, too many nodes (81), threshold is 50. Consider increasing DOT_GRAPH_MAX_NODES. warning: Included by graph for 'types.h' not generated, too many nodes (52), threshold is 50. Consider increasing DOT_GRAPH_MAX_NODES. a00518:146: warning: explicit link request to 'com::sun::star::uno::Sequence< E >' could not be resolved a00518:267: warning: unexpected token TK_COMMAND_BS as the argument of _internalref There is a LibreOffice Q&A page that might have to do something with this subject matter: https://ask.libreoffice.org/en/question/189887/uno- hanging-or-libreoffice-crashing/ Then again, there's multiple bug reports that are open here on Launchpad considering UNO+LibreOffice. Perhaps this needs a closer look? -- 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/1922112 Title: libreoffice (var. versions under v.7.x) on arm64, terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' \ Fatal exception: Signal 6 Status in libreoffice package in Ubuntu: New Bug description: Hi there, I've had the recurring problem on multiple 64-bit Ubuntu installations on multiple Raspberry Pi 4B's [aarch64/arm64] where libreoffice crashes on startup -- this seems to be a persistent bug, as it has happened to me on 20.04 LTS (arm64) as well as more recently on 20.10 groovy (arm64), whether I've used the official APT packages or the LibreOffice Launchpad PPA's. I've tried looking around for the bug and for example, deleted the existing user config etc. -- to no avail. As for the window manager, I'm running on Xubuntu (Xfce/Xfwm4) and with the latest available upstream kernel (5.8.0.1020-raspi), although LibreOffice crashing on startup has been a persisting problem on my RPi4B Ubuntu installations for quite some time now, probably around a half a year or so. Every now and then, as the apt packages get updated, LibreOffice actually works (!), so that's kind of odd. Here's the error message I get (same crash applies for all other libreoffice executables that I've tried): $ libreoffice terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c850)[0xb3f50850] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c9ec)[0xb3f509ec] linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xb85805d8] /lib/aarch64-linux-gnu/libc.so.6(gsignal+0xdc)[0xb3d7ce9c] /lib/aarch64-linux-gnu/libc.so.6(abort+0xf4)[0xb3d6950c] /lib/aarch64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x1a8)[0xb135f888] /lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f1dc)[0xb135c1dc] /lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f240)[0xb135c240] /lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f534)[0xb135c534] /usr/lib/libreoffice/program/libmergedlo.so(+0x116b51c)[0xb50f251c] /usr/lib/libreoffice/program/libmergedlo.so(+0x116bbc4)[0xb50f2bc4] /usr/lib/libreoffice/program/libmergedlo.so(+0x116c228)[0xb50f3228] /usr/lib/libreoffice/program/libmergedlo.so(+0x116ccd4)[0xb50f3cd4] /usr/lib/libreoffice/program/libmergedlo.so(+0x11709fc)[0xb50f79fc] /usr/lib/libreoffice/program/libmergedlo.so(+0x2c4b6e0)[0xb6bd26e0] /usr/lib/libreoffice/program/libmergedlo.so(+0x2c4be68)[0xb6bd2e68] /usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x78)[0xb6bca33c] /usr/lib/libreoffice/program/libmergedlo.so(+0x2c905c8)[0xb6c175c8] /usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x124)[0xb6c18b54] /usr/
[Desktop-packages] [Bug 1922186] Re: ibus very difficult to restart
It's not clear to me why you would want to kill the ibus-daemon process in the first place. It's setup (via im-config) to be started and configured at login. As regards commands to start ibus from terminal it differs depending on the desktop environment. GNOME: ibus-daemon --panel disable --xim -d Other desktop environments: ibus-daemon --xim -d In situations where ibus crashes somehow, and IM inputting stops working, you normally can do: ibus restart to fix it. ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: Incomplete Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885086] Re: XDG "Desktop" item not translated on Live CD
Good, then we can keep focusing on the live session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/885086 Title: XDG "Desktop" item not translated on Live CD Status in Ubuntu Translations: Triaged Status in casper package in Ubuntu: In Progress Status in xdg-user-dirs package in Ubuntu: Opinion Bug description: When I switch the language on my Oneiric Live CD, other XDG directories are translated except the "Desktop" item. When I have a look inside ~/.config/user-dirs.dirs, the string is untranslated (other strings in the file are translated all right). If I run xdg- user-dirs-update, ~/.config/user-dirs.dirs is updated to the correct translation. So I suppose that the default Live CD user is created by some not-localized hackish solution. If this seems not so important, since installed systems have the "Desktop" directory translated all right (at least I hope so, because my system has), it certainly affects all Ubuntu localized Live-CDs and makes them fail the basic "translated or not surface check". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/885086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I'm adding the following, so searches of this symptom will also find this thread: Once the bug is triggered, it also repeatably affects LibreOffice Calc - if you click-select a worksheet tab or drag-select a set of cells then release mouse, it enters drag-and-drop mode, and (strangely) draws a thick border around the selection, which you cannot undo or reformat. I can exit DND mode with ESC. And temporarily remove the problem with the xinput solution, but I agree with #53 that disabling touch screen is insufficient - you need to re-enable too. System details: Lenovo Yoga 3 Pro with ATML1000:00 03EB:8A10 touch screen 20.04.1-Ubuntu (although this bug has been affecting previous versions for me) Linux kernel 5.8.0-48-generic -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Seems the rendering performance penalty of desktop-icons-ng on my machine is roughly 10%. That's not terrible and especially considering desktop-icons-ng is implemented as a full-screen GtkWindow (not a Clutter widget) in a separate process(!) If you need better performance then just remove the extension via the 'Extensions' app. I'm really not sure what can be done about compositing it any faster though. Maybe more local redraws instead of global redraws? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in Dash to dock: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1872796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922112] Re: libreoffice (var. versions under v.7.x) on arm64, terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' \ Fatal exception: Signal
** Description changed:
Hi there,
I've had the recurring problem on multiple 64-bit Ubuntu installations
on multiple Raspberry Pi 4B's [aarch64/arm64] where libreoffice crashes
on startup -- this seems to be a persistent bug, as it has happened to
me on 20.04 LTS (arm64) as well as more recently on 20.10 groovy
(arm64), whether I've used the official APT packages or the LibreOffice
Launchpad PPA's.
I've tried looking around for the bug and for example, deleted the
existing user config etc. -- to no avail.
As for the window manager, I'm running on Xubuntu (Xfce/Xfwm4) and with
the latest available upstream kernel (5.8.0.1020-raspi), although
LibreOffice crashing on startup has been a persisting problem on my
RPi4B Ubuntu installations for quite some time now, probably around a
half a year or so. Every now and then, as the apt packages get updated,
LibreOffice actually works (!), so that's kind of odd.
Here's the error message I get (same crash applies for all other
libreoffice executables that I've tried):
$ libreoffice
terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'
Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c850)[0xb3f50850]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c9ec)[0xb3f509ec]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xb85805d8]
/lib/aarch64-linux-gnu/libc.so.6(gsignal+0xdc)[0xb3d7ce9c]
/lib/aarch64-linux-gnu/libc.so.6(abort+0xf4)[0xb3d6950c]
/lib/aarch64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x1a8)[0xb135f888]
/lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f1dc)[0xb135c1dc]
/lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f240)[0xb135c240]
/lib/aarch64-linux-gnu/libstdc++.so.6(+0x9f534)[0xb135c534]
/usr/lib/libreoffice/program/libmergedlo.so(+0x116b51c)[0xb50f251c]
/usr/lib/libreoffice/program/libmergedlo.so(+0x116bbc4)[0xb50f2bc4]
/usr/lib/libreoffice/program/libmergedlo.so(+0x116c228)[0xb50f3228]
/usr/lib/libreoffice/program/libmergedlo.so(+0x116ccd4)[0xb50f3cd4]
/usr/lib/libreoffice/program/libmergedlo.so(+0x11709fc)[0xb50f79fc]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2c4b6e0)[0xb6bd26e0]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2c4be68)[0xb6bd2e68]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x78)[0xb6bca33c]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2c905c8)[0xb6c175c8]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x124)[0xb6c18b54]
/usr/lib/libreoffice/program/libmergedlo.so(+0x30956a4)[0xb701c6a4]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xd8928)[0xad5e0928]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xda1d4)[0xad5e21d4]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xea218)[0xad5f2218]
/usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x4a0)[0xb7029d60]
/usr/lib/libreoffice/program/libmergedlo.so(_Z10ImplSVMainv+0xf8)[0xb702b468]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x9c)[0xb5f66f3c]
/usr/lib/libreoffice/program/soffice.bin(+0x8b4)[0xd806e8b4]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0xe8)[0xb3d69878]
/usr/lib/libreoffice/program/soffice.bin(+0x904)[0xd806e904]
As for troubleshooting, I've been following i.e. these instructions for
suggestions on how to try fixing the install [from:
https://forum.openoffice.org/en/forum/viewtopic.php?f=16&t=53761 ]:
1. Made sure I don't have any existing OpenOffice packages installed
(ran 'dpkg -l | grep openoffice').
2. Deleted the entire configuration directory ("libreoffice/") under
"~/.config/".
3. I still can't even run 'libreoffice --help' without getting the same
error message as otherwise (although with 'libreoffice --help' it's much
shorter):
terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'
+ As of now, these are the packages for LibreOffice that I have installed
+ ('dpkg -l | grep libreoffice'):
+
+ ii liblibreoffice-java
1:7.0.3-0ubuntu0.20.10.1 all LibreOffice UNO
runtime environment -- Java library
+ ii libreoffice
1:7.0.3-0ubuntu0.20.10.1 arm64office productivity
suite (metapackage)
+ rc libreoffice-avmedia-backend-gstreamer
1:7.0.3-0ubuntu0.20.10.1 arm64transitional package
for GStreamer backend for LibreOffice
+ ii libreoffice-base
1:7.0.3-0ubuntu0.20.10.1 arm64office productivity
suite -- database
+ ii libreoffice-base-core
[Desktop-packages] [Bug 1917044] Re: Allow launching does not work
** Tags added: hirsute ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #111 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/111 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/111 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1917044 Title: Allow launching does not work Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Bug description: Copied an app eg firefox.desktop from /usr/share/applications to desktop. new icon on desktop is a gray rectangle with a gear. right click on the icon on desktop. click on 'Allow launching' - nothing happen - icon should change to Firefox icon and Firefox should start if clicked click on Properties -> Permissions -> Allow executing: OK problem both in Wayland and X11. journalctl says: feb 26 13:50:53 corrado-x5-hh-0107 systemd-resolved[614]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. feb 26 13:50:53 corrado-x5-hh-0107 systemd-resolved[614]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. feb 26 13:50:54 corrado-x5-hh-0107 systemd-resolved[614]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1917044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922216] Re: SRU the current 3.36.10 stable update
Closing for the current ubuntu serie since we are on 3.38+ ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1922216 Title: SRU the current 3.36.10 stable update Status in evince package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including a theme fix and some translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the viewer to display documents, pdf mostly but also dvi, ps and other supported types. Ensure that annotations and still loaded and that it's possible to add new ones, that searching for text and selecting is also working. * Regression potential The update has fixes around display scaling on x11 so verify that the rendering is still correct there while unscaled and with scaling enabled. There is also a change impacting fonts on dvi document so we should test several of those to ensure there is no unwanted side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922216] [NEW] SRU the current 3.36.10 stable update
Public bug reported: * Impact That's the current GNOME stable update, including a theme fix and some translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the viewer to display documents, pdf mostly but also dvi, ps and other supported types. Ensure that annotations and still loaded and that it's possible to add new ones, that searching for text and selecting is also working. * Regression potential The update has fixes around display scaling on x11 so verify that the rendering is still correct there while unscaled and with scaling enabled. There is also a change impacting fonts on dvi document so we should test several of those to ensure there is no unwanted side effect. ** Affects: evince (Ubuntu) Importance: Low Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1922216 Title: SRU the current 3.36.10 stable update Status in evince package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including a theme fix and some translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the viewer to display documents, pdf mostly but also dvi, ps and other supported types. Ensure that annotations and still loaded and that it's possible to add new ones, that searching for text and selecting is also working. * Regression potential The update has fixes around display scaling on x11 so verify that the rendering is still correct there while unscaled and with scaling enabled. There is also a change impacting fonts on dvi document so we should test several of those to ensure there is no unwanted side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922211] [NEW] Rubber band only works in the top-left quarter of the desktop
Public bug reported: Rubber band only works in the top-left quarter of the desktop when using display scale 200%. Even less at 300%. It only works correctly at display scale 100%. ** Affects: gnome-shell-extension-desktop-icons-ng Importance: Unknown Status: Unknown ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: hirsute ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #87 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/87 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/87 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1922211 Title: Rubber band only works in the top-left quarter of the desktop Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: In Progress Bug description: Rubber band only works in the top-left quarter of the desktop when using display scale 200%. Even less at 300%. It only works correctly at display scale 100%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1922211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 116453] Re: evince can not find ü in attached PDF
The word Über is now found when searching the attached PDF within Evince on Ubuntu 18.04.5 "Bionic Beaver" using evince 3.28.4-0ubuntu1.2 and poppler 0.62.0-2ubuntu2.12. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/116453 Title: evince can not find ü in attached PDF Status in Poppler: Fix Released Status in poppler package in Ubuntu: Fix Released Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with the attached document is when one searches for: über it is found: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453/+attachment/102979/+files/example.pdf 4) What happens instead is it does not return any matches. WORKAROUND: Use the built-in PDF viewer+search with chromium-browser or chrome (doesn't work in Firefox). apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages apt-cache policy google-chrome-stable:i386 google-chrome-stable:i386: Installed: 39.0.2171.95-1 Candidate: 39.0.2171.95-1 Version table: *** 39.0.2171.95-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 Date: Wed May 23 18:22:27 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en PATH=~/local/bin:~/local/lib:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux copper 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 116453] Re: evince can not find ü in attached PDF
** Changed in: poppler (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/116453 Title: evince can not find ü in attached PDF Status in Poppler: Fix Released Status in poppler package in Ubuntu: Fix Released Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with the attached document is when one searches for: über it is found: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453/+attachment/102979/+files/example.pdf 4) What happens instead is it does not return any matches. WORKAROUND: Use the built-in PDF viewer+search with chromium-browser or chrome (doesn't work in Firefox). apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages apt-cache policy google-chrome-stable:i386 google-chrome-stable:i386: Installed: 39.0.2171.95-1 Candidate: 39.0.2171.95-1 Version table: *** 39.0.2171.95-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 Date: Wed May 23 18:22:27 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en PATH=~/local/bin:~/local/lib:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux copper 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1109210] Re: LibreOffice freezes indefinitely when opening attached PDF
This is still occurring on Ubuntu 18.04.5 "Bionic Beaver" with libreoffice 1:6.0.7-0ubuntu0.18.04.10. ** Tags added: bionic -- 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/1109210 Title: LibreOffice freezes indefinitely when opening attached PDF Status in libreoffice package in Ubuntu: Triaged Bug description: I tried opening the attached PDF with LibreOffice but LibreOffice just freezes and has to be force-killed. I get the same problem with this PDF on LibreOffice 4.0 RC1 on Windows 7 64-bit. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-draw 1:3.6.2~rc2-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 29 14:23:53 2013 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1109210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865838] Re: no error displayed on failed fingerprint authentication
Test on XPS 9310 with 5.8.0-48-generic kernel, BIOS: 1.2.5 with, codename: groovy. Login page will pop up message to notify user, if user uses finger which is not registered. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentication Status in gdm: New Status in OEM Priority Project: New Status in fprintd package in Ubuntu: Triaged Status in gdm package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in fprintd source package in Focal: Triaged Status in gdm source package in Focal: New Status in gnome-shell source package in Focal: In Progress Status in gnome-shell source package in Groovy: Fix Committed Bug description: [ Impact ] No fingerprint errors are exposed on fingerprint login failures. from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. [ Test case ] 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. Each time the wrong finger is used an error is shown 5. After 3 times retries, an authentication error is shown, suggesting to use another method. [ Regression potential] Wrong errors are shown during both fingerprint auth and other kinds of authentications. Password failures aren't properly exposed. Verification can't restart on error. Password authentication doesn't work anymore for users with no enrolled prints (as per LP: #1915570) --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922187] [NEW] [snap] No menu on i3wm/xorg
Public bug reported: Description No menu is shown in applications when installed with snap. Startup of libreoffice is extremely slow. When installing with "apt install libreoffice" menus are shown and startup is very fast. Expected: Menu bar is shown Actual: Menu bar is not shown Setup Ubuntu server 20.04.2 LTS i3 4.17.1 sudo X -version gives: X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu Current Operating System: Linux dev 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=/dev/mapper/ubuntu--vg-lv--0 ro Build Date: 17 January 2021 09:13:31AM xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1922187 Title: [snap] No menu on i3wm/xorg Status in libreoffice package in Ubuntu: New Bug description: Description No menu is shown in applications when installed with snap. Startup of libreoffice is extremely slow. When installing with "apt install libreoffice" menus are shown and startup is very fast. Expected: Menu bar is shown Actual: Menu bar is not shown Setup Ubuntu server 20.04.2 LTS i3 4.17.1 sudo X -version gives: X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu Current Operating System: Linux dev 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=/dev/mapper/ubuntu--vg-lv--0 ro Build Date: 17 January 2021 09:13:31AM xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1922187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922186] [NEW] ibus very difficult to restart
Public bug reported: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description:Ubuntu 20.10 Release:20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- 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/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: New Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelea
