[Desktop-packages] [Bug 1987159] Re: Drop VNC support from GNOME Remote Desktop in Kinetic
I agree with the general consensus here. RDP is not "desktop interactive" and VNC is insecure, however, when SSH tunneling to the VNC localhost server, is very secure. Enabling Vino for Ubuntu Gnome desktop was brutally simple and easy, plus there is excellent support for using SSH to connect. PLEASE bring VNC (Vino) back to Ubuntu, especially the LTS versions! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987159 Title: Drop VNC support from GNOME Remote Desktop in Kinetic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: RDP has significantly improved privacy and performance compared to VNC. I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. GNOME is so far unwilling to provide full VNC options in the GNOME Settings app. The VNC feature was labeled as Legacy in Ubuntu 22.04 LTS. There is value in only providing a single remote desktop method by default that works well. gnome-remote-desktop 43 by default only builds the RDP provider and so far I haven't seen complaints about that. Therefore, I think we should drop the VNC feature for Ubuntu 22.10. Otherwise, we need to: 1. enable VNC in gnome-remote-desktop 43 2. Update the VNC patch in gnome-control-center 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987159/+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 1785350] Re: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of pack
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1785350 Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: Expired Bug description: First appeared after system upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Fri Aug 3 20:32:48 2018 DistUpgraded: 2018-05-18 02:00:49,256 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-24-generic, x86_64: installed nvidia, 390.77, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:18.0.5-0ubuntu0~18.04.1 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BSmI2b/074-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2017-03-23 (499 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=54d26cb9-e0f9-41d1-a593-869de12e6c28 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: Upgraded to bionic on 2018-05-18 (77 days ago) dmi.bios.date: 06/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1902 dmi.board.asset.tag: Default string dmi.board.name: Z170-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1902:bd06/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 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:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1785350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 2038728] Re: Settings - About gives wrong disk capacity
*** This bug is a duplicate of bug 2038761 *** https://bugs.launchpad.net/bugs/2038761 I am marking this a duplicate of bug 2038761 ** This bug has been marked a duplicate of bug 2038761 gnome-disk-utility does not give size of nvme disk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038728 Title: Settings - About gives wrong disk capacity Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have 3 disks 500GB each but Settings - About says disk capacity is 1 TB instead 1.5 TB corrado@corrado-n4-mm-1005:~$ sudo parted -l Model: ATA CT500MX500SSD1 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 269MB 268MB fat32 msftdata 2 269MB 8859MB 8590MB linux-swap(v1)swap 3 8859MB 43.2GB 34.4GB ext4 4 43.2GB 77.6GB 34.4GB ext4 5 77.6GB 112GB 34.4GB ext4 6 112GB 146GB 34.4GB ext4 7 146GB 500GB 354GB ext4 Model: ATA CT500MX500SSD1 (scsi) Disk /dev/sdb: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 34.4GB 34.4GB ext4 2 34.4GB 68.7GB 34.4GB ext4 3 68.7GB 103GB 34.4GB ext4 4 103GB 137GB 34.4GB ext4 5 137GB 500GB 363GB ext4 Model: KINGSTON SNV2S500G (nvme) Disk /dev/nvme0n1: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 538MB 537MB fat32EFI System Partition boot, esp 2 538MB 34.9GB 34.4GB ext4 3 34.9GB 69.3GB 34.4GB ext4 4 69.3GB 104GB 34.4GB ext4 5 104GB 138GB 34.4GB ext4 6 138GB 172GB 34.4GB ext4 7 172GB 500GB 328GB ext4 corrado@corrado-n4-mm-1005:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 19:04:08 2023 InstallationDate: Installed on 2023-10-07 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038728/+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 2023447] Re: 1.12.7 -> .8 and 1.14.0 -> .4 need updating. Some fixes are security backports from 1.14.4 for .8.
** No longer affects: flatpak -- 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/2023447 Title: 1.12.7 -> .8 and 1.14.0 -> .4 need updating. Some fixes are security backports from 1.14.4 for .8. Status in flatpak package in Ubuntu: New Bug description: https://nvd.nist.gov/vuln/detail/CVE-2023-28101 https://nvd.nist.gov/vuln/detail/CVE-2023-28100 https://github.com/flatpak/flatpak/releases/tag/1.12.8 https://github.com/flatpak/flatpak/releases/tag/1.14.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2023447/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
** Changed in: gvfs Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2039115] [NEW] Package gnome-shell-extension-gamemode is not available, but is referred to by another package.
Public bug reported: ~$ apt-cache depends gamemode | grep Suggests Suggests: ~$ sudo apt install gnome-shell-extension-gamemode Package gnome-shell-extension-gamemode is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source https://packages.ubuntu.com/search?keywords=gnome-shell-extension- gamemode ** Affects: gamemode (Ubuntu) Importance: Undecided Status: New ** Tags: jammy lunar mantic packaging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/2039115 Title: Package gnome-shell-extension-gamemode is not available, but is referred to by another package. Status in gamemode package in Ubuntu: New Bug description: ~$ apt-cache depends gamemode | grep Suggests Suggests: ~$ sudo apt install gnome-shell-extension-gamemode Package gnome-shell-extension-gamemode is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source https://packages.ubuntu.com/search?keywords=gnome-shell-extension- gamemode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2039115/+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 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
*** This bug is a duplicate of bug 1836616 *** https://bugs.launchpad.net/bugs/1836616 @Nathan That's not the same bug from my reading. That's about an upgrade. I'm saying on a totally fresh install the default behavior is not to use the OS keyring, despite it being available. -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 1969220] Re: Pinch to zoom not working on Wayland on Jammy
Can confirm. Zoom to pinch not working with Firefox snap on Wayland. Two finger scroll does work properly. Ubuntu 22.04.3 LTS snap list | grep firefox firefox118.0.1-1 3206 latest/stable/… mozilla** - Mesa Intel® Xe Graphics (TGL GT2) -- 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/1969220 Title: Pinch to zoom not working on Wayland on Jammy Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox running within snap confinement is unable to use the pinch to zoom gesture on 22.04. This is a regression as it does work on 21.10. I had been following https://bugs.launchpad.net/bugs/1964541 as it was suspected that these two issues were linked, however I am using the updated mutter released as a fix for the drag and drop bug but this didn't result in a fix for pinch to zoom. Pinch to zoom does work when using Firefox from the official tarball with the variable MOZ_ENABLE_WAYLAND=1 set. Originally reported on the snapcraft forum:https://forum.snapcraft.io/t/firefox-pinch-to-zoom-not-working- on-22-04/29391 Screen recording attached showing pinch to zoom not working on snap firefox and comparing with the gesture working on mozilla tarball firefox with libinput debug-gui showing the pinch gesture Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/beta refresh-date: 2 days ago, at 18:06 BST channels: latest/stable:99.0.1-12022-04-13 (1232) 163MB - latest/candidate: 99.0.1-12022-04-12 (1232) 163MB - latest/beta: 100.0b6-1 2022-04-15 (1244) 163MB - latest/edge: 101.0a1 2022-04-15 (1243) 180MB - esr/stable: 91.8.0esr-1 2022-04-05 (1184) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 100.0b5-1 (1236) 163MB - mutter: Installed: (none) Candidate: 42.0-3ubuntu2 Version table: 42.0-3ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969220/+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 1653351]
Strange : the latest version (3.6 published August, 8th) of " Deselect on Delete TB78" (unfortunate that the name includes "TB78") should work with Thunderbird 115. -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+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 1653351]
Great. :) Unfortunately, in my case I'm a user of the deselect addon, so that's what I was referring to. I don't know if that developer is following this bug? -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+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 1653351]
I've updated my addon and it now works with Thunderbird 115, it has not been validated ... but hopefully soon. https://addons.thunderbird.net/fr/thunderbird/addon/select-prev-on-delete/ -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+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 1653351]
The new overhaul of Thunderbird unfortunately broke the workaround addon again. :/ I don't suppose anyone has had time to look at implementing this in Thunderbird directly? -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+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 2038964] Re: raspi ethernet rename is racy
** Package changed: ubuntu-settings (Ubuntu) => ubuntu-raspi-settings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-raspi-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2038964/+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 2039104] [NEW] ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
Public bug reported: In response to LP: #2038964 and due to the timing we have forked ubuntu- raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi-settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Affects: ubuntu-settings (Ubuntu Mantic) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Tags: foundations-todo ** Also affects: ubuntu-settings (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu Mantic) Assignee: (unassigned) => Dave Jones (waveform) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2038964] Re: raspi ethernet rename is racy
Figured out a work-around: ensure the matching state of the rename rule matches the end-state of the rename rule so the networkd state machine stops flopping between the two rules. Linked the MP with the required change; will tag ubuntu-release to see if it's not too late for a re- spin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/453340 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
I have the same issue on Ubuntu 23.04 using NVIDIA 470.199.02 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 2038964] Re: raspi ethernet rename is racy
There does seem to be something unusual going on with the lan78xx re- initializing (or restarting?) part way through the boot sequence, causing another round of renaming to kick off (and then everything fails). Bizarre. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
The jammy build of 1:0.9.6.2~0.22.04.6 is still failing[1] in arm64
after a retry:
FAIL: test_system_driver_packages_force_install_nvidia
(test_ubuntu_drivers.DetectTest)
system_driver_packages() force install config points to an older version.
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
File "/<>/tests/test_ubuntu_drivers.py", line 1495, in
test_system_driver_packages_force_install_nvidia
self.assertEqual(set(packages), set(['nvidia-driver-470']))
AssertionError: Items in the first set but not the second:
'nvidia-driver-510'
Items in the second set but not the first:
'nvidia-driver-470'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1855736] Re: Duplicity fails to start
BTW, bug reporting has moved to https://gitlab.com/duplicity/duplicity/-/issues. Please report an issue there if you're still having problems. -- 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/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+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 1990341] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.1.2
---
ubuntu-drivers-common (1:0.9.7.1.2) lunar; urgency=medium
* UbuntuDrivers/detect.py:
- Skip modalias checking if id in force install list (LP: #1990341)
-- Dirk Su Thu, 31 Aug 2023 12:21:20 +0800
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2039092] [NEW] Gnome hangs on activity overview. Did the alt+f2 r workaround, but sent this bug report first.
Public bug reported: I did the alt+f2 r workaround, but sent this bug report first. Hopefully this system debugging information helps the team resolve the issue. It happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: I did the alt+f2 r workaround, but sent this bug report first. Hopefully - this helps resolve the issue. It happens frequently. + this system debugging information helps the team resolve the issue. It + happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2039092 Title: Gnome hangs on activity overview. Did the alt+f2 r workaround, but sent this bug report first. Status in gnome-shell package in Ubuntu: New Bug description: I did the alt+f2 r workaround, but sent this bug report first. Hopefully this system debugging information helps the team resolve the issue. It happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039092/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@deisi , That certainly is something for valid consideration. In my use- case there is no network bridging going on, just to clear that up. The NAS and the client are on the same network (two non-routing switches exist between them), on the same CIDR IP range, same DHCP server involved, same DNS, same internet access. So nothing is really sticking- out for me in that regards that could be relevant for my scenario. But I'm open to even more ideas I had not considered :^) as I really just would love this solved lol. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1855736] Re: Duplicity fails to start
Hi David, This sounds like a mismatch in libraries which happens when multiple versions of duplicity are installed from different sources. I'd like you to do this: $ sudo apt purge duplicity# to remove the distro version. $ sudo python3 -m pip uninstall duplicity # to remove the pip3 version. $ sudo snap remove duplicity # to remove the snap version. You may get errors in any of those. That's OK. Then reinstall from Gitlab by doing: $ sudo python3 -m pip install https://gitlab.com/duplicity/duplicity/uploads/3e1efd3ebe74bbbf2109f3d9c239f4be/duplicity-2.1.3.tar.gz This is the versioned source from https://gitlab.com/duplicity/duplicity/-/releases. -- 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/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+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 2038775] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2038775/+attachment/5708682/+files/ProcEnviron.txt -- 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/2038775 Title: Cursor dissappears in full screen Status in mutter package in Ubuntu: Incomplete Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-01-17 (2092 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter 42.9-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Tags: wayland-session jammy Uname: Linux 5.15.0-86-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-transmission dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2038775/+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 2038775] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2038775/+attachment/5708681/+files/ProcCpuinfoMinimal.txt -- 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/2038775 Title: Cursor dissappears in full screen Status in mutter package in Ubuntu: Incomplete Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-01-17 (2092 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter 42.9-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Tags: wayland-session jammy Uname: Linux 5.15.0-86-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-transmission dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2038775/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Given that a restart of the application is helping and fixes this temporarily. This reminds be of a known issue in rygel, where disable IGMP snooping is the solution if network bridges are involved and rygel can only be discovered after a restart. https://wiki.gnome.org/Projects/Rygel/FAQ Not saying that this would help anything here. I just want to raise awareness that this might also be caused by other external factors along the network. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2038775] Re: Cursor dissappears in full screen
apport information ** Tags added: apport-collected jammy ** Description changed: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2018-01-17 (2092 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) + Package: mutter 42.9-0ubuntu5 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 + Tags: wayland-session jammy + Uname: Linux 5.15.0-86-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom debian-transmission dip docker input lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2038775/+attachment/5708680/+files/Dependencies.txt -- 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/2038775 Title: Cursor dissappears in full screen Status in mutter package in Ubuntu: Incomplete Bug description: Only started recently, but not all apps. Some snap, flatpak, or deb. Snap: youtube music desktop Flatpak: Easy effects Deb: MultiViewer When in windowed mode the cursor is fine, But in full screen mode in some apps it is invisible. Ubuntu 20.04.3 LTS Kernel: 5.15.0-86 Window system: wayland Gnome: 42.9 Mesa: 23.0.4-ubuntu1~22.04.1 Cpu/gpu: AMD Kaveri A10-7800 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-01-17 (2092 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter 42.9-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Tags: wayland-session jammy Uname: Linux 5.15.0-86-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-transmission dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2038775/+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 2034986] Re: some text became unreadable during a distribution upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:23.10.10 --- ubuntu-release-upgrader (1:23.10.10) mantic; urgency=medium * Fix failing autopkgtest due to PEP8 line to long issue. * Run pre-build.sh: updating po files, mirrors, and demotions. ubuntu-release-upgrader (1:23.10.9) mantic; urgency=medium [ Tim Andersson ] * fix: stop TypeError traceback in DistUpgradeQuirks:_set_generic_font (LP: #2038900) [ Brian Murray ] * Run pre-build.sh: updating po files, mirrors, and demotions. [ Gunnar Hjalmarsson ] * Temporary font for Ubuntu MATE (LP: #2034986) -- Brian Murray Wed, 11 Oct 2023 04:48:13 -0700 ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
It's looking like maybe the most relevant GNOME issue thread is : https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 (Holy cow! 6 years originally posted! Yikes!) Also, there looks to be two open MRs in #307 (linked above) which might help. One is for use of WSD (which as demonstrated isn't relevant, in my case anyways), and the other, something about SMB server cache (which I'm a touch dubious of, but I'm asking for details). Ondrej really carrying the torch there though! :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
STILL having this problem! Also, the gnome issue of #506 is NOT RELEVANT! As this issue PREDATED WSD IN TOTALITY. Like, how more clear do I REEAALLL need to make this? I kill the gvfsd-smb-browse process, and IMMEDIATELY I can browse SMB shares when SMB1 is disabled. CLEARLY the application is capable, however is unwilling to cooperate until it gets restarted (gvfsd-smb-browse). This has NOTHING to do with WSD in impact, or even as a solution! WSD _IS NOT PRESENT ON MY NETWORK_. Hell, we even have another thread _claiming_ that this was fixed in much earlier versions of Ubuntu (which clearly it wasn't): https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322 Again, also, _THIS HAPPENS OUT OF THE BOX FOR ALL UBUNTU DESKTOP INSTALLATIONS CURRENT AND FOR THE PAST 4+ YEARS_. ** Changed in: gvfs Remote watch: gitlab.gnome.org/GNOME/gvfs/-/issues #506 => None ** Changed in: gvfs Status: New => Unknown ** Changed in: gvfs Remote watch: None => gitlab.gnome.org/GNOME/gvfs/-/issues #307 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2034986] Re: some text became unreadable during a distribution upgrade
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Still having to kill gvfsd-smb-browse each time I reboot just so I can browse network shares. Clearly the fix didn't actually fix this. This is going on 4-ish years now. Additional thread: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Released Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Released Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Argh! During ISO testing I thought I'd just quickly check this still didn't occur on a Pi 5... only to find it did, this time. I've still not encountered a Pi 4 where it *didn't* occur, but I wonder if this is a race-condition somewhere and just more prone to occurring on the slower 4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+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 1855736] Re: Duplicity fails to start
Hello, Not sure that is is correct, the full backup and the incremental seem to work but I have this at the end : CommandLineError: Wrong number of positional args for 'restore', got 3 Expected 2 positionals from ['--file-to-restore=home/..deja-dup/metadata', 'gio+file:///media/../backups', '/home/..deja-dup/metadata']. Any idea for if it is link ? For the first backup, the partition of the deja-dup cache, have been very few space, don't know if at a moment, it has been full. Thanks in advance. David -- 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/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+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 2038728] Re: Settings - About gives wrong disk capacity
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038728 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038728 Title: Settings - About gives wrong disk capacity Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have 3 disks 500GB each but Settings - About says disk capacity is 1 TB instead 1.5 TB corrado@corrado-n4-mm-1005:~$ sudo parted -l Model: ATA CT500MX500SSD1 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 269MB 268MB fat32 msftdata 2 269MB 8859MB 8590MB linux-swap(v1)swap 3 8859MB 43.2GB 34.4GB ext4 4 43.2GB 77.6GB 34.4GB ext4 5 77.6GB 112GB 34.4GB ext4 6 112GB 146GB 34.4GB ext4 7 146GB 500GB 354GB ext4 Model: ATA CT500MX500SSD1 (scsi) Disk /dev/sdb: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 34.4GB 34.4GB ext4 2 34.4GB 68.7GB 34.4GB ext4 3 68.7GB 103GB 34.4GB ext4 4 103GB 137GB 34.4GB ext4 5 137GB 500GB 363GB ext4 Model: KINGSTON SNV2S500G (nvme) Disk /dev/nvme0n1: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 538MB 537MB fat32EFI System Partition boot, esp 2 538MB 34.9GB 34.4GB ext4 3 34.9GB 69.3GB 34.4GB ext4 4 69.3GB 104GB 34.4GB ext4 5 104GB 138GB 34.4GB ext4 6 138GB 172GB 34.4GB ext4 7 172GB 500GB 328GB ext4 corrado@corrado-n4-mm-1005:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 19:04:08 2023 InstallationDate: Installed on 2023-10-07 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038728/+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 2038761] Re: gnome-disk-utility does not give size of nvme disk
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038761 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2038761 Title: gnome-disk-utility does not give size of nvme disk Status in udisks: New Status in udisks2 package in Ubuntu: Triaged Bug description: Mantic gnome-disk-utility: 45.0-1ubuntu1 Size of nvme disk is blank while in Jammy 42.0-1ubuntu1 gives correct size. see attached image ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-disk-utility 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 17:16:12 2023 InstallationDate: Installed on 2023-10-07 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2038761/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.6.2~0.22.04.6 in jammy-proposed has no closing bug, and the
changes file should include version 22.04.5 too I believe. There is also
a build failure for arm64 (due to a build-time test failing). I will
retrigger it, but I'm thinking we need a new upload to fix the changes
file at least, and perhaps the build failure if it persists.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Committed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2034986] Re: some text became unreadable during a distribution upgrade
@Ethan: MATE is about to be fixed. Once ubuntu-release-upgrader 1:23.10.10 has made it to mantic-release, you shouldn't be able to reproduce that. Let us know otherwise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2024377] Re: Adsys can't fetch GPOs
regularuser@LCXVDU22NPE4030:~$ apt list --installed | grep adsys
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
adsys/jammy-updates,now 0.9.2~22.04.2 amd64 [installed]
regularuser@LCXVDU22NPE4030:~$ apt list --installed | grep libsmbclient
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
libsmbclient/jammy-security,now 2:4.15.13+dfsg-0ubuntu1.5 amd64
[installed,automatic]
regularuser@LCXVDU22NPE4030:~$ sudo adsysctl update -m -vvv
INFO github.com/ubuntu/adsys/internal/config/config.go:78 Init() Using
configuration file: /etc/adsys.yaml
DEBUG Connecting as [[4492:009622]]
DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:27
StreamServerInterceptor.func1() New request /service/UpdatePolicy
DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:60
loggedServerStream.RecvMsg() Requesting with parameters: IsComputer: true, All:
false, Target: LCXVDU22NPE4030, Krb5Cc:
DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:571 (*AD).NormalizeTargetName()
NormalizeTargetName for "LCXVDU22NPE4030", type "computer"
DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:111
Authorizer.IsAllowedFromContext() Check if grpc request peer is authorized
DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:150
Authorizer.isAllowed() Authorized as being administrator
DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:225 (*AD).GetPolicies()
GetPolicies for "LCXVDU22NPE4030", type "computer"
DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:293 (*AD).GetPolicies() Getting
gpo list with arguments: "--objectclass computer
ldap://n060adkhdc121.domain.com LCXVDU22NPE4030"
DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:315 (*AD).GetPolicies() GPO
"00cEntCTX-Ubuntu-Edge" for "LCXVDU22NPE4030" available at
"smb://domain.com/SysVol/domain.com/Policies/{F7E97A8D-7DB1-4571-956A-005D1658DC35}"
DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:315 (*AD).GetPolicies() GPO
"00cEntCtx-Ubuntu-Test" for "LCXVDU22NPE4030" available at
"smb://domain.com/SysVol/domain.com/Policies/{5B925A10-9572-4FB8-B9A0-DB2DFF9EF34B}"
DEBUG github.com/ubuntu/adsys/internal/ad/download.go:113 (*AD).fetch.func2()
Analyzing "00cEntCtx-Ubuntu-Test"
DEBUG github.com/ubuntu/adsys/internal/ad/download.go:113 (*AD).fetch.func2()
Analyzing "00cEntCTX-Ubuntu-Edge"
DEBUG github.com/ubuntu/adsys/internal/ad/download.go:113 (*AD).fetch.func2()
Analyzing "assets"
INFO github.com/ubuntu/adsys/internal/ad/download.go:124 (*AD).fetch.func2() No
assets directory with GPT.INI file found on AD, skipping assets download
ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from
server: error while updating policy: can't get policies for "LCXVDU22NPE4030":
can't download all gpos and assets: one or more error while fetching GPOs and
assets: can't download "00cEntCtx-Ubuntu-Test": can't check if
00cEntCtx-Ubuntu-Test needs refreshing: no GPT.INI file: cannot open
smb://domain.com/SysVol/domain.com/Policies/{5B925A10-9572-4FB8-B9A0-DB2DFF9EF34B}/GPT.INI:
invalid argument
Let me know if you want any additional information or want me to try
anything. These are VMs so I can spin them back up quickly if I brick
one.
I can do a cifs mount to the GPT.INI file and open it just fine but
Adsys and Smbclient will fail out trying to hit those directly. I did
notice smbclient works when using the -D flagsmbclient
//example.com/sysvol -D "example.com/policies/{policy}" Without that
flag (smbclient //example.com/sysvol/example.com/policies/{policy}) it
comes back with tree connect failed: NT_STATUS_BAD_NETWORK_NAME Case
matching doesn't seem to make a difference for me. I thought it was a
client side configuration problem and have been tinkering with SMB.conf
but I had not gotten anywhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Confirmed
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
just attaching a screen shot ** Attachment added: "upgrade.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5708659/+files/upgrade.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2034986 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038964] Re: raspi ethernet rename is racy
FWIW, this works correctly with a 6.2 lunar kernel and mantic userspace. ** Attachment added: "udev-6-2-3b+.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708655/+files/udev-6-2-3b+.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038811] Re: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connecti
Reproducer: nmcli con add type wifi ifname wlan0 ssid asdasd wifi-sec.key-mgmt wpa-eap 802-1x.eap leap 802-1x.identity username 802-1x.password The crash (SIGABRT) happens in NetworkManager's Netplan integration patch, because of running into a "nm_assert_not_reached()" call. This could easily be avoided by muting that assert and just logging the error and returning FALSE (as is already done below the assert): https://git.launchpad.net/ubuntu/+source/network- manager/tree/debian/patches/netplan/0002-netplan-make-use-of-libnetplan- for-YAML-backend.patch#n319 This would not fix the root-cause, though, which is located in libnetplan: When creating or updating a NetworkManager connection profile that uses a 802.1x eap authentication method unknown to Netplan (such as "leap" or "pwd"), the Netplan keyfile parser is getting confused and generates a broken keyfile config for NetworkManager. https://github.com/canonical/netplan/blob/main/src/parse-nm.c#L383 This is triggered when manually adding/modifying a corresponding NM connection profile (through the NM GUI, nmcli, NM DBus, ...) or automatically, when migrating a corresponding profile through NetworkManager's "Netplan everywhere" migration as part of the .postinst maintainer script. In the latter case the crash is handled gracefully, NetworkManager is restarted and the broken keyfile is restored from a backup. https://git.launchpad.net/ubuntu/+source/network- manager/tree/debian/network-manager.postinst#n67 This can be fixed by supporting all of NetworkManager's 802.1x eap authentication methods in Netplan or by making Netplan's passthrough logic detect such cases and handle them as a fallback. Kudos to @danilogondolfo for the investigation and the proposed patch: https://github.com/canonical/netplan/pull/415 ** Changed in: netplan.io (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Importance: High => Medium ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Status: New => Triaged -- 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/2038811 Title: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.44.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+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 2039021] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)
Launchpad has imported 9 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=157424. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2023-09-25T07:09:33+00:00 Bákonyi Zsolt wrote: Description: After upgrading via ppa to 7.6.1.2 60(Build:2) version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous versions doesent produces this error, e.g: 7.5.6.2 50(Build:2) work perfect. Steps to Reproduce: 1. soffice --headless --convert-to pdf path/to/file Actual Results: Error: source file could not be loaded Expected Results: convert path/to/file as a Writer document -> path/to/file using filter : writer_pdf_Export Reproducible: Always User Profile Reset: No Additional Info: soffice --version LibreOffice 7.6.1.2 60(Build:2) Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/0 On 2023-10-09T12:55:44+00:00 Bákonyi Zsolt wrote: Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/1 On 2023-10-09T13:28:42+00:00 Stephane-guillou-i wrote: I can't reproduce convert ODT or DOCX to PDF with: libreoffice7.6 --headless --convert-to pdf some_doc and: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded ...but this isn't a -nogui install. (In reply to Zsolt Bákonyi from comment #1) > !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Maybe a fix made it in that version? Would be interesting to see if version 7.6.2.1 also works for you as -nogui, using this PPA: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa Any chance you could test that one too? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/2 On 2023-10-09T13:47:04+00:00 Bákonyi Zsolt wrote: Hi! On normal Ubuntu Desktop no error. Personally I use Kubuntu 20.04 LTS version with LibreOffice 7.6.2.1 60(Build:1) and this problem does not appear. And I had no issues with older versions. Only no-gui installation produces these issues, I've tested on 3 different Ubuntu 20.04 Server LTS. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/3 On 2023-10-10T09:17:42+00:00 Ilmari-lauhakangas wrote: Related: https://packages.debian.org/sid/libreoffice-nogui https://packages.debian.org/sid/libreoffice-core-nogui I could not find out what manipulations have been made to this thing. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/4 On 2023-10-10T09:28:08+00:00 Ilmari-lauhakangas wrote: Please report it to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libreoffice/ Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/5 On 2023-10-11T09:09:32+00:00 Bákonyi Zsolt wrote: Something I don't understand if I use LibreOffice 7.5.6.2 50(Build:2) no-gui installation on these systems, it works perfectly in both case ( xlsx and docx conversion ) Maybe somethng went wrong while packaging in PPA? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/comments/6
[Desktop-packages] [Bug 2039045] [NEW] GNOME Shell locking hard when Telegram opens a full-screen photo
Public bug reported: Steps: - run https://snapcraft.io/telegram-desktop - open a full-screen image preview Expected: - the image preview opens - and can be closed Current: - the image preview opens - the shell becomes unresponsive Often it's possible to wait a few seconds to close the preview again, but sometimes it just locks up hard with no way to recover. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 14:30:31 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-06 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2039045 Title: GNOME Shell locking hard when Telegram opens a full-screen photo Status in gnome-shell package in Ubuntu: New Bug description: Steps: - run https://snapcraft.io/telegram-desktop - open a full-screen image preview Expected: - the image preview opens - and can be closed Current: - the image preview opens - the shell becomes unresponsive Often it's possible to wait a few seconds to close the preview again, but sometimes it just locks up hard with no way to recover. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 14:30:31 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-06 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039045/+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 2024377] Re: Adsys can't fetch GPOs
Interesting - so we are able to get the list of GPOs, _and_ smbclient is
able to print the contents of the GPT.INI file, but adsys still fails.
At this point I'm out of ideas, I would suggest the following:
- upgrade the system to make sure you are running the latest available versions
of adsys (0.9.2~22.04.2) and libsmbclient (2:4.15.13+dfsg-0ubuntu1.5) for your
OS version
- confirm
- paste the output of running `sudo adsysctl update -m -vv` again
I noticed you're not the originator of the ticket and you haven't yet
shared actual logs of running adsysctl - so this would be helpful in our
investigation.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Confirmed
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER')
Additional info:
Domain Controller and machine are on the same subnet without firewall on any
level;
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
udev debug log from a 3B+ ** Attachment added: "udev-3b+.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708640/+files/udev-3b+.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
udev debug log from a 3B ** Attachment added: "udev-3b.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708641/+files/udev-3b.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038951] Re: Welcome To Ubuntu application not in specified language after installing offline.
** Package changed: ubiquity (Ubuntu) => gnome-initial-setup (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2038951 Title: Welcome To Ubuntu application not in specified language after installing offline. Status in gnome-initial-setup package in Ubuntu: New Bug description: I installed in swedish with no internet connection, and after the install completed and rebooted, everything was in swedish except the Welcome To Ubuntu application. This is not the case with an installation with internet access. --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-10-10 (0 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) Package: ubiquity (not installed) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Tags: mantic wayland-session ubiquity-23.10.8 Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2038951/+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 2037017] Re: Sharing tab hangs gnome-control-center
Oh, one other note: no output in the journal during the hang; I'm afraid the only info is from the backtrace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+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 2038964] Re: raspi ethernet rename is racy
** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038951] [NEW] Welcome To Ubuntu application not in specified language after installing offline.
You have been subscribed to a public bug: I installed in swedish with no internet connection, and after the install completed and rebooted, everything was in swedish except the Welcome To Ubuntu application. This is not the case with an installation with internet access. --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-10-10 (0 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) Package: ubiquity (not installed) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Tags: mantic wayland-session ubiquity-23.10.8 Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected iso-testing mantic ubiquity-23.10.8 wayland-session -- Welcome To Ubuntu application not in specified language after installing offline. https://bugs.launchpad.net/bugs/2038951 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. -- 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 2038909] Re: X13s desktop image is missing qcom power management tools
** Changed in: ubuntu-cdimage Status: New => Fix Committed ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Milestone: None => mantic-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2038909 Title: X13s desktop image is missing qcom power management tools Status in Ubuntu CD Images: Fix Committed Status in ubuntu-meta package in Ubuntu: New Bug description: X13s desktop image is missing qcom power management tools specifically protection-domain-mapper and qrtr-tools which potentially need MIR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2038909/+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 2038903] Re: X13s didn't run flashkernel as part of the install
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2038903 Title: X13s didn't run flashkernel as part of the install Status in Ubuntu CD Images: Fix Released Status in ubuntu-meta package in Ubuntu: New Bug description: X13s didn't run flashkernel as part of the install hence dtb was not preset in /boot/ and thus installed system is incorrect. either we need to splice dtb into vmlinuz (which we can with sd-boot stub + zimg + devicetree) or make flashkernel run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2038903/+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 2039021] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)
** Bug watch added: Document Foundation Bugzilla #157424 https://bugs.documentfoundation.org/show_bug.cgi?id=157424 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=157424 Importance: Unknown Status: Unknown -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+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 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels
** Changed in: gnome-control-center (Ubuntu) Milestone: None => mantic-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: In Progress Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+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 2039021] [NEW] NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)
Public bug reported: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/2039021 Title: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2) Status in libreoffice package in Ubuntu: New Bug description: Original bug report to LibreOffice team: https://bugs.documentfoundation.org/show_bug.cgi?id=157424 7.6.1.2 60(Build:2) no-gui version, Ubuntu Server 20.04 LTS gives error. soffice --headless --convert-to pdf path/to/file --> Error: source file could not be loaded Ubuntu 20.04 LTS Desktop version has no error with the same version, only on Server. The installation difference is libreoffice vs libreoffice-nogui. Previous version doesent produces this error: 7.5.6.2 50(Build:2) work perfect. Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error: source file could not be loaded" message. Specific examples: - LibreOffice 6.4.7.2 40(Build:2) --> Same error with xlsx with --convert-to html - LibreOffice 7.5.3.2 50(Build:2) --> Same error with xlsx with --convert-to html !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case. !!! Example outputs: soffice --headless --convert-to pdf teszt.docx convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : writer_pdf_Export soffice --headless --convert-to html teszt.xlsx convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML (StarCalc) Fortunately *ppa:libreoffice/libreoffice-still* contains the good version so i had to change the repos in all servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2039021/+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 2038998] Re: Screen artifacts/UI oddities on Wayland following Steam/Proton session
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
Screen artifacts/UI oddities on Wayland following Steam/Proton session
Status in xorg package in Ubuntu:
New
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/xorg/+bug/2038998/+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 2038998] [NEW] Screen artifacts/UI oddities on Wayland following Steam/Proton session
You have been subscribed to a public bug:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two compatible
titles.
Screen corruption (white and grey streaks) present in-game when GNOME UI
elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS (GNOME,
Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this computer
without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption mantic ubuntu wayland-session
--
Screen artifacts/UI oddities on Wayland following Steam/Proton session
https://bugs.launchpad.net/bugs/2038998
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
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 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
*** This bug is a duplicate of bug 1836616 *** https://bugs.launchpad.net/bugs/1836616 Found the duplicate target; See there that the interface auto-connection was denied by Snap Store. ** This bug has been marked a duplicate of bug 1836616 [snap] Upgrade from deb to snap forgets saved passwords -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
** Tags added: password-storage -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Released Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin/chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+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 2038741] Re: Disk capacity shows as uknown on NVME SSD
*** This bug is a duplicate of bug 2038761 ***
https://bugs.launchpad.net/bugs/2038761
thanks, it's the same as bug #2038761
** This bug has been marked a duplicate of bug 2038761
gnome-disk-utility does not give size of nvme disk
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2038741
Title:
Disk capacity shows as uknown on NVME SSD
Status in udisks2 package in Ubuntu:
Incomplete
Bug description:
see picture added
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: udisks2 2.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.eog.rules 70-snap.gnome-logs.rules
70-snap.discord.rules 70-snap.snap-store.rules 70-snap.steam.rules
70-snap.element-desktop.rules 70-snap.0ad.rules 70-snap.cups.rules
70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules
70-snap.snapd-desktop-integration.rules 70-snap.thunderbird.rules
70-snap.gedit.rules 70-snap.gimp.rules 70-snap.onlyoffice-desktopeditors.rules
ubuntu--vg-ubuntu--lv.rules 70-snap.kdenlive.rules 70-snap.firefox.rules
70-snap.snapd.rules
Date: Sun Oct 8 09:23:26 2023
InstallationDate: Installed on 2023-09-27 (11 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: Upgraded to mantic on 2023-10-03 (4 days ago)
dmi.bios.date: 09/04/2023
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E15K1IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-15K1
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15K1IMS.10E:bd09/04/2023:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnCyborg15A13VE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15K1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15K1.1:
dmi.product.family: GF
dmi.product.name: Cyborg 15 A13VE
dmi.product.sku: 15K1.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2038741/+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 2038727] Re: Chromium snap theme parsing error
** Changed in: chromium-browser (Ubuntu) Status: In Progress => 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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
