[Desktop-packages] [Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+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 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+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 1972991] Re: 22.04 Totem crashes on launch (segmentation fault)
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1972991 Title: 22.04 Totem crashes on launch (segmentation fault) Status in totem package in Ubuntu: Expired Bug description: Hello, Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem crashing. I have not been able to pin down when it works and when it doesn't, as playing the same videos seems to work sometimes and not work others. After it crashes, trying to open it again normally does not work and trying to launch totem from the commandline gives a segmentation fault. Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Segmentation fault (core dumped) $ totem Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 11 13:10:48 2022 InstallationDate: Installed on 2022-04-24 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1972991/+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 1975407] Re: pulseaudio is getting crashed
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1975407 Title: pulseaudio is getting crashed Status in pulseaudio package in Ubuntu: Expired Bug description: Operating System: Ubuntu 22.04 Life cycle: LTS Architecture: AMD64 Kernel version (uname -a): 5.15.0-30-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnm 3822 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 22 12:08:58 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.104 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.68 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.33 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: B7A48EA#ABV dmi.product.version: A1008C11 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2022-01-28T22:42:20.933634 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1975407/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
I believe he wasn't forcing me, just making a suggestion. Cheers 樂 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1982581] Re: Nautilus (files) hangs on first seach after restart/log in
I did try "sudo apt-get install xserver-xorg-core-dbg" with the above step, but I got E: Unable to locate package xserver-xorg-core-dbg I will try more from that page (that PPA?) tomorrow. That page seems a bit cryptic for me, but maybe I can manage. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1982581 Title: Nautilus (files) hangs on first seach after restart/log in Status in nautilus package in Ubuntu: Incomplete Bug description: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+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 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
sorry for the annoyance, the other debs are the same page but you shouldn't have to go through those problems. you can disable phasing with the options described in https://discourse.ubuntu.com/t/phased- updates-in-apt-in-21-04 but otherwise I would recommend waiting for the SRU to be available for everyone... -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. [ Test case(s) ] 1. Run gsettings set org.gnome.desktop.interface gtk-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu User theme settings should have not changed (Adwaita is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The icon theme is still reset if changed externally while the appearance panel is open. -- 1. Run gsettings set org.gnome.desktop.interface icon-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu Icon theme settings should have not changed (Adwaita icon theme is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The theme is still reset if changed externally while the appearance panel is open. -- 1. From Gedit settings, select an editor color scheme that is not Yaru or Yaru-dark. 2. Start Settings Appearance panel: gnome-control-center ubuntu Gedit theme should not have changed 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Does not change the Gedit theme, unless a Yaru variant is selected as gedit color scheme. [ Regression Potential ] Theme is not updated to upgraders that use some unsupported custom themes. Theme selection doesn't work in some custom configurations. --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968213/+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 1982581] Re: Nautilus (files) hangs on first seach after restart/log in
thanks, the backtrace indeed confirms it has to do with tracker. Could you install debug symbols as explained on https://wiki.ubuntu.com/DebuggingProgramCrash and get a detailed version? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1982581 Title: Nautilus (files) hangs on first seach after restart/log in Status in nautilus package in Ubuntu: Incomplete Bug description: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+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 1982493] Re: gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not set - and more
@alexmurray thanks - I have created a new public bug report here for further discussion and exploration: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1982607 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1982493 Title: gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not set - and more Status in freerdp2 package in Ubuntu: Fix Released Bug description: An immediate upgrade to 2.7.0 appears to be critical both for functionality (cannot work without it and having the backported NTLM fixes) and security: Please see the following for details: https://askubuntu.com/questions/1419705/gnome-remote-desktop-couldnt-retrieve-rdp-username-credentials-not-set-and The FreeRDP developers believe that Ubuntu has not backported the NTLM fixes from 2.7.0 to 2.6.1 and subsequently the reason for the failures users are experiencing. The easier / more clean path appears to be to upgrade to FreeRDP 2.7.0. It seems to be related to this vulnerability bounty: https://vuldb.com/?id.198528 See: * https://www.freerdp.com/2022/04/25/2_7_0-release * https://github.com/FreeRDP/FreeRDP/blob/2.7.0/ChangeLog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1982493/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
I also tested in a focal VM with the firefox snap from the candidate channel (version 103.0-1), and I can confirm that in conjunction with the xdg-desktop-portal backport in that PPA the "Show in Folder" functionality works as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: In Progress Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1982581] Re: Nautilus (files) hangs on first seach after restart/log in
I ran Nautilus with gdb. I hope this is good. PS: I closed the process when it started to hang (ctrl+c in the gdb terminal). ** Attachment added: "gdb nautilus" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+attachment/5604813/+files/gdb-nautilus.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1982581 Title: Nautilus (files) hangs on first seach after restart/log in Status in nautilus package in Ubuntu: Incomplete Bug description: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+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 1982564] Re: Shotwell Piwigo plugin does not upload
** Changed in: shotwell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1982564
Title:
Shotwell Piwigo plugin does not upload
Status in shotwell package in Ubuntu:
Invalid
Bug description:
Trying to upload photo to Piwigo via Shotwell plugin I got and error
like "URL not valid" (I got it in Italian).
Looking at Piwigo side I found this php error:
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Deprecated: substr(): Passing null
to parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Deprecated: substr(): Passing null
to parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
I think both Shotwell and Piwigo are updated to latest version:
Shotwell: 0.30.14 – “Celle”
Piwigo 12.3.0
Operating System: Linux
PHP: 8.1.2
MySQL: 5.5.5-10.6.7-MariaDB-2ubuntu1.1
Grafic Lib: GD 2.3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1982564/+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 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
Hi Sebastien, Thanks for the quick reply. I've found the correct version libfreerdp .deb package and tried to install it, but it had other dependency issues. I used this version: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+build/23822013 The package available in the repo is too new (available: ubuntu2.2, neede: ubuntu2.1). Installing build 2.2 yielded the following issues: karol@kolatek ~/Downloads $ sudo apt install ./libfreerdp2-2_2.6.1+dfsg1-3ubuntu2.1_amd64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'libfreerdp2-2' instead of './libfreerdp2-2_2.6.1+dfsg1-3ubuntu2.1_amd64.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libfreerdp2-2 : Depends: libwinpr2-2 (= 2.6.1+dfsg1-3ubuntu2.1) but 2.6.1+dfsg1-3ubuntu2.2 is to be installed E: Unable to correct problems, you have held broken packages. karol@kolatek ~/Downloads $ I'm sorry, but don't really feel like installing a possibly endless stream of dependencies. -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [ Impact ] I upgraded to the 22.04 beta last week from 21.10. I use a custom icon theme. Whenever I enter the Appearance tab in settings the icon theme is set back to Yaru. [ Test case(s) ] 1. Run gsettings set org.gnome.desktop.interface gtk-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu User theme settings should have not changed (Adwaita is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The icon theme is still reset if changed externally while the appearance panel is open. -- 1. Run gsettings set org.gnome.desktop.interface icon-theme Adwaita 2. Start Settings Appearance panel: gnome-control-center ubuntu Icon theme settings should have not changed (Adwaita icon theme is still in use) 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Interface and icon themes are matching the selected variant / accent. Note: The theme is still reset if changed externally while the appearance panel is open. -- 1. From Gedit settings, select an editor color scheme that is not Yaru or Yaru-dark. 2. Start Settings Appearance panel: gnome-control-center ubuntu Gedit theme should not have changed 3. Select a Dark/Light variant OR a Color in the Appearance panel: - Does not change the Gedit theme, unless a Yaru variant is selected as gedit color scheme. [ Regression Potential ] Theme is not updated to upgraders that use some unsupported custom themes. Theme selection doesn't work in some custom configurations. --- ProblemType: BugDistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 20:47:41 2022 InstallationDate: Installed on 2022-02-02 (64 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968213/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
I can see this might start getting out of hand so I'm going to be the referee here. Luis, you cannot force someone to work on a bug report. Alberto, since you're unwilling or unable to confirm, please keep the report as incomplete for gimp. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1982581] Re: Nautilus (files) hangs on first seach after restart/log in
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at https://wiki.ubuntu.com/Backtrace and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1982581 Title: Nautilus (files) hangs on first seach after restart/log in Status in nautilus package in Ubuntu: Incomplete Bug description: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+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 283115] Re: Gimp: toolbox windows can't be minimized
** Changed in: gimp (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/283115 Title: Gimp: toolbox windows can't be minimized Status in The Gimp: Fix Released Status in GTK+: Unknown Status in gimp package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: New Bug description: gimp 2.6 in intrepid: it is impossible to minimize toolbar windows; they have only a x-Button to close ideally, these windows should be minimized automatically when the (last) Gimp image window is minimized Update While waiting, I designed some sort of workaround : Gnome>System>Preferences>Windows>Double-click titlebar>Roll up To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/283115/+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 1982584] [NEW] wacom invisible cursor on startup, xorg 22.04
Public bug reported: With a Wacom One attached, the mouse cursor doesn't show. The mouse cursor can be made to show if, after logging in using the keyboard, you type the super-key, type "zoom", and arrow key over to zoom, and activate the zoom functionality with the enter key. Then the mouse cursor appears once your view is zoomed in, and you can deactivate the zoom and go about everything as normal with the mouse cursor working normally again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 06:45:04 2022 InstallationDate: Installed on 2022-01-30 (172 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-05-16 (66 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1982584 Title: wacom invisible cursor on startup, xorg 22.04 Status in mutter package in Ubuntu: New Bug description: With a Wacom One attached, the mouse cursor doesn't show. The mouse cursor can be made to show if, after logging in using the keyboard, you type the super-key, type "zoom", and arrow key over to zoom, and activate the zoom functionality with the enter key. Then the mouse cursor appears once your view is zoomed in, and you can deactivate the zoom and go about everything as normal with the mouse cursor working normally again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 06:45:04 2022 InstallationDate: Installed on 2022-01-30 (172 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-05-16 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982584/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
No, because I no longer install or use Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1959103] Re: polkitd crashes with segfault with specific config file
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: policykit-1 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1959103
Title:
polkitd crashes with segfault with specific config file
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
The following config file in
`/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a
segfault in `polkitd`.
```
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.color-manager.create-device" ||
action.id == "org.freedesktop.color-manager.create-profile" ||
action.id == "org.freedesktop.color-manager.delete-device" ||
action.id == "org.freedesktop.color-manager.delete-profile" ||
action.id == "org.freedesktop.color-manager.modify-device" ||
action.id == "org.freedesktop.color-manager.modify-profile") &&
subject.isInGroup("{group}")) {
return polkit.Result.YES;
}
});
```
1. As normal user: `systemctl restart cron.service`
2. Error message `Failed to restart cron.service: Message recipient
disconnected from message bus without replying`
3. `dmesg` reports:
```
58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp
7ffda31e45f0 error 4 in polkitd[558a96784000+f000]
[ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00
00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40
08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c
``
If you remove the 02-allow-colord.conf the segfault goes away and you
are normally prompted for a password. You can also find a couple of
references in the internet, e.g http://c-nergy.be/blog/?p=12043.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+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 1946769] Re: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout
It's a big joke for Brazillian users when somebody types ć: "oh, so you are using linux? They still didn't fix that? :D" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1946769 Title: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout Status in firefox package in Ubuntu: Confirmed Bug description: Since I upgraded to impish, firefox is the only application on my desktop which produces "ć" instead of "ç" when I enter the combination "'" + "c". I suspect it's because now it's a snap, and is not respecting some system-wide configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1946769/+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 1785184] Re: Screen scintillation with Nvidia GPU and nouveau
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1785184 Title: Screen scintillation with Nvidia GPU and nouveau Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: When using my Quadro K620 with the nouveau driver, the screen scintillates. This is more perceptible on the SDDM login screen and when viewing the desktop background. This does not happen when driving the GPU with the closed NVIDIA driver. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau 1:1.0.15-2 Uname: Linux 4.17.0-996-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Aug 3 09:22:34 2018 DistUpgraded: 2018-07-01 17:39:22,208 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Subsystem: Dell HD Graphics P530 [1028:06b7] NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098] InstallationDate: Installed on 2016-09-07 (694 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-996-generic root=UUID=cfbd19c8-1ab6-4c40-9d40-26479783657f ro video=DP-1:3840x2160 resume=PARTUUID=06a1b832-1aa6-48fe-8118-65f8c27f1091 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to bionic on 2018-07-01 (32 days ago) dmi.bios.date: 06/11/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd06/11/2018:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. drirc: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 3 09:20:31 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1785184/+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 1946769] Re: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout
Now with Jammy 22.04, I have no choice and firefox is forcibly a snap and the ć problem continues. It works fine in chrome, and the firefox binary tarball downloaded from https://getfirefox.com. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1946769 Title: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout Status in firefox package in Ubuntu: Confirmed Bug description: Since I upgraded to impish, firefox is the only application on my desktop which produces "ć" instead of "ç" when I enter the combination "'" + "c". I suspect it's because now it's a snap, and is not respecting some system-wide configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1946769/+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 1982581] [NEW] Nautilus (files) hangs on first seach after restart/log in
Public bug reported: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "screenshot while waiting" https://bugs.launchpad.net/bugs/1982581/+attachment/5604752/+files/2022-07-22-14%3A03%3A08_001-Workspace1.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1982581 Title: Nautilus (files) hangs on first seach after restart/log in Status in nautilus package in Ubuntu: New Bug description: I have a new laptop and Nautilus hangs on the first search I try it on after the laptop is restarted or logged in. I never had this problem with the old laptops, so it is new to me, but I did find others complaining about it. It seems to be something related to the tracker: https://askubuntu.com/questions/1257693/files-nautilus-hangs-at-start-and-for-searches?noredirect=1#comment2463463_1257693 While Nautilus hangs I get a system notice to either wait for it or close it, but if I close it, I never get through and I get the same but next time I search, so I have to wait. This wait can take 2 seconds or 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 14:03:53 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1036, 852)' InstallationDate: Installed on 2022-06-14 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1982581/+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 1969303] Re: "No package to remove" error when attempting to uninstall
My apologies, @fossfreedom. I forgot to upgrade/downgrade the snap- plugin package and didn't notice it being removed. I've repeated the test in the above comment, including package `gnome- software-plugin-snap` and all tests now passed. Unfortunately I don't have access to a clean install to test, but it works on the dirty install so I won't open a new issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Jammy: Fix Committed Bug description: [Impact] * The Ubuntu repository version of gnome-software in 22.04 does not allow a user to uninstall an application. For new users this could be be construed as disconcerting allowing only installing apps without the ability to remove those apps later if required. This SRU is applicable only to the gnome-software application installed from the repository and not the branded ubuntu-store snap that is the default in Ubuntu (but not in flavours such as Ubuntu Budgie) This fix for gnome-software has been backported from the v41 version of ubuntu's snap-store. The fixed software now checks for the status of a deb package installed - either manually installed or automatically as part of a distro install. Previously this check was not done and gnome-software defaulted to not allowing the package to be uninstalled. The new status check allows gnome-software to evaluate that the package can be uninstalled. [Test Plan] * Choose a package from the installed list in gnome-software. Click the trash icon. Note the error message that the package cannot be removed. * install gnome-software from the proposed repository. Logout and login. Repeat the trash icon click step above. This time the package can be removed. Confirm via either your distro menu or searching in GNOME Overview (if you are using gnome-software from the repository) that the application has been successfully removed. * Perform additional testing such as installing applications from the repository (change the source to "Ubuntu (deb)") and then deleting the application. * Perform additional testing such as installing applications from the snap repository (change the source to "Snap") and then deleting the application. [Where problems could occur] * The code changed is specific to 'packagekit' repos i.e. debian based repos. Thus it is sensitive to possible regressions when installing & removing apps. * The patch itself is well tested since it was backported to the ubuntu snap-store several weeks ago and has been rolled out. No adverse issues has been reported. * The risk would be that there could be additional changes to the snap-store that was not incorporated in gnome-software possibly producing different results. * The additional regression tests in the Test Plan will reveal this. [Other Info] * There is no need to backport this to Kinetic since a revised version of the patch has been upstreamed (GNOME Team) and is in the kinetic version. On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1248174] Re: Update the Ubuntu colour palette to fit the spec
Alberto Salvia Novella, you can create Ubuntu VMs and test in them, just like I do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1248174 Title: Update the Ubuntu colour palette to fit the spec Status in One Hundred Papercuts: Triaged Status in Inkscape: Fix Released Status in Ubuntu Accomplishments Daemon: Confirmed Status in Ubuntu Accomplishments Extra Information: Confirmed Status in Ubuntu Accomplishments System: Confirmed Status in Ubuntu Accomplishments Viewer: Confirmed Status in Ubuntu Accomplishments Web Gallery: Confirmed Status in Ubuntu Brand Guidelines website: Invalid Status in ubuntu-community: Fix Released Status in Ubuntu Community Accomplishments: Confirmed Status in Ubuntu Desktop Accomplishments: Confirmed Status in gimp package in Ubuntu: Incomplete Status in inkscape package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" colour palette. 2. Compare colour with "Ubuntu Orange" in http://design.ubuntu.com/brand/colour-palette. ** EXPECTED BEHAVIOUR ** - The colour to be the same. ** REAL BEHAVIOUR ** - The colour is different. - The colours listed in the palette from Inkscape have no relationship with the ones in design.ubuntu.com. *** WORK-AROUND *** - To use the colours in http://design.ubuntu.com/brand/colour-palette instead. RELEVANT DETAILS - Orange colour is very similar, but not equal. So it's very probable someone use the wrong colour in their designs for Ubuntu. - In fact, the logo of "Ubuntu" project in Launchpad is affected (https://launchpad.net/ubuntu). - A demonstrative image is attached to this bug. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: inkscape 0.48.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 13:47:52 2013 InstallationDate: Installed on 2013-05-21 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+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 1969303] Re: "No package to remove" error when attempting to uninstall
Further to Roberts observations: I've done a clean Ubuntu Budgie install and fully up-to-date. Confirmed I saw the error reported here when uninstalling a .deb. Confirmed that snap installation and snap removal works as expected without any error reported. Upgraded from the proposed repo version 41.5-2ubuntu2 sudo apt install gnome-software gnome-software-common gnome-software- plugin-snap logged out and logged in. Retested snap installation and snap removal - as before works expected without any error reported. Retested .deb install and deb removal - no error reported when uninstalling and the app was successfully removed. Thus I'm happy to verify this bug report. Robert - I would raise a separate issue for your snap removal issue - please though do test on a clean install and verify as I have above ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Jammy: Fix Committed Bug description: [Impact] * The Ubuntu repository version of gnome-software in 22.04 does not allow a user to uninstall an application. For new users this could be be construed as disconcerting allowing only installing apps without the ability to remove those apps later if required. This SRU is applicable only to the gnome-software application installed from the repository and not the branded ubuntu-store snap that is the default in Ubuntu (but not in flavours such as Ubuntu Budgie) This fix for gnome-software has been backported from the v41 version of ubuntu's snap-store. The fixed software now checks for the status of a deb package installed - either manually installed or automatically as part of a distro install. Previously this check was not done and gnome-software defaulted to not allowing the package to be uninstalled. The new status check allows gnome-software to evaluate that the package can be uninstalled. [Test Plan] * Choose a package from the installed list in gnome-software. Click the trash icon. Note the error message that the package cannot be removed. * install gnome-software from the proposed repository. Logout and login. Repeat the trash icon click step above. This time the package can be removed. Confirm via either your distro menu or searching in GNOME Overview (if you are using gnome-software from the repository) that the application has been successfully removed. * Perform additional testing such as installing applications from the repository (change the source to "Ubuntu (deb)") and then deleting the application. * Perform additional testing such as installing applications from the snap repository (change the source to "Snap") and then deleting the application. [Where problems could occur] * The code changed is specific to 'packagekit' repos i.e. debian based repos. Thus it is sensitive to possible regressions when installing & removing apps. * The patch itself is well tested since it was backported to the ubuntu snap-store several weeks ago and has been rolled out. No adverse issues has been reported. * The risk would be that there could be additional changes to the snap-store that was not incorporated in gnome-software possibly producing different results. * The additional regression tests in the Test Plan will reveal this. [Other Info] * There is no need to backport this to Kinetic since a revised version of the patch has been upstreamed (GNOME Team) and is in the kinetic version. On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1982564] [NEW] Shotwell Piwigo plugin does not upload
Public bug reported:
Trying to upload photo to Piwigo via Shotwell plugin I got and error
like "URL not valid" (I got it in Italian).
Looking at Piwigo side I found this php error:
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Deprecated: substr(): Passing null to
parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Deprecated: substr(): Passing null to
parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
I think both Shotwell and Piwigo are updated to latest version:
Shotwell: 0.30.14 – “Celle”
Piwigo 12.3.0
Operating System: Linux
PHP: 8.1.2
MySQL: 5.5.5-10.6.7-MariaDB-2ubuntu1.1
Grafic Lib: GD 2.3.0
** Affects: shotwell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1982564
Title:
Shotwell Piwigo plugin does not upload
Status in shotwell package in Ubuntu:
New
Bug description:
Trying to upload photo to Piwigo via Shotwell plugin I got and error
like "URL not valid" (I got it in Italian).
Looking at Piwigo side I found this php error:
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Deprecated: substr(): Passing null
to parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Deprecated: substr(): Passing null
to parameter #1 ($string) of type string is deprecated in
/var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Fatal error: Uncaught TypeError:
get_class(): Argument #1 ($object) must be of type object, bool given in
/var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289):
PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42):
PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281):
PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
I think both Shotwell and Piwigo are updated to latest version:
Shotwell: 0.30.14 – “Celle”
Piwigo 12.3.0
Operating System: Linux
PHP: 8.1.2
MySQL: 5.5.5-10.6.7-MariaDB-2ubuntu1.1
Grafic Lib: GD 2.3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1982564/+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 1982551] Re: Print is failed via USB
Yes, this problem is happened with multiple printers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS ErrorLog, the job has been delivered completely.
(refer to error_log->[Job 313])
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
D [21/Jul/2022:15:21:17 +0800] [Job 313]
I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
[Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
(refer to usb2.pcapng, snapshot.pn)
4.We extracted the accepted data on the printer side, the data is really lost.
(refer to prt00016.prn,
prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] Re: Print is failed via USB
I added back the "Our analysis" section from the old bug report since it
has a wealth of useful debugging data. Thank you for going to so much
trouble to make this report, all that debugging you did may prove
extremely useful.
** Description changed:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
+
+ Our analysis:
+ 1.We think that part of the data was lost via USB transmission
+
+ 2.In CUPS ErrorLog, the job has been delivered completely.
+ (refer to error_log->[Job 313])
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
+ D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
+ D [21/Jul/2022:15:21:17 +0800] [Job 313]
+
+ I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
+
+ 3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
+ [Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
+ (refer to usb2.pcapng, snapshot.pn)
+
+ 4.We extracted the accepted data on the printer side, the data is really lost.
+ (refer to prt00016.prn,
+ prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS
[Desktop-packages] [Bug 1982551] Re: Print is failed via USB
** Description changed:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
- 4.The problem does not occur viai network.
- 5.Other systems (such as Windows, Mac OS) do not have this problem.
+ 4.Other systems (such as Windows, Mac OS) do not have this problem.
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS ErrorLog, the job has been delivered completely.
(refer to error_log->[Job 313])
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
D [21/Jul/2022:15:21:17 +0800] [Job 313]
I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
[Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
(refer to usb2.pcapng, snapshot.pn)
4.We extracted the accepted data on the printer side, the data is really lost.
(refer to prt00016.prn,
prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
[Desktop-packages] [Bug 1982551] Re: Print is failed via USB
And it's happening with multiple printers as well? (Asking to narrow
down where the problem might be)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS ErrorLog, the job has been delivered completely.
(refer to error_log->[Job 313])
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
D [21/Jul/2022:15:21:17 +0800] [Job 313]
I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
[Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
(refer to usb2.pcapng, snapshot.pn)
4.We extracted the accepted data on the printer side, the data is really lost.
(refer to prt00016.prn,
prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] Re: Print is failed via USB
Yes, it is related to https://bugs.launchpad.net/ubuntu/+bug/1982531.
And I tried some other USB cables, the problem is still happened.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS ErrorLog, the job has been delivered completely.
(refer to error_log->[Job 313])
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
D [21/Jul/2022:15:21:17 +0800] [Job 313]
I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
[Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
(refer to usb2.pcapng, snapshot.pn)
4.We extracted the accepted data on the printer side, the data is really lost.
(refer to prt00016.prn,
prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] Re: Print is failed via USB
This may sound silly, but try a different USB cable between your printer and the system. That will help rule out a USB cable problem. (Even though Windows and macOS don't have this problem, there's still a chance that the USB cable is at fault.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1982551 Title: Print is failed via USB Status in cups package in Ubuntu: New Bug description: Phenomenon: After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it can be printed at the first time, but after the second or multiple times, the job will be canceled. Comment: 1.Wait a few minutes and the job still won't be printed. 2.After unplugging in and plugging in the USB cable, the job can be printed 3.The problem does not occur via network printing. 4.Other systems (such as Windows, Mac OS) do not have this problem. Description: Ubuntu 18.04.5 LTS Release: 18.04 CUPS 2.2.7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 15:43:30 2022 InstallationDate: Installed on 2022-07-05 (16 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. OptiPlex 3010 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] Re: Print is failed via USB
Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this report related to https://bugs.launchpad.net/ubuntu/+bug/1982531 ? (this report is the better one, having apport data on it) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1982551 Title: Print is failed via USB Status in cups package in Ubuntu: New Bug description: Phenomenon: After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it can be printed at the first time, but after the second or multiple times, the job will be canceled. Comment: 1.Wait a few minutes and the job still won't be printed. 2.After unplugging in and plugging in the USB cable, the job can be printed 3.The problem does not occur via network printing. 4.Other systems (such as Windows, Mac OS) do not have this problem. Description: Ubuntu 18.04.5 LTS Release: 18.04 CUPS 2.2.7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 15:43:30 2022 InstallationDate: Installed on 2022-07-05 (16 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. OptiPlex 3010 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] [NEW] Print is failed via USB
Public bug reported: Phenomenon: After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it can be printed at the first time, but after the second or multiple times, the job will be canceled. Comment: 1.Wait a few minutes and the job still won't be printed. 2.After unplugging in and plugging in the USB cable, the job can be printed 3.The problem does not occur via network printing. 4.The problem does not occur viai network. 5.Other systems (such as Windows, Mac OS) do not have this problem. Description:Ubuntu 18.04.5 LTS Release:18.04 CUPS 2.2.7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 15:43:30 2022 InstallationDate: Installed on 2022-07-05 (16 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. OptiPlex 3010 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1982551 Title: Print is failed via USB Status in cups package in Ubuntu: New Bug description: Phenomenon: After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it can be printed at the first time, but after the second or multiple times, the job will be canceled. Comment: 1.Wait a few minutes and the job still won't be printed. 2.After unplugging in and plugging in the USB cable, the job can be printed 3.The problem does not occur via network printing. 4.The problem does not occur viai network. 5.Other systems (such as Windows, Mac OS) do not have this problem. Description: Ubuntu 18.04.5 LTS Release: 18.04 CUPS 2.2.7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 15:43:30 2022 InstallationDate: Installed on 2022-07-05 (16 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. OptiPlex 3010 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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
