[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
I pulled the evince source and there does not appear to be any direct support for portals, and sandbox support is an untasked item on their roadmap. However it still may be possible via the gnome libs, or via dlopen. Those routes would need to be further investigated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946621] [NEW] Crash in libegl-mesa0 (eglReleaseThread)
Public bug reported: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Is there any option to do this via portals - ie can evince use https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus- org.freedesktop.portal.OpenURI to open the URI? Would then this allow to avoid going via xdg-open? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
I installed the ubuntu hirsute on a Dell machine which enabled sof audio driver and enanbled -proposed ppa, installed the pulseaudio 1:14.2-1ubuntu1.2 and alsa-ucm-conf 1.2.4-2ubuntu1.4. now the speaker and headphone has separate volume from gnome-sound-setting, this verified the pulseaudio's SRU. And adjust the external microphone's volume, the Mic Boost is changed accordingly. This verified the alsa- ucm-conf. And all audio output and input worked as well as before. Verification done on hirsute. thx. ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop worki
[Touch-packages] [Bug 1942899] Re: Revert Add ACCEL_LOCATION=base property for Dell clamshell models
This bug was fixed in the package systemd - 248.3-1ubuntu8 --- systemd (248.3-1ubuntu8) impish; urgency=medium [ Dan Streetman ] * d/p/dell-clamshell-accel-location-base-with-sku.patch: Revert incorrect patch (LP: #1942899) [ Lukas Märdian ] * Add d/p/Merge-pull-request-20705-from-yuwata-test-oomd-util.patch Replace lp1942113.patch with upstream commit 54966b7 (LP: #1942113) Files: - debian/patches/lp1942113.patch - debian/patches/Merge-pull-request-20705-from-yuwata-test-oomd-util.patch * Drop snapd cgroupv2 workaround, not needed anymore as of snapd 2.53~pre1 File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f9f340f74abdc4060cfd27a7cb3001929b6f9cf4 -- Lukas Märdian Mon, 04 Oct 2021 11:23:28 +0200 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1942899 Title: Revert Add ACCEL_LOCATION=base property for Dell clamshell models Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [impact] initial patch for LP: #1938259 was incorrect. [test case] this bug is only to revert the previous patch the upstream commit is:https://github.com/systemd/systemd/pull/20314/commits/55b29d8f130684bf1fd9fdfaef3bcca64b66930e checking for lack of the new 'sku' lines, and presence of the old lines, should be enough to verify this revert is correct [regression potential] any regression would likely be restricted to dell clamshell models matching the modified config settings [scope] the incorrect patch was added in f/h/i so only those need the patch removed/reverted [other info] this only reverts the patch that was added for bug 1938259, as the bug reporter indicated in that bug in comment 15 that the patch did not actually work correctly. a correct patch will need to go upstream first, so this bug is just to revert the last patch and respin systemd for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455780] Re: the i386 and amb64 versions break each other
** Changed in: libvpx (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1455780 Title: the i386 and amb64 versions break each other Status in libvpx package in Ubuntu: Fix Released Bug description: Trying to install wine1.6 leads to a series of dependency errors that lead back to libvpx1:i386. Trying to install that package means that libvpx1:amd64 is to be removed, which then wants to remove a whole bunch of other, important, packages, like software-center & gnome-control-center. $ sudo apt-get install libvpx1:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: colord dvipng ffmpeg gnome-control-center graphviz gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-good gvfs-backends handbrake-gtk hplip libavcodec-dev libavcodec54 libavformat-dev libavformat54 libcheese-gtk23 libcheese7 libchromaprint0 libgd3 libgphoto2-6 libgvc6 libopencv-contrib2.4 libopencv-highgui2.4 libopencv-legacy2.4 libopencv-objdetect2.4 libsane libvpx-dev libvpx1 printer-driver-postscript-hp python-pygraphviz sane-utils simple-scan software-center vlc vlc-nox vlc-plugin-notify vlc-plugin-samba xdot The following NEW packages will be installed: libvpx1:i386 0 upgraded, 1 newly installed, 38 to remove and 93 not upgraded. Need to get 525 kB of archives. After this operation, 188 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. --= $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 --= What I expect to happen: in a multi-arch system, that amd64 and i386 packages happily coexist. --= What happens instead: they break each other. $ apt-cache depends libvpx1 libvpx1 Depends: libc6 PreDepends: multiarch-support multiarch-support:i386 Replaces: libvpx1:i386 Breaks: libvpx1:i386 $ apt-cache depends libvpx1:i386 libvpx1:i386 Depends: libc6:i386 PreDepends: multiarch-support:i386 multiarch-support Replaces: libvpx1 Breaks: libvpx1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1455780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)
I ran into this today. My system has packagekit 1.2.2-2ubuntu3, so it does not look like it is related to bug 1943189. Since this computer currently is used for testing, I'm in no hurry to install the NVIDIA drivers so I can do some further testing, if needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1946196 Title: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257) Status in software-properties package in Ubuntu: Triaged Bug description: Additional Drivers fails to install nvidia-driver-470: Error while applying changes pk-client-error-quark: Cannot download packages whilst offline (257) But the machine is ONLINE with full Internet access. WORKAROUND: sudo apt install nvidia-driver-470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1946196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946595] Re: indicator-applet-complete clock occasionally shows UTC
Standalone is not indicator, it's mate-panel's built-in clock applet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1946595 Title: indicator-applet-complete clock occasionally shows UTC Status in indicator-datetime package in Ubuntu: New Bug description: Sometimes at login, but sometimes at other times, the clock in indicator-applet-complete starts showing UTC instead of local. It is not a system clock problem, in the terminal and in the standalone clock applet the time is correct. See https://i.stack.imgur.com/x11A4.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-applet-complete (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Oct 10 08:37:00 2021 InstallationDate: Installed on 2018-04-27 (1261 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: indicator-applet UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946595] Re: indicator-applet-complete clock occasionally shows UTC
Ok, but the standalone clock indicator works. The clock in "indicator applet complete" doesn't. See https://i.stack.imgur.com/x11A4.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1946595 Title: indicator-applet-complete clock occasionally shows UTC Status in indicator-datetime package in Ubuntu: New Bug description: Sometimes at login, but sometimes at other times, the clock in indicator-applet-complete starts showing UTC instead of local. It is not a system clock problem, in the terminal and in the standalone clock applet the time is correct. See https://i.stack.imgur.com/x11A4.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-applet-complete (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Oct 10 08:37:00 2021 InstallationDate: Installed on 2018-04-27 (1261 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: indicator-applet UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946595] Re: indicator-applet-complete clock occasionally shows UTC
The applet just shows what the actual indicator provides, so reassigning to indicator-datetime. ** Package changed: indicator-applet (Ubuntu) => indicator-datetime (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1946595 Title: indicator-applet-complete clock occasionally shows UTC Status in indicator-datetime package in Ubuntu: New Bug description: Sometimes at login, but sometimes at other times, the clock in indicator-applet-complete starts showing UTC instead of local. It is not a system clock problem, in the terminal and in the standalone clock applet the time is correct. See https://i.stack.imgur.com/x11A4.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-applet-complete (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Oct 10 08:37:00 2021 InstallationDate: Installed on 2018-04-27 (1261 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: indicator-applet UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946595] [NEW] indicator-applet-complete clock occasionally shows UTC
You have been subscribed to a public bug: Sometimes at login, but sometimes at other times, the clock in indicator-applet-complete starts showing UTC instead of local. It is not a system clock problem, in the terminal and in the standalone clock applet the time is correct. See https://i.stack.imgur.com/x11A4.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-applet-complete (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Oct 10 08:37:00 2021 InstallationDate: Installed on 2018-04-27 (1261 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: indicator-applet UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- indicator-applet-complete clock occasionally shows UTC https://bugs.launchpad.net/bugs/1946595 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
As 3 years before in bug 1756238 the root of the problem is VTE library. Downgrading VTE to version 2.91_0.62.3-1ubuntu1 ( https://packages.ubuntu.com/source/hirsute/vte2.91 ) fixes the issue. ** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Changed in: vte2.91 (Ubuntu) Status: New => Confirmed ** Changed in: gdebi (Ubuntu) Status: New => Confirmed ** No longer affects: dpkg (Ubuntu) ** Changed in: ubuntu-mate Status: New => Won't Fix ** Changed in: ubuntu-mate Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-1
[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
This bug is returned to impish as bug 1946499 . Please fix it. ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946597] Re: dpkg "Setting up " hangs on the every package that should be set up
** Description changed: So the hang occurs on the first package that should be set up, - alphabetically. + alphabetically. For example, if I run "sudo dpkg --configure -a", it + will hand on "Setting up acpid (1:2.0.32-1ubuntu2) ...". - Ubuntu 21.10 beta with KDE desktop. I believe the problem was caused by - dist-upgrade from 21.04. I use ZFS filesystem. + The problem may have been caused by dist-upgrade from 21.04. I use ZFS + filesystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 10 17:24:26 2021 InstallationDate: Installed on 2021-08-30 (40 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-07 (3 days ago) VarLogDistupgradeTermlog: ** Package changed: ubuntu-release-upgrader (Ubuntu) => dpkg (Ubuntu) ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: So the hang occurs on the first package that should be set up, alphabetically. For example, if I run "sudo dpkg --configure -a", it will hand on "Setting up acpid (1:2.0.32-1ubuntu2) ...". The problem may have been caused by dist-upgrade from 21.04. I use ZFS filesystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 - Package: ubuntu-release-upgrader-core 1:21.10.8 + Package: ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 10 17:24:26 2021 InstallationDate: Installed on 2021-08-30 (40 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-07 (3 days ago) VarLogDistupgradeTermlog: ** Description changed: So the hang occurs on the first package that should be set up, alphabetically. For example, if I run "sudo dpkg --configure -a", it - will hand on "Setting up acpid (1:2.0.32-1ubuntu2) ...". + will hang on "Setting up acpid (1:2.0.32-1ubuntu2) ...". The problem may have been caused by dist-upgrade from 21.04. I use ZFS filesystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 - Package: + Package: ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 10 17:24:26 2021 InstallationDate: Installed on 2021-08-30 (40 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-07 (3 days ago) VarLogDistupgradeTermlog: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1946597 Title: dpkg "Setting up " hangs on the every package that should be set up Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Bug description: So the hang occurs on the first package that should be set up, alphabetically. For example, if I run "sudo dpkg --configure -a", it will hang on "Setting up acpid (1:2.0.32-1ubuntu2) ...". The problem may have been caused by dist-upgrade from 21.04. I use ZFS filesystem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 10 17:24:26 2021 InstallationDate: Installed on 2021-08-30 (40 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-07 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1946597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1914839] Re: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically
** Changed in: ca-certificates (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914839 Title: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically Status in ca-certificates package in Ubuntu: Confirmed Status in ca-certificates package in Debian: Fix Released Bug description: While upgrading the ca-certificates package, a process got the error: SSL_ca_file /etc/ssl/certs/ca-certificates.crt does not exist This file should be replaced atomically, with no time gap where the file does not exist. (I am flagging this as a security vulnerability because, while I did not experience any security issue, I can imagine at least the possibility of this being exploitable in some way in some circumstances.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: New Status in dpkg package in Ubuntu: New Status in gdebi package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940097] Re: A forgotten "space"
Indeed. Looks like the trailing space is missing.
** Changed in: python-apt (Ubuntu)
Status: New => Confirmed
** Tags added: bitesize impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1940097
Title:
A forgotten "space"
Status in python-apt package in Ubuntu:
Confirmed
Bug description:
Hi
A "space" character has been forgotten in the "apt/package.py" file and line
"592".
I found this error while translating.
https://translations.launchpad.net/ubuntu/impish/+source/python-apt/+pots/python-apt/fa/36/+translate
if not dsc:
return _("Missing description for '%s'." <===
"Please report.") % (self.package.name)
This line should be like this
if not dsc:
return _("Missing description for '%s'. " <===
"Please report.") % (self.package.name)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1940097/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
