[Desktop-packages] [Bug 2012738] Re: language support crashes on install missing translations or writing aids
** Tags removed: rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2012738 Title: language support crashes on install missing translations or writing aids Status in devscripts package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Bug description: Installing missing "translations or writing aids" crashes the gnome- language-selector app. I have attached a recording (sorry should have had capture cursor on) and relevant stack trace from journalctl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/2012738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop
Public bug reported: When building images with livecd-rootfs, there is a hook to set up oem- config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011722 Title: Move oem-config-setup steps into ubuntu-raspi-settings-desktop Status in ubuntu-settings package in Ubuntu: New Bug description: When building images with livecd-rootfs, there is a hook to set up oem-config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490
@arutyun-akopov, can you try the workaround detailed in comment #1? ** Changed in: systemd (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1896540 Title: Incorrectly specified Touchpad size for Lenovo T490 Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Bug description: The vertical sensitivity of the touchpad on my laptop Lenovo T490 seemed significantly higher than the horizontal sensitivity. After doing some research I found out that the touchpad size is incorrectly listed by the kernel. Touchpad size listed by the kernel: 77x107mm The real size of the touchpad: 68x100mm Description: Ubuntu 20.04.1 LTS Release: 20.04 Systemd version: 245.4-4ubuntu3.2 Output from the touchpad-edge-detector: miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 /dev/input/event5 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5 Move one finger around the touchpad to detect the actual edges Kernel says: x [1266..5678], y [1162..4694] Touchpad sends: x [1266..5678], y [1161..4694] -^C Touchpad size as listed by the kernel: 77x107mm User-specified touchpad size: 68x100mm Calculated ranges: 4412/3533 Suggested udev rule: # evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:* EVDEV_ABS_00=1266:5678:65 EVDEV_ABS_01=1161:4694:35 EVDEV_ABS_35=1266:5678:65 EVDEV_ABS_36=1161:4694:35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960458] [NEW] patch git_socket_dir.patch causing FTBFS in gspell
Public bug reported: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: New Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test Case 3 verification ubuntu@focalvm:~$ apt-cache policy ghostscript ghostscript: Installed: 9.50~dfsg-5ubuntu4.4 Candidate: 9.50~dfsg-5ubuntu4.4 Version table: *** 9.50~dfsg-5ubuntu4.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 9.50~dfsg-5ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 9.50~dfsg-5ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@focalvm:~$ gs waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 4000 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4308816 2840291 2772400 1477426 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3041706 2792600 1499350 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 28 18 282 764 %%HiResBoundingBox: 28.547999 18.251999 281.375991 763.055977 >>showpage, press to continue<< GS>quit ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ gs -r300x300 -sPAPERSIZE=letter -sOUTPUTFILE=waterfal.jpg -dNOPAUSE -dBATCH waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 300 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4329016 2846189 1581112 279688 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3044172 1601312 301839 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 22 18 282 763 %%HiResBoundingBox: 22.080001 18.240001 281.520011 762.960029 ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ gs -r300x300 -sPAPERSIZE=letter -sOUTPUTFILE=waterfal.jpg -dNOPAUSE -dBATCH -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 300 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4329016 2848173 1581112 279944 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3046156 1601312 302095 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 22 18 282 763 %%HiResBoundingBox: 22.080001 18.240001 281.520011 762.960029 ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ ** 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 ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test showing the failure with ocrfeeder before installing from -proposed ** Attachment added: "gs_test2_fail_case.png" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5542883/+files/gs_test2_fail_case.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the terminal from which it was launched * Install ghostscript from -proposed * Run ocrfeeder from a terminal and attempt to import the PDF file again * Note that the pages of the PDF are displayed in ocrfeeder and no error is reported in the terminal - Test Plan 3 --- * Using the version of ghostscript in -proposed, run a variety of different commands to ensure there has been no regression. * gs * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH -- [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test showing ocrfeeder succeeding with the version of ghostscript in -proposed ** Attachment added: "gs_test2_success_casae.png" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5542884/+files/gs_test2_success_casae.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the terminal from which it was launched * Install ghostscript from -proposed * Run ocrfeeder from a terminal and attempt to import the PDF file again * Note that the pages of the PDF are displayed in ocrfeeder and no error is reported in the terminal - Test Plan 3 --- * Using the version of ghostscript in -proposed, run a variety of different commands to ensure there has been no regression. * gs * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH -- [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
The verification passed for focal. --- Test case 1 verification ubuntu@focalvm:~$ apt-cache policy ghostscript ghostscript: Installed: 9.50~dfsg-5ubuntu4.3 Candidate: 9.50~dfsg-5ubuntu4.4 Version table: 9.50~dfsg-5ubuntu4.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages *** 9.50~dfsg-5ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 9.50~dfsg-5ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@focalvm:~$ gs -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Error: /undefinedfilename in (waterfal.ps) Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push Dictionary stack: --dict:724/1123(ro)(G)-- --dict:0/20(G)-- --dict:76/200(L)-- Current allocation mode is local Last OS error: Permission denied GPL Ghostscript 9.50: Unrecoverable error, exit code 1 ubuntu@focalvm:~$ sudo apt install ghostscript -y Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgs9 libgs9-common Suggested packages: ghostscript-x The following packages will be upgraded: ghostscript libgs9 libgs9-common 3 upgraded, 0 newly installed, 0 to remove and 33 not upgraded. Need to get 2,906 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 ghostscript amd64 9.50~dfsg-5ubuntu4.4 [51.8 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgs9 amd64 9.50~dfsg-5ubuntu4.4 [2,173 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgs9-common all 9.50~dfsg-5ubuntu4.4 [682 kB] Fetched 2,906 kB in 1s (4,127 kB/s) (Reading database ... 214058 files and directories currently installed.) Preparing to unpack .../ghostscript_9.50~dfsg-5ubuntu4.4_amd64.deb ... Unpacking ghostscript (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Preparing to unpack .../libgs9_9.50~dfsg-5ubuntu4.4_amd64.deb ... Unpacking libgs9:amd64 (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Preparing to unpack .../libgs9-common_9.50~dfsg-5ubuntu4.4_all.deb ... Unpacking libgs9-common (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Setting up libgs9-common (9.50~dfsg-5ubuntu4.4) ... Setting up libgs9:amd64 (9.50~dfsg-5ubuntu4.4) ... Setting up ghostscript (9.50~dfsg-5ubuntu4.4) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for man-db (2.9.1-1) ... ubuntu@focalvm:~$ gs -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 4000 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4308816 2842275 2772400 1477640 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3043690 2792600 1499460 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 28 18 282 764 %%HiResBoundingBox: 28.547999 18.251999 281.375991 763.055977 >>showpage, press to continue<< ubuntu@focalvm:~$ ** Description changed: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. - In addition see
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
racb: In order to add the steps from comment #2 as a useful test case, another bug in ocrfeeder needed to be fixed with an SRU. See https://bugs.launchpad.net/ubuntu/+source/ocrfeeder/+bug/1890013 for more details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. In addition see comment 6 and comment 2 for two more items in the test plan. -- ~racb [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
This bug appears to also exist in hirsute. Could you prepare a debdiff for hirsute as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537488/+files/lp1938442_bionic.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537487/+files/lp1938442_impish.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537375/+files/lp1938442_impish.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537379/+files/lp1938442_bionic.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Focal debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537378/+files/lp1938442_focal.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Hirsute debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537377/+files/lp1938442_hirsute.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537376/+files/lp1938442_impish.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Description changed: + [Impact] + * The directory ~/.hplip/.gnupg is readable by non-root users + * This directory contains only public keys, but should still + have the permissions changed to 700 for privacy reasons + + [Test Case] + * Install hplip and run `hp-plugin -i` + * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x + * rm -rf ~/.hplip and install hplip from -proposed + * run `hp-plugin -i` again + * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- + + [Regression Potential] + * Because of file permissions becoming more restrictive, + it is possible that some other hplip binaries would + fail to read the .gnupg directory + * To ensure this isn't the case, testing should be done + on different hplip use-cases to ensure they still + function properly + + [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. ** Patch added: "Jammy debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537374/+files/lp1938442_jammy.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: Fix for Ghostscript 9.50 upstream bug needs to be back-ported
** Patch added: "lp1913656.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5532989/+files/lp1913656.debdiff ** Changed in: ghostscript (Ubuntu Focal) Assignee: Till Kamppeter (till-kamppeter) => William Wilson (jawn-smith) ** Changed in: ghostscript (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: Fix for Ghostscript 9.50 upstream bug needs to be back-ported Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: In Progress Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Case] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: Fix for Ghostscript 9.50 upstream bug needs to be back-ported
** Tags added: verification-needed verification-needed-focal ** Description changed: - Ghostscript 9.50 exhibits - https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co - options) which causes (eg) ocrfeeder to fail to load PDF files: an input - file specified using the "... -- filename ..." command line syntax has - no read permission in the GS interpreter. + [Impact] + * The command line syntax `gs [options] -- ` fails +to load in the input file with a "permission denied" error. + * Per the ghostscript documentation, the `--` syntax is used as follows: + "-- filename arg1 ... +Takes the next argument as a file name as usual, +but takes all remaining arguments (even if they +have the syntactic form of switches) and defines +the name ARGUMENTS in userdict (not systemdict) +as an array of those strings, before running the +file. When Ghostscript finishes executing the file, +it exits back to the shell." + + [Test Case] + -- to be performed in a desktop environment -- + * Obtain a valid input file for ghostscript. The Source package +contains an `examples/` directory with plenty to choose from. + * `gs -- ` + * Observe that the test failed with a "permission denied" error. + * Install the version of ghostscript from focal-proposed. + * `gs -- ` + * Observe that the command succeeds and a ghostscript window. +appears with the output of the `gs` command. + + [Regression Potential] + * Since this patch affects command line processing, it is possible +that other arguments or command line syntaxes could be affected. + + [Original Description] + Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: Fix for Ghostscript 9.50 upstream bug needs to be back-ported Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: In Progress Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Case] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
We've found that this bug is much easier to create on certain monitors. satmandu, dnoedelfan: what monitors are you using? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Invalid Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-firmware-raspi2 source package in Impish: Confirmed Status in linux-raspi source package in Impish: Fix Committed Status in mutter source package in Impish: Invalid Bug description: [ Impact ] The desktop does not come up and the screen stays blank when using 'dtoverlay=vc4-kms-v3d' on a Pi 4 (as is the case in raspi desktop images). If the desktop does come up, playing video freezes the desktop and/or the system. The kernel log shows loads of WARNINGs and potentially firmware errors. [ Test Case ] Use a raspi desktop image, play video (youtube or VLC), move windows around, switch to and from fullscreen video playback. [ Where problems could occur ] The fixes are all local to the VC4 driver so (new) issues should only show up when that driver is in use. Potential problems are UI freezes, kernel stalls and crashes. [ Original Description ] Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
linux-raspi/5.11.0-1021.22 does not fix this problem. I am still seeing the flip_done timed out error message. ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Invalid Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-firmware-raspi2 source package in Impish: Confirmed Status in linux-raspi source package in Impish: Fix Committed Status in mutter source package in Impish: Invalid Bug description: [ Impact ] The desktop does not come up and the screen stays blank when using 'dtoverlay=vc4-kms-v3d' on a Pi 4 (as is the case in raspi desktop images). If the desktop does come up, playing video freezes the desktop and/or the system. The kernel log shows loads of WARNINGs and potentially firmware errors. [ Test Case ] Use a raspi desktop image, play video (youtube or VLC), move windows around, switch to and from fullscreen video playback. [ Where problems could occur ] The fixes are all local to the VC4 driver so (new) issues should only show up when that driver is in use. Potential problems are UI freezes, kernel stalls and crashes. [ Original Description ] Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
This was fixed previously in hirsute by an upstream merge that resulted in bluez 5.56-0ubuntu1 ** Changed in: bluez (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- 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/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Groovy: Won't Fix Status in bluez source package in Hirsute: Fix Released Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub 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 |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
Confirmed
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
Attached is a patch to add the hwcap metric to ubuntu-report.
** Patch added: "lp1922712.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+attachment/5485728/+files/lp1922712.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
New
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
New
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922792] [NEW] Bluez should notify users when they need to reboot to apply changes
Public bug reported: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes Status in bluez package in Ubuntu: New Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
