[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Changed in: xorg-server (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Jammy) Status: New => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: xserver-xorg-video-nouveau (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Given that other fixes are not as straight forward as I thought, I've uploaded it as it is for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in Dash to dock: Fix Released Status in ubuntu-dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: [Impact] If the dock is set to auto-hide and a window is under the dock, then the dock hides prematurely when a menu is opened from one of its icons. This only seems to happen with GNOME 42. [Test Plan] 1. Set the dock to auto hide. 2. Move a window under the dock's position so that it wants to auto-hide. 3. Open the dock and right click on one of the icons to open a menu. Expected: Dock stays open while the menu is open. Observed: Dock closes while the menu is open. [Where problems could occur] This fix may affect any scenarios relating to the dock auto-hiding. [Other Info] Upstream fixes: ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739 dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1970206] Re: Cursor goes missing in games
[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/1970206 Title: Cursor goes missing in games Status in gnome-shell package in Ubuntu: Expired Bug description: Unable to play any games in Full screen mode like 0AD or Kingdom Rush (steam) which involve a custom cursor. MOnitor is Acer T231 (Touchscreen monitor) Hardware is B68 motherboard with Athlon processor. I wonder if it has to do with Wayland and full screen games. With the cursor going invisible it is impossible to play the games. have to exit the games to get back the cursor. Effectively cannot play games at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970206/+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 1971429] Re: gnome shell
[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/1971429 Title: gnome shell Status in gnome-shell package in Ubuntu: Expired Bug description: gjs show all time on bar menu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 3 09:50:23 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-27 (5 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971429/+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 1971704] Re: Wayland/Gnome Shell freezes when Android phone is connected
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1971704 Title: Wayland/Gnome Shell freezes when Android phone is connected Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: I got occasional freeze on new Ubuntu 22.04 LTS. The machine is Lenovo 7/8th gen Carbon with 10th gen Intel. But after the latest freeze and reboot (because of the freeze) I logged in and then it freezes everytime, propably when loading gnome setting, I see the icon emerging on the dock and freezing. Just before the freeze there was kernel and some packages upgrade) The report is from previous kernel which I thought it was culprit but it seems not. I can login to the machine with SSH therefore I produced this report. There"s process getting 100% of 1 cpu core: gnome-shell After a while it blanks (as schedules) to login manager and I can login back and same story. I see following error in syslog May 5 14:02:13 graf gnome-shell[1740]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed May 5 14:02:13 graf gnome-shell[1740]: cr_declaration_parse_list_from_buf: assertion 'parser' failed May 5 14:02:13 graf gnome-shell[1740]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed May 5 14:02:13 graf gnome-shell[1740]: cr_declaration_parse_list_from_buf: assertion 'parser' failed May 5 14:02:13 graf gnome-shell[1740]: ATK Bridge is disabled but a11y has already been enabled. May 5 14:02:14 graf gnome-shell[1740]: Registering session with GDM May 5 14:02:17 graf gnome-shell[1740]: Could not open device /dev/input/event17: Could not get device info for path /dev/input/event17: No such file or directory May 5 14:02:17 graf gnome-shell[1740]: Could not open device /dev/input/event16: GDBus.Error:System.Error.ENODEV: No such device May 5 14:02:19 graf gnome-shell[1740]: Removing a network device that was not added May 5 14:02:19 graf gnome-shell[1740]: Removing a network device that was not added May 5 14:02:27 graf gnome-shell[3287]: Running GNOME Shell (using mutter 42.0) as a Wayland display server May 5 14:02:27 graf gnome-shell[3287]: Device '/dev/dri/card0' prefers shadow buffer May 5 14:02:27 graf gnome-shell[3287]: Added device '/dev/dri/card0' (i915) using atomic mode setting. May 5 14:02:27 graf gnome-shell[3287]: Created gbm renderer for '/dev/dri/card0' May 5 14:02:27 graf gnome-shell[3287]: Boot VGA GPU /dev/dri/card0 selected as primary May 5 14:02:27 graf gnome-shell[3287]: Using public X11 display :0, (using :1 for managed services) May 5 14:02:27 graf gnome-shell[3287]: Using Wayland display name 'wayland-0' May 5 14:02:27 graf gnome-shell[3287]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. May 5 14:02:27 graf gnome-shell[3287]: Will monitor session 2 May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.39' (uid=1000 pid=3334 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") May 5 14:02:27 graf gnome-shell[3287]: Telepathy is not available, chat integration will be disabled. May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.39' (uid=1000 pid=3334 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.freedesktop.FileManager1' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:28 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.gnome.Shell.Notifications' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:28 graf at-spi-dbus-bus.desktop[3293]: dbus-daemon[3293]: Activating service name='org.a11y.atspi.Registry' requested
[Desktop-packages] [Bug 1972004] Re: Dock follows primary display scaling for all displays
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1972004 Title: Dock follows primary display scaling for all displays Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: This bug seems like #1826543, but I fled a new one because it is a regression from 21.10. While writing this, I also noticed that other elements only follow the primary display scaling, like the numbers on the top left that say which display is which, and the pop-up that asks whether I want to keep the new display settings, so I might have filed this bug in the wrong package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-29.30-generic 5.15.35 Uname: Linux 5.15.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 6 13:21:52 2022 InstallationDate: Installed on 2021-09-13 (235 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210912) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to jammy on 2022-03-31 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972004/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
I seem to be having similar issues. I could connect my android phone for a bit then it just kinda stopped. My Ipad has never been able to join the network. sometimes with an error saying the channel is too busy (fixed that by starting with nmcli and selecting another channel). Otherwise, the Ipad gives the error "unable to join network" (A nice helpful message, thanks apple) All devices can connect to other networks (android hotstpot and wifi router) I've attached my log file if it'll be any help This might be the wrong place to post, but it was the most recent relevant bug report. ** Attachment added: "My Journalctl log file" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5601989/+files/log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
Can you please provide the output of journalctl /usr/bin/gnome-shell When this happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979096/+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 1969838] Re: Ubuntu-dock does not work when using Turkish Language
** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969838 Title: Ubuntu-dock does not work when using Turkish Language Status in Dash to dock: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in gjs source package in Jammy: Fix Released Bug description: [ Impact ] Ubuntu dock doesn't work when Turkish language is selected. Issue on dash-to-dock's github: https://github.com/micheleg/dash-to-dock/issues/1687 Ubuntu version: Ubuntu 22.04 LTS gnome-shell-extension-ubuntu-dock version: 72~ubuntu5 [ Test case ] - Run ubuntu session - Ubuntu dock should be visible on a screen edge Alternatively: Save this test case in a file (i.e. /tmp/test.js): const { GLib, GObject } = imports.gi; const ImplicitProp = GObject.registerClass({ Properties: { "prop-int": GObject.ParamSpec.uint( "prop-int", "prop-int", "prop-int", GObject.ParamFlags.READWRITE | GObject.ParamFlags.CONSTRUCT_ONLY, 0, GLib.MAXUINT32, 55), }, }, class DashToDock extends GObject.Object { }); if (new ImplicitProp().propInt === undefined) throw new Error("Missing property") print('All good'); In a terminal run: LC_ALL=tr_TR gjs /tmp/test.js The script should work without throwing any error. [ Regression potential ] Implicit properties on GJS may be wrongly computed, and further objects could have undefined properties. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969838/+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 1981025] Re: Firefox SNAP update removes icon from desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1981025 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1981025 Title: Firefox SNAP update removes icon from desktop Status in firefox package in Ubuntu: New Bug description: Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the desktop icon disappearing, because the firefox_firefox.desktop file "icon=" line then points to a now non-existent directory. https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop- icon-disappeared-after-update/3445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981025/+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 1981025] [NEW] Firefox SNAP update removes icon from desktop
Public bug reported: Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the desktop icon disappearing, because the firefox_firefox.desktop file "icon=" line then points to a now non-existent directory. https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop- icon-disappeared-after-update/3445 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1981025 Title: Firefox SNAP update removes icon from desktop Status in firefox package in Ubuntu: New Bug description: Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the desktop icon disappearing, because the firefox_firefox.desktop file "icon=" line then points to a now non-existent directory. https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop- icon-disappeared-after-update/3445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981025/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
With evince 42.3-0ubuntu2 and apparmor 3.0.4-2ubuntu2.1 on cinnamon 5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish) : - The 'at-spi/bus' issue is fixed. - The print issue is NOT fixed yet, but Karsten's workaround inside apparmor still works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1970408] Re: brltty package disconnecting ttyUSB0 used for Arduino
*** This bug is a duplicate of bug 1958224 *** https://bugs.launchpad.net/bugs/1958224 There is one now in the main bug report: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1970408 Title: brltty package disconnecting ttyUSB0 used for Arduino Status in brltty package in Ubuntu: Confirmed Bug description: Hello I connected an ESP8266 microcontroller to my pc to use with Arduino. However, the interface didn't appears to list ttyUSB0. Upon inspection with dmesg, I noticed that the device is recognised but then brltty appears to disconnect it. [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [Tue Apr 26 19:09:35 2022] usb 1-8: Product: CP2102 USB to UART Bridge Controller [Tue Apr 26 19:09:35 2022] usb 1-8: Manufacturer: Silicon Labs [Tue Apr 26 19:09:35 2022] usb 1-8: SerialNumber: 0001 [Tue Apr 26 19:09:35 2022] cp210x 1-8:1.0: cp210x converter detected [Tue Apr 26 19:09:35 2022] usb 1-8: cp210x converter now attached to ttyUSB0 [Tue Apr 26 19:09:38 2022] usb 1-8: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [Tue Apr 26 19:09:38 2022] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [Tue Apr 26 19:09:38 2022] cp210x 1-8:1.0: device disconnected This also appears to have happended to other people: https://stackoverflow.com/questions/52143723/usb-serial-loses- connection-immediately-in-new-linux-kernel-4-12-14 Once the brltty package is removed, the USB device mounts fine and Arduino find it (same dmesg as above, without the last 3 lines). I'm actually not sure why this package is installed as I deleted it without having to remove ubuntu-desktop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 19:15:04 2022 InstallationDate: Installed on 2022-04-06 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: brltty UpgradeStatus: Upgraded to jammy on 2022-04-18 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970408/+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 1980908] Re: duplicity does NOT close properly
- version number of duplicity and deja-dup: duplicity 0.8.22, deja-dup 42.9 - Python version running: 3.10.4 - OS version: 22.04, 5.15.0-40-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: New Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
The latest: https://launchpad.net/~nteodosio/+snap/chromium-browser- hwacc/+build/1814664 From the code, there is only video log parts change, so the result won't change. I run on my T460p, the result is the same. How could I let the video log display? I am sure the T460P and N3450 machine, the video decode type is the ffmpeg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the snap with sudo snap install --channel candidate/hwacc chromium 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples 4. Enter about:media-internals in the address bar and note what the page says for kVideoDecoderName. Please report - The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder; - If failed, the video used for testing, including codec and resolution if possible; - Distro version (if in doubt, `grep VERSION= /etc/os_release`); - GPU (if in doubt, attach the output of `lscpu`); - CPU generation (if in doubt, attach the output of `lscpu`). About the last point, it may be that unfortunately only those with newer generations of Intel CPUs will have luck with this, but it's still an uncertainty. So reports are highly welcome. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1980989] Re: Create Archive's archive format list is cut off
Thank you for your bug report, the issue is fixed in https://launchpad.net/ubuntu/+source/nautilus/1:42.1.1-0ubuntu1 and newer version, you should install stable updates ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1980989 Title: Create Archive's archive format list is cut off Status in nautilus package in Ubuntu: Fix Released Bug description: When compressing an element from Files, and clicking the archive extension button, a list of 4 formats appear. The list supposedly displays the format's name and description. But in my case, the leftmost part is cut off, thus preventing to read what formats are available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 20:06:35 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 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/1980989/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
This bug was fixed in the package xserver-xorg-video-amdgpu - 22.0.0-2 --- xserver-xorg-video-amdgpu (22.0.0-2) unstable; urgency=medium * Added patches from git to fix slow refresh rate with Displaylink output. (LP: #1875015) -- Timo Aaltonen Thu, 07 Jul 2022 11:29:03 +0300 ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: New Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1980989] [NEW] Create Archive's archive format list is cut off
Public bug reported: When compressing an element from Files, and clicking the archive extension button, a list of 4 formats appear. The list supposedly displays the format's name and description. But in my case, the leftmost part is cut off, thus preventing to read what formats are available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 20:06:35 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 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 from 2022-07-07 20-27-23.png" https://bugs.launchpad.net/bugs/1980989/+attachment/5601910/+files/Screenshot%20from%202022-07-07%2020-27-23.png -- 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/1980989 Title: Create Archive's archive format list is cut off Status in nautilus package in Ubuntu: New Bug description: When compressing an element from Files, and clicking the archive extension button, a list of 4 formats appear. The list supposedly displays the format's name and description. But in my case, the leftmost part is cut off, thus preventing to read what formats are available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 20:06:35 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 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/1980989/+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 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
Tested with nvidia-graphics-drivers-515 and the problem persists. -- 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/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970291/+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 1980975] [NEW] Rubbish Bin Context Menu references wrong name
Public bug reported: When right clicking the rubbish bin in the file explorer or dock, the context menu says "Empty wastebasket". This is an inconsistent reference as it is now referred to as Rubbish Bin across the Ubuntu OS. Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip describes "Delete all items in the Rubbish Bin". ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-07-07 17-42-53.png" https://bugs.launchpad.net/bugs/1980975/+attachment/5601876/+files/Screenshot%20from%202022-07-07%2017-42-53.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1980975 Title: Rubbish Bin Context Menu references wrong name Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When right clicking the rubbish bin in the file explorer or dock, the context menu says "Empty wastebasket". This is an inconsistent reference as it is now referred to as Rubbish Bin across the Ubuntu OS. Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip describes "Delete all items in the Rubbish Bin". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1980975/+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 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
I don't know if it's the same situation for me, but it might be. On my work laptop I recently upgraded from Ubuntu 20.04 to 22.04, and the mouse focus follow function (or whatever it's called) has changed in this LTS upgrade. For me this is specifically when I close an application/window. I have it set so focus automatically switches to where the mouse is over top, but to NOT bring any window forward (over top of others) when the focus changes, which is the desired state. Let's say I have on one monitor Vivaldi (browser) maximised, and I have two text editor windows overlapping each other but are only windows that take up a portion of the screen. Text Editor 1 is "on top" of Text Editor 2, and both of these Text Editor windows are "on top" of Vivaldi, in terms of the stack of view (or whatever it is called). On Ubuntu 20.04: If I were to close Text Editor 1, then Text Editor 2 would be on top, and if my mouse is over top of it Text Editor 2 would have focus, and still be on top of Vivaldi. If my mouse is not over top of Text Editor 2 after closing Text Editor 1, then Text Editor 2 may not be focused, however it is _still_ over top of Vivaldi and Text Editor 2 is still visible. This is the desired outcome. On Ubuntu 22.04 If I were to close Text Editor 1, then Text Editor 2 would immediately be moved behind Vivaldi, unless my mouse was over top of Text Editor 2 when closing Text Editor 1, which is often not the case. This is _not_ the desired outcome. To put it another way, it looks like when closing a window the check related to mouse focus immediately is performed, however in 22.04 it brings whatever window it is hovering over to the very front, which is not desired nor how it is configured to behave. Again, in 20.04 this change of window stacking did not happen with the exact same settings, and it happens in 22.04. I rely on focus shifting tied to my mouse (without windows being pulled forward) as a key part of my high-performance workflow. So this change in outcome actually makes my workflow less efficient as I need to bring one or multiple windows back in-front when this forces windows behind others in ways that it shouldn't. I'm unsure if this is related to the original bug, but for me this really does need to be fixed. -- 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/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1980908] Re: duplicity does NOT close properly
Please provide some more info: - version number of duplicity and deja-dup - Python version running - OS version Also, how did you exit deja-dup? Clean exit or task killed? ** Also affects: duplicity Importance: Undecided Status: New ** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: New Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+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 1980873] Re: New release 103.0.5060.53 for Bionic
The update is ready and pending sponsoring from the Ubuntu security team. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1980873 Title: New release 103.0.5060.53 for Bionic Status in chromium-browser package in Ubuntu: Fix Committed Bug description: A new upstream release 103.0.5060.53 is available. Debian released a security advisory on June 22. Please package it for Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1980873/+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 1980873] Re: New release 103.0.5060.53 for Bionic
** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1980873 Title: New release 103.0.5060.53 for Bionic Status in chromium-browser package in Ubuntu: Confirmed Bug description: A new upstream release 103.0.5060.53 is available. Debian released a security advisory on June 22. Please package it for Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1980873/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
OK, I'm now on site ... and it works here is the journal log thanks for the efforts of the team ** Attachment added: "journal log" https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5601872/+files/journal.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1980545] Re: Update evolution-data-server to 3.44.3
Merge request for ubuntu/jammy proposed at Salsa: https://salsa.debian.org/gnome-team/evolution-data- server/-/merge_requests/6 Please note that, for Gmail, I could not get the Google Authentication Request to work and thus could not access my mail. After allowing Evolution access, it gets stuck in "Requesting access token, please wait...". However, that is both for 3.44.2-0ubuntu1 and 3.44.3-0ubuntu1, so this is not a problem introduced by the latter, and other accounts such as Microsoft's work fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1980545 Title: Update evolution-data-server to 3.44.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.3/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+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 1980545] Re: Update evolution-data-server to 3.44.3
** Changed in: evolution-data-server (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1980545 Title: Update evolution-data-server to 3.44.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.3/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+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 1803604] Re: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work
** Changed in: df-libreoffice Status: Confirmed => Incomplete -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1748895] Re: LO unable to find a working email configuration
** Changed in: df-libreoffice Status: Confirmed => Incomplete -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1748895]
This would be a duplicate of bug 74067 with similar problem in bug 75825. Or we may regard this one for sending attachment and other one for warning. That one lists commit 8e7a3669dd86f86325b3012abc657b5d4665374d titled Combine senddoc null and default cases for better mailer selection. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
I tested sending with claws-email now, previously I used mutt, and all is working, composer window is invoked and file is attached. I understood this bug was about claws-email but if not it needs a precision. "xdg-email is a command line tool for sending mail using the user's preferred e-mail composer" so why would it be used in Tools/Options/Internet/Email I don't know. My understanding is that it's working implicitly, if you don't set Email than xdg-email is used to invoke some (from Default/Preferred Applications). In my case, when I deleted claws-email path from Email and not from the system, it used mutt. But I got no screen prompts for the setting of Tools-Options-Internet-Email? Please paste screenshot here. Mail from mutt was composed and sent but without attachment. I then changed system mail to claws-email and xdg-email invoked claws-email but without composer window. So for me, bug is that xdg-email doesn't attach file or compose mail, seen when when having Email empty ie. relying on xdg-email. Mine is version 1.1.2 from Ubuntu 18.04. But it should be that Ubuntu bug. And there "xdg-utils 1.1.3-4.1ubuntu1.22.04.1 seems to have fixed this". (1) seems Ubuntu bug. (2) I wrote my view on xdg-utils (3) I asked you to clarify, to have all here, but that would be another issue anyway. -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1748895]
Oh, not really well in Ubuntu 22.04. Lo has sensible-lomua set in Email (don't know what's that, probably ends with xdg-email anyway) but behaves like when empty, invoking default mail which I set to be claws-mail. Also program window invoked, not composer window. xdg-email is 1.1.3-4.1. So that would be the same, not resolved. Another new problem: if I set Email to /usr/bin/claws-mail, I get a message "LO unable to find a working mail configuration". claws-mail is version 4.0 If system has no default email client, sending with LO doesn't give any warning. That would be another issue, related to (3). -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
This would be a duplicate of bug 74067 with similar problem in bug 75825. Or we may regard this one for sending attachment and other one for warning. That one lists commit 8e7a3669dd86f86325b3012abc657b5d4665374d titled Combine senddoc null and default cases for better mailer selection. -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1748895]
I tested sending with claws-email now, previously I used mutt, and all is working, composer window is invoked and file is attached. I understood this bug was about claws-email but if not it needs a precision. "xdg-email is a command line tool for sending mail using the user's preferred e-mail composer" so why would it be used in Tools/Options/Internet/Email I don't know. My understanding is that it's working implicitly, if you don't set Email than xdg-email is used to invoke some (from Default/Preferred Applications). In my case, when I deleted claws-email path from Email and not from the system, it used mutt. But I got no screen prompts for the setting of Tools-Options-Internet-Email? Please paste screenshot here. Mail from mutt was composed and sent but without attachment. I then changed system mail to claws-email and xdg-email invoked claws-email but without composer window. So for me, bug is that xdg-email doesn't attach file or compose mail, seen when when having Email empty ie. relying on xdg-email. Mine is version 1.1.2 from Ubuntu 18.04. But it should be that Ubuntu bug. And there "xdg-utils 1.1.3-4.1ubuntu1.22.04.1 seems to have fixed this". (1) seems Ubuntu bug. (2) I wrote my view on xdg-utils (3) I asked you to clarify, to have all here, but that would be another issue anyway. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1748895]
There are 3 levels at which this is an LO bug: (1) senddoc provides settings for claws-mail (claws|sylpheed), which work fine, EXCEPT that since apparmor was enforced, these settings only work if claws-mail is included in the apparmor settings (2) xdg-email is seen as the default email application, but the coding in senddoc uses the 'mailto:' command format. The manual for xdg-email is explicit "xdg-email limits support to, cc, subject and body fields in mailto-uri, all other fields are silently ignored." This makes xdg-email with mailto: command format a bad choice for LO's senddoc. If the alternative command-line-style were used, with simple email addresses rather than the mailto: style, I think all would be well. It certainly works well for me from the command line. (3) the screen prompts for the setting of Tools-Options-Internet-Email are not helpful. Perhaps they couldn't be until senddoc works dependably for all reasonable email clients. Evolution, kmail, icedove, and thunderbird are given specific entries in senddoc; I don;t know how well they work - but all other clients must be a potential problem. The implication in this user configuration setting is that any email application should work. That simply is not so. I agree with Timur (#27) that a main problem in in xdg-email, but I can find no indication that its maintainers are likely to extend the capabilities of the mailto: option. In the meantime, however, LO could and should use the command option that does the essential job of attaching the document to the email. And then improve the Tools-Options email entry screen. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1748895]
Reading this, I don't see it as LO bug. And it well may be NotOurBug. I restrict to claws-mail and kindly ask reporter to follow up with new version. Since Ubuntu bug is listed, this can simply be closed. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
Oh, not really well in Ubuntu 22.04. Lo has sensible-lomua set in Email (don't know what's that, probably ends with xdg-email anyway) but behaves like when empty, invoking default mail which I set to be claws-mail. Also program window invoked, not composer window. xdg-email is 1.1.3-4.1. So that would be the same, not resolved. Another new problem: if I set Email to /usr/bin/claws-mail, I get a message "LO unable to find a working mail configuration". claws-mail is version 4.0 If system has no default email client, sending with LO doesn't give any warning. That would be another issue, related to (3). -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1803604]
Reading this, I don't see it as LO bug. And it well may be NotOurBug. I restrict to claws-mail and kindly ask reporter to follow up with new version. Since Ubuntu bug is listed, this can simply be closed. -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1803604]
There are 3 levels at which this is an LO bug: (1) senddoc provides settings for claws-mail (claws|sylpheed), which work fine, EXCEPT that since apparmor was enforced, these settings only work if claws-mail is included in the apparmor settings (2) xdg-email is seen as the default email application, but the coding in senddoc uses the 'mailto:' command format. The manual for xdg-email is explicit "xdg-email limits support to, cc, subject and body fields in mailto-uri, all other fields are silently ignored." This makes xdg-email with mailto: command format a bad choice for LO's senddoc. If the alternative command-line-style were used, with simple email addresses rather than the mailto: style, I think all would be well. It certainly works well for me from the command line. (3) the screen prompts for the setting of Tools-Options-Internet-Email are not helpful. Perhaps they couldn't be until senddoc works dependably for all reasonable email clients. Evolution, kmail, icedove, and thunderbird are given specific entries in senddoc; I don;t know how well they work - but all other clients must be a potential problem. The implication in this user configuration setting is that any email application should work. That simply is not so. I agree with Timur (#27) that a main problem in in xdg-email, but I can find no indication that its maintainers are likely to extend the capabilities of the mailto: option. In the meantime, however, LO could and should use the command option that does the essential job of attaching the document to the email. And then improve the Tools-Options email entry screen. -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1980748] Re: Update gnome-remote-desktop to 42.3
Merge request opened in Salsa for ubuntu/jammy: https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/merge_requests/4 I followed the test cases both for the current version (42.2-0ubuntu1) and the proposed one (42.3-0ubuntu1). I also logged out and in again after installing the .deb for 42.3-0ubuntu1. The only thing that didn't work was using the "user@192.168.1.1" notation in Remmina, whereas giving it just the IP address, "192.168.1.1", did work. So please drop the user name if you encounter this issue. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1980748 Title: Update gnome-remote-desktop to 42.3 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1980748/+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 1980806] Re: New release 91.11.0
** Also affects: thunderbird (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: thunderbird (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: thunderbird (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: thunderbird (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: thunderbird (Ubuntu Bionic) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu Impish) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu Jammy) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu Bionic) Status: New => In Progress ** Changed in: thunderbird (Ubuntu Focal) Status: New => In Progress ** Changed in: thunderbird (Ubuntu Impish) Status: New => In Progress ** Changed in: thunderbird (Ubuntu Jammy) Status: New => In Progress ** Changed in: thunderbird (Ubuntu) Importance: Wishlist => High ** Changed in: thunderbird (Ubuntu Bionic) Importance: Undecided => High ** Changed in: thunderbird (Ubuntu Focal) Importance: Undecided => High ** Changed in: thunderbird (Ubuntu Impish) Importance: Undecided => High ** Changed in: thunderbird (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980806 Title: New release 91.11.0 Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: In Progress Status in thunderbird source package in Focal: In Progress Status in thunderbird source package in Impish: In Progress Status in thunderbird source package in Jammy: In Progress Bug description: Thunderbird 91.11.0 has been released, and fixes many CVEs when compared with the version currently in the Ubuntu releases under standard support (91.9.1). Please package this version to all Ubuntu releases under standard support. Debian has released a security advisory on July 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980806/+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 1980804] Re: New bugfix release 22.0.5
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980804 Title: New bugfix release 22.0.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] This is the last point-release of the 22.0.x-series, we should put it in jammy so latest bugfixes would get there, and in focal for 20.04.5 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980804/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
I don't know how this might help, but I followed the instructions to download and un-squash the version 102.0.1 of thunderbird to my home folder, cd'd into the squashfs-root folder and ran thunderbird using ./thunderbird -p which picked up my current profile from the ~/.thunderbird directory. >From another terminal window and within the same squashfs-root directory, I >can successfully run ./thunderbird --compose which then brings up a compose >window whilst thunderbird itself is still running. Make sure that you make a backup of the ~/.thunderbird folder first, running the latest version of thunderbird alters the profile. Does this add further info to the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: New Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 114928] Re: Problem with special characters?
For the 15th birthday of this bug ;-) I don't use PPTP in my server installations anymore - not only, but also due to this bug. Therefore I can't provide an upstream bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/114928 Title: Problem with special characters? Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-pptp Hi! I try to connect to a Win 2003 server via PPTP VPN with Networkmanager (gnome). It works with pptpconfig but not with NM. Syslog: May 16 00:58:54 andreas-laptop pptp[7183]: anon warn[ctrlp_disp:pptp_ctrl.c:955]: Non-zero Async Control Character Maps are not supported! May 16 00:58:54 andreas-laptop pppd[7178]: nm-pppd-plugin: CHAP credentials requested. May 16 00:58:54 andreas-laptop pppd[7178]: MS-CHAP authentication failed: E=691 Authentication failure May 16 00:58:54 andreas-laptop pppd[7178]: CHAP authentication failed I had to write the password in quotation marks in pptpconfig as it contains special characters like &%$. I tried it with "" and without it in NM. But it doesn't work - so NM is not good for strong passwords??? Anyone confirm this issue? Regards, Andreas Weller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/114928/+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 1980936] [NEW] Flatpaked apps doesn't start under wayland, if called from another app
Public bug reported: I run Gnome Wayland session and I have several apps installed from flatpak - gthumb and evince are among them. If I download a file using a web-browser and try to open this file from the browser's "download" menu, the PDF or JPG files won't open. I can fix it by setting up evince or gthumb to run x11 by disabling wayland with flatseal. Web-browser is not installed by a flatpak or snap, so it can be vivaldi or yandex-browser. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 12:09:43 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-06-08 (28 days ago) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1980936 Title: Flatpaked apps doesn't start under wayland, if called from another app Status in flatpak package in Ubuntu: New Bug description: I run Gnome Wayland session and I have several apps installed from flatpak - gthumb and evince are among them. If I download a file using a web-browser and try to open this file from the browser's "download" menu, the PDF or JPG files won't open. I can fix it by setting up evince or gthumb to run x11 by disabling wayland with flatseal. Web-browser is not installed by a flatpak or snap, so it can be vivaldi or yandex-browser. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 12:09:43 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-06-08 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1980936/+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 1980937] [NEW] [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Public bug reported: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: New Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubu
[Desktop-packages] [Bug 1980933] Re: Blanked screen doesn't wake up after put into powersave
Out of the system journal I think these are the smoking guns: Jul 06 23:14:20 Excelsior kernel: INFO: task firefox:cs0:6721 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:firefox:cs0 state:D stack:0 pid: 6721 ppid: 3462 flags:0x0220 Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_timeout+0xfb/0x140 Jul 06 23:14:20 Excelsior kernel: ? __wake_up_locked+0x16/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_default_wait+0x1c4/0x1f0 Jul 06 23:14:20 Excelsior kernel: ? dma_fence_free+0x20/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_wait_timeout+0xb7/0xd0 Jul 06 23:14:20 Excelsior kernel: gmc_v10_0_flush_gpu_tlb+0x285/0x310 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_gart_invalidate_tlb+0x43/0x60 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_ttm_alloc_gart+0x150/0x1a0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_parser_bos+0x406/0x4e0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_ib_fill+0x1e3/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_ioctl+0xf8/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_ioctl_kernel+0xae/0xf0 [drm] Jul 06 23:14:20 Excelsior kernel: drm_ioctl+0x264/0x4b0 [drm] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? __seccomp_filter+0x4a/0x4a0 Jul 06 23:14:20 Excelsior kernel: amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Jul 06 23:14:20 Excelsior kernel: __x64_sys_ioctl+0x91/0xc0 Jul 06 23:14:20 Excelsior kernel: do_syscall_64+0x5c/0xc0 Jul 06 23:14:20 Excelsior kernel: ? exit_to_user_mode_prepare+0x92/0xb0 Jul 06 23:14:20 Excelsior kernel: ? syscall_exit_to_user_mode+0x27/0x50 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jul 06 23:14:20 Excelsior kernel: RIP: 0033:0x7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RSP: 002b:7fa95f32fa18 EFLAGS: 0246 ORIG_RAX: 0010 Jul 06 23:14:20 Excelsior kernel: RAX: ffda RBX: 7fa95f32fa80 RCX: 7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RDX: 7fa95f32fa80 RSI: c0186444 RDI: 0026 Jul 06 23:14:20 Excelsior kernel: RBP: c0186444 R08: 7fa95f32fbb0 R09: 0020 Jul 06 23:14:20 Excelsior kernel: R10: 7fa95f32fbb0 R11: 0246 R12: 7fa969dd7e00 Jul 06 23:14:20 Excelsior kernel: R13: 0026 R14: R15: 7fa916022090 Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: INFO: task kworker/13:0:20618 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:kworker/13:0state:D stack:0 pid:20618 ppid: 2 flags:0x4000 Jul 06 23:14:20 Excelsior kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_preempt_disabled+0xe/0x10 Jul 06 23:14:20 Excelsior kernel: __mutex_lock.constprop.0+0x263/0x490 Jul 06 23:14:20 Excelsior kernel: __mutex_lock_slowpath+0x13/0x20 Jul 06 23:14:20 Excelsior kernel: mutex_lock+0x34/0x40 Jul 06 23:14:20 Excelsior kernel: dm_suspend+0xaa/0x270 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? nv_common_set_clockgating_state+0x9f/0xb0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_device_set_cg_state+0x12f/0x280 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend_phase1+0xa3/0x180 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend+0x21/0x70 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_pre_asic_reset+0xdd/0x480 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? drm_fb_helper_set_suspend_unlocked+0x33/0xa0 [drm_kms_helper] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_gpu_recover.cold+0x6ec/0x8f8 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_job_timedout+0x14f/0x170 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_sched_job_timedout+0x6f/0x110 [gpu_sched] Jul 06 23:14:20 Excelsior kernel: process_one_work+0x22b/0x3d0 Jul 06 23:14:20 Excelsior kernel: worker_thread+0x53/0x410 Jul
[Desktop-packages] [Bug 1980934] [NEW] Backup fail with unknown error
Public bug reported: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1980934 Title: Backup fail with unknown error Status in deja-dup package in Ubuntu: New Bug description: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+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 1980933] Re: Blanked screen doesn't wake up after put into powersave
** Attachment added: "output of journalctl --user --no-pager (XZipped to match the system journal)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+attachment/5601834/+files/user-journal.log.xz -- 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/1980933 Title: Blanked screen doesn't wake up after put into powersave Status in mutter package in Ubuntu: New Bug description: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+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 1980933] [NEW] Blanked screen doesn't wake up after put into powersave
Public bug reported: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "output of journalctl --system --no-pager (XZipped due to being huge - ~900MB)" https://bugs.launchpad.net/bugs/1980933/+attachment/5601831/+files/system-journal.log.xz -- 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/1980933 Title: Blanked screen doesn't wake up after put into powersave Status in mutter package in Ubuntu: New Bug description: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-nouveau (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: New Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1978700] Re: Update gnome-text-editor to 42.2
This bug was fixed in the package gnome-text-editor - 42.2-0ubuntu1 --- gnome-text-editor (42.2-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1978700) -- Jeremy Bicha Tue, 14 Jun 2022 11:23:11 -0400 ** Changed in: gnome-text-editor (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1978700 Title: Update gnome-text-editor to 42.2 Status in gnome-text-editor package in Ubuntu: Fix Released Status in gnome-text-editor source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/blob/42.2/NEWS Test Case - Install the new gnome-text-editor Verify that the app still opens a variety of files. What Could Go Wrong --- This app is not included by default in any Ubuntu flavor. This app should fall under the GNOME microrelease exception since it is a part of core GNOME since GNOME 42. It's not been formally added to the discourse wiki yet. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1978700/+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