[Desktop-packages] [Bug 2041825] Re: Saving a wireguard VPN connection fails
I'm adding a wireguard config by hand.. - add the private key as generated by 'wg genkey' - add the peer (endpoint, public key, allowed ip's) - set up ipv4 (manual; address/mask, dns) if at this point (before saving) you select "automatic", it allows you to save but it isn't actually saved as mentioned originally. But if, instead of saving, you select "manual" again, it *doesn't* let you save unless you change some of the previously entered values. -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2036817]
Created attachment 190495 spreadsheet that randomly crashes on close -- 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/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Occurred when exiting Calc/ ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 13:44:57 2023 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2023-09-17 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi PC (0x7f4aee4abf8e) ok source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, com::sun::star::uno::Reference const&) () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::OAccessibleContextWrapper::disposing() () from /usr/lib/libreoffice/program/libmergedlo.so cppu::WeakComponentImplHelperBase::dispose() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 cppu::WeakComponentImplHelperBase::release() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2036817]
LibreOffice 7.6.2.1 on opensuse Tumbleweed. This just crashed when i closed it. It's a simple spreadsheet I am attaching, but the crash happens randomly at close, not every time. Application: soffice (soffice), signal: Segmentation fault [KCrash Handler] #4 0x7feea0b5fac0 in rtl_uString_release () at /usr/lib64/libreoffice/program/libuno_sal.so.3 #5 0x7fee9d6bf2fb in () at /usr/lib64/libreoffice/program/libmergedlo.so #6 0x7fee9d8130c3 in () at /usr/lib64/libreoffice/program/libmergedlo.so #7 0x7fee9c041b06 in __run_exit_handlers () at /lib64/libc.so.6 #8 0x7fee9c041c50 in () at /lib64/libc.so.6 #9 0x7fee9c0281b7 in __libc_start_call_main () at /lib64/libc.so.6 #10 0x7fee9c028279 in __libc_start_main_impl () at /lib64/libc.so.6 #11 0x558e5b66b0c5 in () [Inferior 1 (process 31456) detached] -- 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/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Occurred when exiting Calc/ ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 13:44:57 2023 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2023-09-17 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi PC (0x7f4aee4abf8e) ok source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, com::sun::star::uno::Reference const&) () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::OAccessibleContextWrapper::disposing() () from /usr/lib/libreoffice/program/libmergedlo.so cppu::WeakComponentImplHelperBase::dispose() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 cppu::WeakComponentImplHelperBase::release() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2041825] Re: Saving a wireguard VPN connection fails
The description is a bit confusing. So wireguard is listed in the vpn dialog but you fail to import an existing config? Could you provide details on the steps you are following exactly and the configuration details? -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2041853] [NEW] screen goes blank, audio cuts out, cause Window manager warning: Overwriting existing binding of keysym messages
Public bug reported: I'm tracking down the multiple causes of screen flashes and audio interruption on my ubuntu 22.04 laptop. Issue open with Lenovo : https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298 This bug is one of the causes (log reversed : journalctl -r) oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac8bfbc10] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd416dc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996b860] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878ac50] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb009cc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a610] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9f6a480] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd404df0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a2f0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb16d9a0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca446320] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acdf86f70] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996a4e0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6fd0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9e94de0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6350] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb121e80] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996ab60] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6670] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd3dada0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion
[Desktop-packages] [Bug 2041856] [NEW] Evince crash with libreoffice comment in generated PDF
Public bug reported: 1) Description: Ubuntu 22.04.3 LTS, Release:22.04 2) Installed: 42.3-0ubuntu3, Candidate: 42.3-0ubuntu3 3) I expected a PDF with embedded comments to open and display without issue. 4) Evince crashes just after rendering document containing a comment, in larger document it crashes when moving to the page with the comment. The following appears in the /var/log/syslog: Oct 30 11:44:25 flappy dbus-daemon[2156]: [session uid=1000 pid=2156] Successfully activated service 'org.gnome.evince.Daemon' Oct 30 11:44:26 flappy kernel: [1129165.202923] show_signal: 12 callbacks suppressed Oct 30 11:44:26 flappy kernel: [1129165.202937] traps: evince[435563] trap int3 ip:7fd65910bcef sp:7fff5f9d8280 error:0 in libglib-2.0.so.0.7200.4[7fd6590cc000+8f000] I've reported this to gnome, but seems to be fixed upstream: https://gitlab.gnome.org/GNOME/evince/-/issues/1990, and version used in Ubuntu LTS is no longer supported. The ticket also contains example libreoffice file and generated PDF. Kind regards, Dennis ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Oct 30 15:40:57 2023 InstallationDate: Installed on 2016-09-05 (2611 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-29 (427 days ago) modified.conffile..etc.apparmor.d.usr.bin.evince: [modified] mtime.conffile..etc.apparmor.d.usr.bin.evince: 2023-10-30T11:33:14.224555 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2041856 Title: Evince crash with libreoffice comment in generated PDF Status in evince package in Ubuntu: New Bug description: 1) Description: Ubuntu 22.04.3 LTS, Release:22.04 2) Installed: 42.3-0ubuntu3, Candidate: 42.3-0ubuntu3 3) I expected a PDF with embedded comments to open and display without issue. 4) Evince crashes just after rendering document containing a comment, in larger document it crashes when moving to the page with the comment. The following appears in the /var/log/syslog: Oct 30 11:44:25 flappy dbus-daemon[2156]: [session uid=1000 pid=2156] Successfully activated service 'org.gnome.evince.Daemon' Oct 30 11:44:26 flappy kernel: [1129165.202923] show_signal: 12 callbacks suppressed Oct 30 11:44:26 flappy kernel: [1129165.202937] traps: evince[435563] trap int3 ip:7fd65910bcef sp:7fff5f9d8280 error:0 in libglib-2.0.so.0.7200.4[7fd6590cc000+8f000] I've reported this to gnome, but seems to be fixed upstream: https://gitlab.gnome.org/GNOME/evince/-/issues/1990, and version used in Ubuntu LTS is no longer supported. The ticket also contains example libreoffice file and generated PDF. Kind regards, Dennis ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Oct 30 15:40:57 2023 InstallationDate: Installed on 2016-09-05 (2611 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-29 (427 days ago) modified.conffile..etc.apparmor.d.usr.bin.evince: [modified] mtime.conffile..etc.apparmor.d.usr.bin.evince: 2023-10-30T11:33:14.224555 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2041856/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Ok, problem solved on my Ubuntu Noble corrado@corrado-n2-nn-1029:~$ apt policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 87ubuntu2 Candidate: 87ubuntu2 Version table: *** 87ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status corrado@corrado-n2-nn-1029:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2041491] Re: Provide an option to avoid the yaml NM backend
Thank you; if I understood correctly, that method would render all the NM GUI/console tools unusable; it's not a viable workaround, as I would like to be able to use these tools as well... E.g.: - Create a new bond => GUI, nmtui, nmcli - Did I forget any setting while creating that bond? Let's compare it with a Debian box => `meld ubuntu-box:/etc/NetworkManager/system-connections debian-box:/etc/NetworkManager/system-connections` -- 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/2041491 Title: Provide an option to avoid the yaml NM backend Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hi, recently netplan added support for a yaml NM backend: https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml- settings/32420 The rationale is that "the descriptive YAML layer is especially useful in cloud environments": https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556 It's great that you care about that user group! Please also care for the rest of us that do not use cloud environments! For example, I routinely review, clone, backup or even directly edit the /etc/NetworkManager/system-connections files in my desktops and servers, in all distributions. Having an Ubuntu-specific way to do things will make things harder for me. I will have to learn a new Ubuntu-specific syntax, develop scripts and methods to convert my connections between distributions, I will need to discover and report bugs in the netplan <=> nm mapping etc... I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide a unified yaml-based experience for cloud-init etc. But Ubuntu is also great outside the cloud; please allow us to continue having a unified experience between distributions (i.e. directly using nm or systemd-networkd) without enforcing an Ubuntu-specific way of doing things (netplan) to us. For Ubuntu 24.04+, please provide an option to avoid the yaml NM backend, thank you very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+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 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
Same here (( -- 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/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell package in Arch Linux: New Bug description: Hello, Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible to restart gnome-shell without crashing the session. The only way not to crash it is to close all applications before restarting gnome-shell. I have verified this too. This has already been reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050 a tentative patch for mutter proposed: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598 Please consider reviewing/testing this patch and pushing an update so people can restart gnome-shell session without crashing it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+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 2031413] Re: Inherited NFSv4 ACLs are overwritten when moving a file
** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/3077 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2031413 Title: Inherited NFSv4 ACLs are overwritten when moving a file Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Bug description: Ubuntu version: 22.04 libglib2.0 version: libglib2.0-0_2.72.4-0ubuntu2.2 We are mounting an NFS share from an NFS server (FreeBSD 13). Authorization to directories in that share is enforced through NFSv4 ACLs on the server. When copying or moving a file to the share, it will inherit ACLs from the destination directory. In most of the cases this works fine. However, when we move a file that has ACLs to a directory in the share using Nautilus or "gio move", the ACL inheritance goes wrong. The destination file will end up with the original ACLs (the ACLs it had in the source location) instead of the ACLs that are inherited by the destination directory. This behaviour changed when we upgraded from Ubuntu 20.04 to Ubuntu 22.04. In Ubuntu 20.04 the ACL inheritance worked as expected. I assume what happens is the following: 1. A server-side move is performed 2. The destination file is assigned ACLs (they are inherited from the destination directory) 3. glib overwrites the ACLs of the destination file with the original ACLs To workaround the issue we patched glib and removed a call to g_file_set_attributes_from_info, see the attached patch. This brings the expected behaviour but may have unintended side effects. Steps to reproduce: 1. on the server (FreeBSD): prepare two directories A and B and assign the following NFSv4 ACLs: # file: A # owner: root # group: wheel user:alice:rwx--daARWc--s:fd-:allow owner@:rwxp-daARWc--s:fd-:allow group@:--a-R-c--s:fd-:allow everyone@:--a-R-c--s:fd-:allow # file: B # owner: root # group: wheel user:alice:rwx--daARWc--s:fd-:allow user:bob:rwx--daARWc--s:fd-:allow owner@:rwxp-daARWc--s:fd-:allow group@:--a-R-c--s:fd-:allow everyone@:--a-R-c--s:fd-:allow Note the inheritance flags (fd), which indicate that files in the directories will inherit the ACLs. 2. on the client (Ubuntu): mount the NFS share to /mnt using credentials of user "alice" 3. on the client: echo "hello world" > /mnt/A/test.txt 4. on the server: list the ACLs of A/test.txt: # file: A/test.txt # owner: alice # group: wheel user:alice:rw---daARWc--s:--I:allow owner@:rw-p-daARWc--s:--I:allow group@:--a-R-c--s:--I:allow everyone@:--a-R-c--s:--I:allow 5. on the client: gio move /mnt/A/test.txt /mnt/B/test.txt 6. on the server: list the ACLs of B/test.txt # file: B/test.txt # owner: alice # group: wheel user:alice:rw---daARWc--s:--I:allow owner@:rw-p-daARWc--s:--I:allow group@:--a-R-c--s:--I:allow everyone@:--a-R-c--s:--I:allow We expected an ACE for user bob, but it is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2031413/+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 2036751] Re: file-roller's show files doesn't go to file directory
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: file-roller (Ubuntu) Importance: Undecided => Low ** Changed in: file-roller (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2036751 Title: file-roller's show files doesn't go to file directory Status in file-roller package in Ubuntu: Incomplete Bug description: Clicking show files doesn't pull up the directory the files were extracted to. It opens home. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2036751/+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 2041825] Re: Saving a wireguard VPN connection fails
it lets me save if I don't specify the gateway... -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2041825] Re: Saving a wireguard VPN connection fails
if I use manual and add the IP/mask/gateway and DNS server, it still doesn't let me save it. Should be able to leave routes as-is at least according to https://www.xmodulo.com/wireguard-vpn-network-manager-gui.html -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2022391] Re: security breach
** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2022391 Title: security breach Status in gnome-control-center package in Ubuntu: Incomplete Bug description: i update to lunar-lobster a few days ago (40 days ).I understand that i as a beta version but when i go to the security settings i saw that my firmware didnt pass the test so i dont know if is a problem of the version or is my laptop's problem My computer hardware : System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi Drives: Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%) Info: Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%) Shell: Bash inxi: 3.3.25 Informe de seguridad del dispositivo == Detalles del informe Fecha generada: 2023-06-02 22:48:37 Versión de fwupd1.8.12 System details Modelo de hardware: HUAWEI NBD-WXX9 Procesador 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz SO: Ubuntu 23.04 Nivel de seguridad: HSI:0! (v1.8.12) HSI-1 Pruebas Intel Management Engine Version: Falló (No válido) UEFI Platform Key: Correcto (Válido) TPM v2.0:Correcto (Encontrada) Firmware BIOS Region:Correcto (Bloqueada) Firmware Write Protection Lock: Correcto (Activada) Platform Debugging: Correcto (No activada) Intel Management Engine Manufacturing Mode: Correcto (Bloqueada) UEFI Secure Boot:Correcto (Activada) Firmware Write Protection: Correcto (No activada) Intel Management Engine Override:Correcto (Bloqueada) TPM Platform Configuration: Correcto (Válido) HSI-2 Pruebas Intel BootGuard Fuse:Correcto (Válido) Intel BootGuard Verified Boot: Falló (No válido) Intel BootGuard ACM Protected: Falló (No válido) Intel BootGuard: Correcto (Activada) TPM Reconstruction:Falló (No encontrada) IOMMU Protection: Falló (No encontrada) Platform Debugging: Correcto (Bloqueada) HSI-3 Pruebas Suspend To RAM: Correcto (No activada) Intel BootGuard Error Policy: Falló (No válido) Pre-boot DMA Protection: Correcto (Activada) Intel CET: Correcto (Activada) Suspend To Idle: Correcto (Activada) HSI-4 Pruebas Encrypted RAM: Falló (No admitida) Intel SMAP: Correcto (Activada) Pruebas de tiempo de ejecución Firmware Updater Verification: Correcto (No envenenado) Linux Kernel Lockdown: Correcto (Activada) Linux Swap:Falló (No cifrado) Linux Kernel Verification: Correcto (No envenenado) Intel CET: Correcto (Admitida) Eventos de seguridad del equipo 2023-04-21 20:11:14 Firmware Updater VerificationCorrecto (No activada → No envenenado) 2023-01-28 17:13:05 Firmware Updater VerificatiFalló (No envenenado → No activada) Para obtener información sobre el
[Desktop-packages] [Bug 2036315] Re: sol takes a long time to start
many thanks, your suggestion solved MY problem on MY system, but what about others? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Confirmed Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2041825] Re: Saving a wireguard VPN connection fails
oh indeed: loka 30 15:23:48 leon gnome-control-c[12423]: Failed to add connection: ipv4.method: method "auto" is not supported for WireGuard if it's not supported, then the option shouldn't be available -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2002882] Re: nautilus sometimes gets stuck when opening a folder and never shows the files inside
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2002882 Title: nautilus sometimes gets stuck when opening a folder and never shows the files inside Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Observed behaviour: open a directory (in my case, containing 20 photos, ~200 MB in total). Nautilus shows activity (the "Loading..." indicator is active and animated), but it just stays that way indefinitely (2-3 minutes now), without showing the files. Expected behaviour: Effectively immediately show the contents of a directory with ~20 files. Repeatability: infrequently, maybe 5% of the time Workarounds: go to the parent dir, come back to the subdirectory in question and its contents show up immediately, without issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 18:51:07 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'198' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-11-03 (72 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2002882/+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 2019885] Re: Printer ink level bars don't line up
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/2019885 Title: Printer ink level bars don't line up Status in gnome-control-center package in Ubuntu: Confirmed Bug description: See screenshot. I'd like to know the ink level in my laser printer. I can see the ink level in the gnome control center. However the colours look like they're not centred vertically. The ink levels are inside a losenge but don't fit perfectly vertically. There's a gap below the coloured bar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:28:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019885/+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 2019886] Re: Printer ink levels are incorrect
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High -- 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/2019886 Title: Printer ink levels are incorrect Status in gnome-control-center package in Ubuntu: New Bug description: I would like to see the printer ink levels of my printer. If I visit the gnome settings printer panel, I see lots of cyan, and a small amount of magenta, and a small amount of yellow. An unknown about of black is shown, perhaps in between magenta and yellow, or perhaps the bar after the yellow. I don't know. What's more concerning is the bars don't even line up with what the printer thinks the fill level is. Attached two screenshots. One of gnome settings, and one of the web UI for the printer. The ink levels don't correlate at all. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:31:08 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019886/+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 2036315] Re: sol takes a long time to start
When the error occurred, the date of the file was as follows. ls --time-style=full-iso -l /usr/lib/x86_64-linux- gnu/guile/3.0/ccache/ice-9/eval.go -rw-r--r-- 1 root root 99461 2023-10-16 20:06:20.0 +0900 /usr/lib/x86_64-linux- gnu/guile/3.0/ccache/ice-9/eval.go When running normally. ls --time-style=full-iso -l /usr/lib/x86_64-linux- gnu/guile/3.0/ccache/ice-9/eval.go -rw-r--r-- 1 root root 99461 2022-03-06 07:19:25.0 +0900 /usr/lib/x86_64-linux- gnu/guile/3.0/ccache/ice-9/eval.go -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Confirmed Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2041491] Re: Provide an option to avoid the yaml NM backend
Thank you for your thoughtful report! This change was not just made to be useful in cloud environments, but also is about unification of network configuration across the different variants of Ubuntu (Desktop/Server/Core/Cloud/..), to improve the UX for Ubuntu users. I understand this impacts the cross-distro compatibility of our NetworkManager packaging. If you want to manage your NM connection profiles manually, you could place the keyfiles in /usr/lib/NetworkManager/system-connections/ and NM will pick them up as before. But those connections would no be visible to Netplan and any modifications through the NetworKManager tooling (GUI, nmtui, nmcli, ...) would write the modifications to /etc/netplan/ instead of /etc/NetworkManager/system-connections/ -- 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/2041491 Title: Provide an option to avoid the yaml NM backend Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hi, recently netplan added support for a yaml NM backend: https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml- settings/32420 The rationale is that "the descriptive YAML layer is especially useful in cloud environments": https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556 It's great that you care about that user group! Please also care for the rest of us that do not use cloud environments! For example, I routinely review, clone, backup or even directly edit the /etc/NetworkManager/system-connections files in my desktops and servers, in all distributions. Having an Ubuntu-specific way to do things will make things harder for me. I will have to learn a new Ubuntu-specific syntax, develop scripts and methods to convert my connections between distributions, I will need to discover and report bugs in the netplan <=> nm mapping etc... I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide a unified yaml-based experience for cloud-init etc. But Ubuntu is also great outside the cloud; please allow us to continue having a unified experience between distributions (i.e. directly using nm or systemd-networkd) without enforcing an Ubuntu-specific way of doing things (netplan) to us. For Ubuntu 24.04+, please provide an option to avoid the yaml NM backend, thank you very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+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 2013115] Re: Bluetooth slider needs toggling two times to disconnect to device
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/2013115 Title: Bluetooth slider needs toggling two times to disconnect to device Status in gnome-control-center package in Ubuntu: New Bug description: OS: 23.04 gnome-control-center: 44.0-1ubuntu3 bluez: 5.66-0ubuntu1 bluez-obexd: 5.66-0ubuntu1 I use a common bose QC45 headset daily and if I want to disconnect the device, I need to click the toggle slider twice to actually get the headset to disconnect (I hear confirmation of this in the headset). On the first click, there are no journalctl logs. On the second click that actually disconnects the device, I see the expected: Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), (0xff) Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), Success(0x20) Mar 28 11:21:39 fenrir obexd[5665]: disconnected: Transport got disconnected I would expect to only have to click the slider once to disconnect from the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2013115/+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 2036315] Re: sol takes a long time to start
This problem seems to occur because the file dates of the aisleriot and guile-3.0-libs packages are different when the system time is not set properly. I solved it like this: 1. dpkg-reconfigure tzdata 2. apt reinstall aisleriot 3. sudo apt reinstall guile-3.0-libs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Confirmed Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2036315] Re: sol takes a long time to start
You need to run the command like this. 1. sudo dpkg-reconfigure tzdata 2. sudo apt reinstall aisleriot 3. sudo apt reinstall guile-3.0-libs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Confirmed Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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
Testing 1:45.0-1ubuntu3 on mantic the privacy panel shows correctly a devices section including thunderbolt and security and those panels are working as expected, marking as verified ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- 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: Fix Released Status in gnome-control-center source package in Mantic: Fix Committed 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 1993327] Re: Misalignment of label alongside Icon size slider under Ubuntu Desktop page
** Tags added: desktop-lts-wishlist -- 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/1993327 Title: Misalignment of label alongside Icon size slider under Ubuntu Desktop page Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In System Settings, the label alongside the Icon size slider under Ubuntu Desktop page is misaligned with the slider, as shown in the attached screenshot. It is placed a bit too low from the position of the slider. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 19:58:27 2022 InstallationDate: Installed on 2022-09-24 (24 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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/1993327/+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 2012757] Re: Incorrect total system memory
Thank you for your bug report. Could you change the units format in the settings and see if that makes a difference? ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2012757 Title: Incorrect total system memory Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: Gnome System Monitor has been incorrectly showing the amount of RAM for some time (months?). Based on the system logs, I was able to determine that Gnome System Monitor has not been updated recently. So where is the incorrect data coming from? Gnome System Monitor: RAM: 33.5 GB SWAP: 1.5 GB $ free totalusedfree shared buff/cache available Mem:3270654012241184 5677344 122342814788012 11034196 Swap:1459904 0 1459904 Everything indicates that Gnome System Monitor as RAM, gives the amount of RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM. In addition, SWAP is shown separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2012757/+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 1948539] Re: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.
You can change the units in the settings ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1948539 Title: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: System Monitor is showing wrong Memory info. Actual is 8(7.6) GB showing 8.2 GB. Current OS version - Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1948539/+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 1991827] Re: No mp3/mkv thumbnails
totem-video-thumbnailer should be doing the previews, do you have totem installed? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1991827 Title: No mp3/mkv thumbnails Status in nautilus package in Ubuntu: New Bug description: .mp3 and .mkv files shown on desktop and in the file explorer, have the default icon (of their respective file type), instead of a thumbnail, as in previous Ubuntu versions (at least 16.04 and before): For mp3 files the embedded image (e.g. album cover), and for mkv files a snapshot of the video. If this is intentional behavior, it would be nice if you could provide a toggle switch or something, giving user the option to view each file's thumbnail (as in 16.04 for example), or keep seeing the default icon. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-oem-5.17-headers-5.17.0-1014_5.17.0-1014.15_all.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Oct 5 20:13:18 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2022-10-03 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1991827/+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 1988422] Re: Bluetooth discoverability is not communicated to the user adequately in Settings
The sharing is from gnome-user-share and it's supposed to display a notification when a file is received, if you aren't getting one you should report a new bug -- 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/1988422 Title: Bluetooth discoverability is not communicated to the user adequately in Settings Status in gnome-control-center package in Ubuntu: Confirmed Bug description: When bluetooth is turned on ubuntu it is discoverable to all nearby devices. It's strange that any "dumb" bluetooth device offers the option to be turned on but not be discoverable, but gnome bluetooth manager doesn't offer such option. Any device can be paired with a device using the gnome desktop, as long as the user gets the prompt to pair. After that, gnome desktop can receive any file to the downloads folder. There should be an option to make the gnome desktop device not show up to other devices, and another one to restrict what files can be sent via BT to the downloads folder ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgnome-bluetooth13 3.34.5-8 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 12:12:16 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth 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/1988422/+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 1990005] Re: Visible columns option missing function
The issue should be fixed in the current version ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2496 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nautilus (Ubuntu) Assignee: Eugenio (thsgiannotti) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1990005 Title: Visible columns option missing function Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1990005/+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 1990785] Re: Extracting files larger than 4 GB doesn't seem to work in .iso
Reported upstream as https://gitlab.gnome.org/GNOME/file- roller/-/issues/186 but which got closed because of the version used ** Bug watch added: gitlab.gnome.org/GNOME/file-roller/-/issues #186 https://gitlab.gnome.org/GNOME/file-roller/-/issues/186 ** Changed in: file-roller (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1990785 Title: Extracting files larger than 4 GB doesn't seem to work in .iso Status in file-roller package in Ubuntu: New Bug description: Hello. I use Linux Mint 20.3 (based on Ubuntu Focal 20.04). This distribution contains the version 3.36.3, via APT. When I try to extract an .iso with large files inside, they are ignored (not even listed) when an iso is opened and its contents are extracted. I have found that files larger than 4 GB generally cause this problem. The program should be able to list and extract all the contents inside an .iso file regardless of its size. The .iso in question were created by using Brasero, on the same distribution. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1990785/+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 1990786] Re: File Roller should indicate compression/extraction speed and estimated remaining time
** Changed in: file-roller (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1990786 Title: File Roller should indicate compression/extraction speed and estimated remaining time Status in file-roller package in Ubuntu: New Bug description: Hello. I use Linux Mint 20.3 (based on Ubuntu Focal 20.04). This distribution contains the version 3.36.3, via APT. When I compress or extract some file. The program only indicates the total remaining files, but this number is invariable. The progress line doesn't work, no compression/extraction speed or no estimated time remaining are shown either. I think the program should provide useful information in the user interface. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1990786/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
Unsubscribing since I'm not working on that issue ** Changed in: freerdp2 (Ubuntu) Assignee: Sebastien Bacher (seb128) => (unassigned) ** Changed in: freerdp2 (Ubuntu Jammy) Assignee: Sebastien Bacher (seb128) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: Incomplete Status in freerdp2 source package in Jammy: Incomplete Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1986845] Re: "send to" with thunderbird snap
On mantic the situation is different because nautilus uses the email portal now which add attachments by crafting a mailto: url, which thunderbird doesn't handle, see https://github.com/flatpak/xdg-desktop- portal-gtk/pull/447 -- 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/1986845 Title: "send to" with thunderbird snap Status in thunderbird package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1986845/+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 2041825] Re: Saving a wireguard VPN connection fails
Wireguard is listed correctly here... -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2041825] Re: Saving a wireguard VPN connection fails
Thank you for your bug report. Could you check if there are any warning displayed in the journal? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2041737] Re: apport-collect permission error on retrieving boot.log
I have not found boot.log in the apport source code, but it is mentioned
two package hooks:
grep boot.log /usr/share/apport/ -r
/usr/share/apport/package-hooks/source_xorg.py:
attach_file_if_exists(report, '/var/log/boot.log', 'BootLog')
/usr/share/apport/package-hooks/source_xorg.py:
report['xserver.logfile'] = xlog.boot_logfile
/usr/share/apport/package-hooks/source_plymouth.py:attach_file(report,
'/var/log/boot.log', 'BootLog')
They use attach_file or attach_file_if_exists. They need to use
root_command_output instead.
** Package changed: apport (Ubuntu) => plymouth (Ubuntu)
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
** Changed in: xorg (Ubuntu)
Status: New => Triaged
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
** Changed in: xorg (Ubuntu)
Importance: Undecided => Medium
--
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/2041737
Title:
apport-collect permission error on retrieving boot.log
Status in plymouth package in Ubuntu:
Triaged
Status in xorg package in Ubuntu:
Triaged
Bug description:
RE: Bug Report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2041736
While reviewing this Bug Report, to add a comment to help explain something
for this user, i noticed this error from apport collect:
...
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
...
This file is needed by Launchpad for diagnostics.
Just this week, I helped a Forum user review his boot.log files, so I am
familiar with this. The permissions and ownership of the boot.log.X files are
currently:
mafoelffen@Mikes-B460M:~$ ls -l /var/log/boot*
-rw--- 1 root root 0 Oct 16 00:00 /var/log/boot.log
-rw--- 1 root root 101106 Oct 16 00:00 /var/log/boot.log.1
-rw--- 1 root root 50432 Oct 14 00:00 /var/log/boot.log.2
-rw--- 1 root root 201696 Oct 12 00:00 /var/log/boot.log.3
-rw--- 1 root root 50375 Oct 10 00:00 /var/log/boot.log.4
-rw--- 1 root root 50497 Oct 9 00:00 /var/log/boot.log.5
-rw--- 1 root root 1598 Sep 29 00:00 /var/log/boot.log.6
-rw--- 1 root root 26496 Sep 28 19:10 /var/log/boot.log.7
-rw-r--r-- 1 root root 108494 Apr 19 2022 /var/log/bootstrap.log
...
Which means the 'root' is only user that can open or view them.
Examples:
...
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ awk 'NR>3{exit} {print $0}'
/var/log/boot.log
awk: fatal: cannot open file `/var/log/boot.log' for reading: Permission
denied
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ sudo awk 'NR>3{exit} {print $0}'
/var/log/boot.log
Sat Jul 22 00:27:04 PDT 2023
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password R…s to Plymouth Directory Watch.
...
That is why I think apport-collect is getting permissions errors and
failing to retrieve the user boot.log for upload.
Expected behavior:
apport-collect should upload the boot.log successfully.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
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
CurrentDesktop: GNOME
Date: Sat Oct 28 20:44:58 2023
InstallationDate: Installed on 2021-09-23 (765 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-08-17 (438 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2041737/+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 2041737] [NEW] apport-collect permission error on retrieving boot.log
You have been subscribed to a public bug:
RE: Bug Report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2041736
While reviewing this Bug Report, to add a comment to help explain something for
this user, i noticed this error from apport collect:
...
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
...
This file is needed by Launchpad for diagnostics.
Just this week, I helped a Forum user review his boot.log files, so I am
familiar with this. The permissions and ownership of the boot.log.X files are
currently:
mafoelffen@Mikes-B460M:~$ ls -l /var/log/boot*
-rw--- 1 root root 0 Oct 16 00:00 /var/log/boot.log
-rw--- 1 root root 101106 Oct 16 00:00 /var/log/boot.log.1
-rw--- 1 root root 50432 Oct 14 00:00 /var/log/boot.log.2
-rw--- 1 root root 201696 Oct 12 00:00 /var/log/boot.log.3
-rw--- 1 root root 50375 Oct 10 00:00 /var/log/boot.log.4
-rw--- 1 root root 50497 Oct 9 00:00 /var/log/boot.log.5
-rw--- 1 root root 1598 Sep 29 00:00 /var/log/boot.log.6
-rw--- 1 root root 26496 Sep 28 19:10 /var/log/boot.log.7
-rw-r--r-- 1 root root 108494 Apr 19 2022 /var/log/bootstrap.log
...
Which means the 'root' is only user that can open or view them.
Examples:
...
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ awk 'NR>3{exit} {print $0}'
/var/log/boot.log
awk: fatal: cannot open file `/var/log/boot.log' for reading: Permission denied
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ sudo awk 'NR>3{exit} {print $0}'
/var/log/boot.log
Sat Jul 22 00:27:04 PDT 2023
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password R…s to Plymouth Directory Watch.
...
That is why I think apport-collect is getting permissions errors and
failing to retrieve the user boot.log for upload.
Expected behavior:
apport-collect should upload the boot.log successfully.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
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
CurrentDesktop: GNOME
Date: Sat Oct 28 20:44:58 2023
InstallationDate: Installed on 2021-09-23 (765 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-08-17 (438 days ago)
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
apport-collect permission error on retrieving boot.log
https://bugs.launchpad.net/bugs/2041737
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth 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 2032852] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
Seem to have managed to fix this - using 'Old Engineers Intuition'. I had upgraded from 18 to Ubuntu 20.04.6 LTS - during which a number of issues popped up, which I agreed to be passed back. After installation, nothing in libreoffice would work. One error window advised "sudo apt-get install -f" - which simply returned faults on libreoffice-common. Running "sudo apt --fix-broken install" did not work either. Looking at "sudo apt" in Terminal, I came across "sudo apt satisfy", which seemd worth trying as "sudo apt satisfy libreoffice-common". A lot of stuff happened, which concluded with no errors. I re-ran "sudo apt --fix-broken install" and then "sudo apt autoremove" which both had nothing to do! Running "sudo apt-get install -f" returned OK, so I rebooted; libreoffice ran in recovery mode; recovered; and I am now back in business! -- 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/2032852 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: In Progress Bug description: package install error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 24 02:36:52 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2032852/+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 2041825] [NEW] Saving a wireguard VPN connection fails
Public bug reported: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/2041825 Title: Saving a wireguard VPN connection fails Status in gnome-control-center package in Ubuntu: New Bug description: Adding a new Wireguard VPN connection fails as it isn't shown on the GUI under "VPN" (like openvpn connection is). this is on 23.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 2041813] [NEW] headset mic not working
Public bug reported: When I plugin a headset, the mic on the headset is not working. audio input is still via laptop built-in mic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gle2040 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 16:42:43 2023 InstallationDate: Installed on 2020-05-02 (1276 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to jammy on 2022-08-12 (443 days ago) dmi.bios.date: 08/12/2019 dmi.bios.release: 1.9 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:br1.9:efr1.9:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130:skuC233: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2041813 Title: headset mic not working Status in pulseaudio package in Ubuntu: New Bug description: When I plugin a headset, the mic on the headset is not working. audio input is still via laptop built-in mic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gle2040 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 16:42:43 2023 InstallationDate: Installed on 2020-05-02 (1276 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to jammy on 2022-08-12 (443 days ago) dmi.bios.date: 08/12/2019 dmi.bios.release: 1.9 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:br1.9:efr1.9:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130:skuC233: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2041813/+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 2041491] Re: Provide an option to avoid the yaml NM backend
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Tags added: netplan-everywhere ** Tags added: rls-nn-incoming -- 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/2041491 Title: Provide an option to avoid the yaml NM backend Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hi, recently netplan added support for a yaml NM backend: https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml- settings/32420 The rationale is that "the descriptive YAML layer is especially useful in cloud environments": https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556 It's great that you care about that user group! Please also care for the rest of us that do not use cloud environments! For example, I routinely review, clone, backup or even directly edit the /etc/NetworkManager/system-connections files in my desktops and servers, in all distributions. Having an Ubuntu-specific way to do things will make things harder for me. I will have to learn a new Ubuntu-specific syntax, develop scripts and methods to convert my connections between distributions, I will need to discover and report bugs in the netplan <=> nm mapping etc... I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide a unified yaml-based experience for cloud-init etc. But Ubuntu is also great outside the cloud; please allow us to continue having a unified experience between distributions (i.e. directly using nm or systemd-networkd) without enforcing an Ubuntu-specific way of doing things (netplan) to us. For Ubuntu 24.04+, please provide an option to avoid the yaml NM backend, thank you very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+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 2041789] Re: amd 7840, ubuntu 22.04, display goes to wrong
** 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/2041789 Title: amd 7840, ubuntu 22.04, display goes to wrong Status in xorg package in Ubuntu: New Bug description: release version: Ubuntu 22.04.3 LTS kernel: linux-oem-22.04d, others just the default of the official release, with update the screen display goes to white or black or full of stripe, but I can still move the pointer. I can restore the display by lock and unlock the screen. there is a photo attached. I have test the default kernel or linux-oem-22.04c linux-oem-22.04d, the problem dont go away. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1004.4-oem 6.5.3 Uname: Linux 6.5.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 13:16:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1004-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2041789/+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 2041789] [NEW] amd 7840, ubuntu 22.04, display goes to wrong
You have been subscribed to a public bug: release version: Ubuntu 22.04.3 LTS kernel: linux-oem-22.04d, others just the default of the official release, with update the screen display goes to white or black or full of stripe, but I can still move the pointer. I can restore the display by lock and unlock the screen. there is a photo attached. I have test the default kernel or linux-oem-22.04c linux-oem-22.04d, the problem dont go away. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1004.4-oem 6.5.3 Uname: Linux 6.5.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 13:16:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1004-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu wayland-session -- amd 7840, ubuntu 22.04, display goes to wrong https://bugs.launchpad.net/bugs/2041789 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 1261351] Re: "Save All" for same-named attachments defaults to only one saved file
So you had time to go through like 3 (THREE!) full major UI redesigns
since this was first posted, but *this* was low priority to you? This
thing that people actually need? With a "fix" that wastes people's time?
--
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/1261351
Title:
"Save All" for same-named attachments defaults to only one saved file
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
thunderbird 1:24.2.0+build1-0ubuntu0.13.10.1, Ubuntu 13.10
1. Send yourself a message containing more than one attachment with the same
filename, e.g. "image.jpeg".
2. Open the message in Thunderbird, and choose "Save All".
3. Select a folder to save the attachments in, and choose "Open" [sic].
What happens: For n attachments, n–1 "Confirm" alerts appear with the
text: "{pathname} already exists. Do you want to replace it?"
If you choose "Cancel", a "Save Attachment" dialog appears for
choosing a different path/filename.
But the default is "OK", and if you choose that each attachment
overwrites the previous one, something that nobody would ever want.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1261351/+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 1828123] Re: File names are percent-encoded when connect to webdav server
The issue is an nginx one ** Package changed: nautilus (Ubuntu) => nginx (Ubuntu) ** Also affects: nginx Importance: Undecided Status: New ** Bug watch added: trac.nginx.org/nginx/ #970 http://trac.nginx.org/nginx/ticket/970 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828123 Title: File names are percent-encoded when connect to webdav server Status in Nautilus: Fix Released Status in Nginx: New Status in nginx package in Ubuntu: Triaged Bug description: When I connected to a Webdav server set up by nginx using the default file manager, some non-English characters in file and folder names are displayed as percent-encoded(url-encoded). For example, "%E4%B8%8D%E5%AE%89%E4%B8%8E%E6%AC%B2%E6%9C%9B" is displayed instead of "不安与欲望", and the " "(space) in a file name is displayed as "%20". Once I copied those files to local disk, the file names are displayed correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1828123/+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 2041716] Re: [SRU] libreoffice 7.5.8 for lunar
** Description changed: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz * [riscv64] not available - * [s390x] ... + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2041716 Title: [SRU] libreoffice 7.5.8 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests
