[Bug 2066516] Re: fractional scaling corrupts the monitors.xml file
(I hope I have identified the correct package, but not 100% sure I figured out the correct one.) ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2066516 Title: fractional scaling corrupts the monitors.xml file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2066516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066516] [NEW] fractional scaling corrupts the monitors.xml file
You have been subscribed to a public bug: Ubuntu 22.04.4, gnome shell 42.9, wayland (per the "About" screen under Ubuntu settings). I have two monitors, I set the fractional scaling on each to be 125%. Each has a resolution of 1920 X 1080. On the left monitor, I have an icon on the desktop appearing in the middle of the monitor. I can move it around on that monitor, but: Something strange happens if I try to move it to one of the three rightmost "columns" of that left monitor. If I try to move it to one of those three rightmost columns on the left monitor, it ends up in one of the three leftmost columns of the right monitor. (But: Attempting to place an icon in one of the three leftmost columns of the right monitor does NOT place it in one of the three rightmost columns of the left monitor - In this case the icon stays on the right monitor where I intend for it to be.) Don't have this problem when the resolution is set at the default of 100% on each monitor. I have the resolution on each monitor to be 1920 X 1080. When I leave the fractional scaling - under the Ubuntu settings display option - at the default of 100%, in the monitors.xml file the x,y coordinates for the two monitors are exactly as I'd expect them to be: viz., 0,0 for the left monitor, and 1920,0 for the right monitor. However, when I change that fractional scaling setting from 100% to 125% on each monitor, and leave the resolution on each monitor at 1920 X 1080, the x,y coordinates automatically get changed to 0,0 and 1536,0. My simplistic understanding is that this change effectively makes the left monitor get cutoff at 1536 instead of at 1920, basically moving the rightmost 20% of that monitor's x dimension to be treated as part of the right monitor's x dimension. If I manually fix the x,y coordinates in the monitors.xml file, then at next reboot the fractional scaling is automatically reset to 100% on each monitor. I obviously do not understand the relationship between fractional scaling and monitor dimensions in the monitors.xml file. (Incidentally, in gnome tweaks under the font setting I have throughout all this left the scaling option at the default of 1.0. Don't know how, if at all, that interacts with the fractional scaling in the Ubuntu settings.) Why is this happening? How do I fix this problem? ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- fractional scaling corrupts the monitors.xml file https://bugs.launchpad.net/bugs/2066516 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Autopkgtest regression report (systemd/255.4-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: 389-ds-base/unknown (armhf, s390x) aide/unknown (s390x) amavisd-new/unknown (s390x) apport/2.28.1-0ubuntu3 (arm64) apport/unknown (s390x) appstream/unknown (s390x) apt/2.7.14build2 (armhf) apt/unknown (s390x) asterisk/unknown (s390x) at-spi2-core/unknown (s390x) ayatana-indicator-session/unknown (s390x) bind9/unknown (amd64, armhf, i386, s390x) bolt/unknown (amd64, s390x) casper/unknown (s390x) casync/unknown (s390x) ceph/unknown (s390x) clamav/unknown (amd64) clevis/unknown (s390x) cloudflare-ddns/unknown (s390x) clutter-1.0/unknown (amd64) cockpit/unknown (s390x) collectd/unknown (s390x) colord/unknown (s390x) comitup/unknown (amd64, s390x) conntrack-tools/unknown (amd64) corosync/3.1.7-1ubuntu3 (arm64) corosync/unknown (s390x) corosync-qdevice/unknown (amd64, s390x) coturn/unknown (armhf, s390x) cron/unknown (ppc64el, s390x) crun/unknown (amd64, s390x) cryptsetup/2:2.7.0-1ubuntu4 (arm64) csync2/unknown (amd64, s390x) cups/unknown (amd64, s390x) dbus/1.14.10-4ubuntu4 (i386) dbus/unknown (amd64, armhf, s390x) dbus-broker/unknown (amd64, s390x) debos/unknown (amd64) dhcpcd/unknown (armhf, s390x) dlm/unknown (amd64) dovecot/unknown (amd64) dpdk/23.11-1build3 (amd64) dq/20240101-1 (amd64) exim4/unknown (amd64, armhf) expeyes/unknown (amd64) fcgiwrap/unknown (amd64) fluidsynth/unknown (amd64, i386) freedom-maker/unknown (amd64, armhf, i386) freedombox/unknown (amd64) freeradius/unknown (amd64) fwupd/unknown (amd64) gamemode/unknown (i386) gdm3/unknown (amd64) golang-github-coreos-go-systemd/unknown (amd64) gpsd/unknown (amd64) gvfs/unknown (s390x) haproxy/unknown (amd64) hddemux/unknown (amd64) hwloc/unknown (amd64, s390x) incus/unknown (amd64) init-system-helpers/unknown (amd64) initramfs-tools/unknown (amd64) interception-tools/unknown (amd64) janus/unknown (amd64) keyman/unknown (amd64) knot/unknown (amd64) knot-resolver/unknown (amd64) libcamera/0.2.0-3fakesync1build6 (amd64, armhf) libei/1.2.1-1 (amd64) libinput/unknown (amd64) liblinux-systemd-perl/unknown (amd64) libreswan/unknown (amd64) libsdl2/unknown (amd64) libsfml/2.6.1+dfsg-2build2 (armhf) libsfml/unknown (amd64) libsoup2.4/2.74.3-6ubuntu1 (ppc64el) libsoup2.4/unknown (amd64) libsoup3/unknown (amd64) libusbauth-configparser/unknown (amd64) libvirt/unknown (amd64) lighttpd/unknown (amd64) linux-ibm/unknown (amd64) logiops/unknown (amd64) logrotate/unknown (amd64) mariadb/unknown (amd64) mediawiki/unknown (amd64) mir/unknown (amd64) mkosi/unknown (amd64) monitoring-plugins-systemd/unknown (amd64) mosquitto/unknown (amd64) multipath-tools/unknown (amd64) munin/unknown (amd64) mutter/unknown (amd64) nagios-tang/unknown (amd64, s390x) ndctl/unknown (armhf, s390x) network-manager/unknown (amd64, s390x) nextepc/unknown (amd64) nix/unknown (amd64, armhf) nut/unknown (amd64, armhf, s390x) open-build-service/unknown (amd64) openssh/unknown (amd64) openvpn/unknown (amd64) openzwave/unknown (amd64) ovn/unknown (amd64) pam/unknown (amd64, i386) pdns-recursor/unknown (amd64) pgagroal/unknown (amd64) pgbouncer/unknown (amd64) pglistener/unknown (amd64) php8.3/unknown (amd64) pipewire/unknown (amd64) policykit-1/unknown (amd64) polkit-qt-1/unknown (amd64) postgresql-16/unknown (amd64, s390x) procps/unknown (armhf) prometheus-homeplug-exporter/unknown (armhf) prometheus-postfix-exporter/0.3.0-4build1 (armhf) pulseaudio/unknown (amd64) puppet-agent/unknown (armhf) pystemd/0.13.2-1build2 (armhf) pystemd/unknown (amd64, s390x) python-dbusmock/unknown (s390x) python-sdbus/unknown (s390x) python-systemd/unknown (s390x) pyudev/unknown (amd64, s390x) qlcplus/unknown (amd64, armhf, s390x) rbldnsd/unknown (amd64, armhf, s390x) redis/unknown (amd64) remctl/unknown (amd64, s390x) rsyslog/8.2312.0-3ubuntu9 (amd64) rtkit/unknown (s390x) rust-whoami/unknown (amd64) samba/2:4.19.5+dfsg-4ubuntu9 (arm64) samba/unknown (s390x) seatd/unknown (i386) shibboleth-sp/unknown (s390x) sks/unknown (s390x) smcroute/unknown (amd64, s390x) snapd/unknown (s390x) squid/unknown (s390x) sssd/unknown (amd64) stayrtr/unknown (s390x) strongswan/unknown (amd64, arm64) stunnel4/unknown (amd64) tgt/unknown (amd64, s390x) tinyssh/20240101-2 (arm64, s390x) tinyssh/unknown (amd64) tmux/unknown (s390x) tpm2-abrmd/unknown (amd64, s390x) udisks2/unknown (amd64) umockdev/unknown (amd64, s390x) upower/1.90.3-1 (armhf) upower/unknown (s390x) usbauth/unknown (amd64, s390x) util-linux/unknown (amd64) vlc/3.0.20-3build6 (arm64) vlc/unknown (i386) weston/unknown (amd64) yder/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/noble/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
[Bug 1876716] Re: Error transferring track: "could not open resource for writing" when copying tracks to library
I am currently having this problem ...again. It is with a single disk I am trying to extract. Ubuntu 22.04.2 LTS RhythmBox 3.4.4 There is no other instance of the files anywhere in the directories I am attempting to send the extraction. The file names are all within the legal characters (which I have had problems with in the past). I have 1.x TB of space on the drive. I can play the CD with RhythmBox, but it won't extract. I have been extracting files all morning till I hit this one CD. I will continue extracting files if the program will permit with 'other' CD's. Is this a problem if the CD has DRM protection on it? I don't think this CD does, but sometimes one never knows. And, if so, is there a way to find out? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1876716 Title: Error transferring track: "could not open resource for writing" when copying tracks to library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1876716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation
+1 for @ and @home by default. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1881932 Title: subiquity isn't able to create btrfs subvolumes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1881932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012954] Re: drag and drop files via hot corner Activities Overview don't work anymore
Here is the bug report on gitlab https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6677 Still present for me in Ubuntu 24.04 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6677 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6677 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012954 Title: drag and drop files via hot corner Activities Overview don't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
In Ubuntu 22.04.4 with NVidia driver 535.171.04 and windowing system X11, I downloaded and installed the packages recommended in #135: after a reboot, my terminal was fixed. Thank you @vanvugt! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
I have verified the fix using systemd 255.4-1ubuntu8.1 from noble- proposed. On a Jammy Desktop system, I simply ran an upgrade: nr@clean-jammy-amd64:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-22 11:45:16-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.36, 91.189.91.83, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: \u2018noble.tar.gz\u2019 noble.tar.gz100%[===>] 1.21M --.-KB/sin 0.1s 2024-05-22 11:45:16 (9.20 MB/s) - \u2018noble.tar.gz\u2019 saved [1274850/1274850] nr@clean-jammy-amd64:~$ tar xf noble.tar.gz nr@clean-jammy-amd64:~$ sudo -E ./noble --frontend DistUpgradeViewNonInteractive [ ... ] The upgrade proceeded without issue. Namely, my session was not killed during the upgrade. nr@clean-jammy-amd64:~$ apt policy systemd systemd: Installed: 255.4-1ubuntu8.1 Candidate: 255.4-1ubuntu8.1 Version table: *** 255.4-1ubuntu8.1 500 500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065136] Re: Throwing error while tiling a window [Error in size change accounting.]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2065136 Title: Throwing error while tiling a window [Error in size change accounting.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2065136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065136] Re: Throwing error while tiling a window [Error in size change accounting.]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2065136 Title: Throwing error while tiling a window [Error in size change accounting.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2065136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
I enabled jammy-proposed, as well as following the guide on https://wiki.ubuntu.com/Testing/EnableProposed to enable selective upgrading from proposed, then ran the following command: sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy- proposed mutter-common/jammy-proposed This installed the same set of packages mentioned in #135. After a reboot, all of my issues with the terminal seem to have gone away. So the fix looks good from here. Anyone planning to install this fix from proposed should enable selective upgrading unless they want to test every package currently in proposed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066391] Re: Non-admin user cannot connect to new WiFi networks
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2066391 Title: Non-admin user cannot connect to new WiFi networks To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2066391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066391] [NEW] Non-admin user cannot connect to new WiFi networks
Public bug reported:
An admin password is required to connect to new Wifi networks.
This is through both quick-settings(gnome-shell) and the
Settings(gnome-control-center) app.
Steps to reproduce:
- Set up Ubuntu Desktop as normal
- Create a new standard user
- Login as the new user and try to connect to a new WiFi network
- Error: "System policy prevents modification of network settings for all
users"
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu 24.04 LTS
Release:24.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
gnome-shell:
Installed: 46.0-0ubuntu5.1
Candidate: 46.0-0ubuntu5.1
3) What you expected to happen
A standard(non-admin) user should be able to create new WiFi connections
(This probably extends to all types of connections like VPN, but I haven't
tested it)
4) What happened instead
The standard user is prompted for admin credentials to connect to new
Wifi networks.
The original report by Jan Schär (@jschaer) says gnome-control-center
allowed to create `personal` connections, but this does not seem to be
true for at least Noble.
Upstream report:
When connecting to a new WiFi in the gnome-shell quick settings as a
non-admin user, an admin password is requested ("System policy prevents
modification of network settings for all users"). However, connecting to
a WiFi in gnome-control-center works without an admin password, and a
connection is created only for the current user.
Here is the logic for this in gnome-control-center:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/e6978a480110ad5e24d3b34107675eb03fa3cc31/panels/network/net-device-wifi.c#L491-506
This logic is missing in gnome-shell:
https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/8a048190b99c7d34a319f41f0a980e388a0ba86e/js/ui/status/network.js#L963
I think gnome-shell should do the same as gnome-control-center is doing,
and create a non-shared connection if there is no permission to create a
shared one.
(from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7378)
** Affects: gnome-shell
Importance: Unknown
Status: Unknown
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7378
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7378
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7378
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2066391
Title:
Non-admin user cannot connect to new WiFi networks
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2066391/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066388] Re: decimal point gnored with LC_NUMERIC=it_IT.UTF-8
Problem does not depend from kernel 6.9, but is the same with standard 24.04 kernel 6.8.0-31-generic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2066388 Title: decimal point gnored with LC_NUMERIC=it_IT.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2066388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066388] [NEW] decimal point gnored with LC_NUMERIC=it_IT.UTF-8
Public bug reported: In Ubuntu 24.04 gnome-calculator: Installato: 1:46.0-1ubuntu1 with italian keyboard and LC_NUMERIC=it_IT.UTF-8 ignores decimal point entered from numeric keypad ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calculator 1:46.0-1ubuntu1 Uname: Linux 6.9.0-060900rc7-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 22 16:47:49 2024 InstallationDate: Installed on 2024-05-04 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2066388 Title: decimal point gnored with LC_NUMERIC=it_IT.UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2066388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061728] Re: Apps don't launch from GNOME Software
Does this bug need any further info? https://askubuntu.com/questions/1513001/why-am-i-getting-this-flatpak- error-ldconfig-failed-exit-status-256-with- ever?noredirect=1#comment2658361_1513001 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2061728 Title: Apps don't launch from GNOME Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2061728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
>You don't really need to enable jammy-proposed. Just download the 3 proposed packages: I first tried to install these 3 packages, albeit not with the suggested method of installing them all at once as a bundle with the dpkg command proposed by Daniel, and I ended up with a broken desktop (was getting some “Failed to start VirtualBox Linux kernel module…” errors on boot), which I fixed running sudo apt install --reinstall ubuntu-gnome- desktop). Enabling jammy-proposed seems to have fixed the issue though. Thanks! Using 550.78 nvidia driver -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2056772] Re: Properties of Audio Files Causes Lock Ups
@Khalid, ack and thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2056772 Title: Properties of Audio Files Causes Lock Ups To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2056772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064192] Re: Unable to resize windows
same problem here with programs e. g. libreoffice, geany ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066315] Autopkgtest regression report (gjs/1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2)
All autopkgtests for the newly accepted gjs (1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gjs/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#gjs [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2066315 Title: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2066315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
Hello Daniel, or anyone else affected, Accepted systemd into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066352] [NEW] Desktop session crashes randomly
Public bug reported: On a test laptop running Ubuntu 24.04, I am occasionally seeing my desktop session crash and return to the login screen. I haven't identified a pattern for these crashes yet but seems to occur randomly regardless of which app i have open or if I'm interacting with the system or it's idle. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 22 10:38:31 2024 DisplayManager: gdm3 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "This journalctl log contains logs for the most recent crash. Crash occurred at around 10:05AM" https://bugs.launchpad.net/bugs/2066352/+attachment/5781146/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2066352 Title: Desktop session crashes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2066352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066348] [NEW] crash post virtual box and wine installation
Public bug reported: slow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 22 10:29:38 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-05 (229 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 42.9-0ubuntu7.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2066348 Title: crash post virtual box and wine installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2066348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066062] Re: Impossible to select item using keyboard if folder has only one item
** Changed in: nautilus (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066062 Title: Impossible to select item using keyboard if folder has only one item To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2066062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065726] Re: gimp crash
That is most likely bug 2055044, even though the trace is missing some of the more characteristic entries. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2065726 Title: gimp crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2065726/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066209] Re: GIMP crashed unexpectedly
*** This bug is a duplicate of bug 2055044 *** https://bugs.launchpad.net/bugs/2055044 ** This bug has been marked a duplicate of bug 2055044 GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2066209 Title: GIMP crashed unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2066209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066062] Re: Impossible to select item using keyboard if folder has only one item
** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2066062 Title: Impossible to select item using keyboard if folder has only one item To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2066062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12154] Re: Nautilus should have a superuser mode
Indeed it was fixed by the admin backend that landed some cycles ago ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/12154 Title: Nautilus should have a superuser mode To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/12154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066309] Re: freezing, acting eratic
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2066309 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. I've marked this report as INCOMPLETE, as no release details, package details etc were provided. Once you've run the `apport-collect` command on your box, please return the status to "New". ** Changed in: gimp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2066309 Title: freezing, acting eratic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2066309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066310] Re: freezing, acting eratic
*** This bug is a duplicate of bug 2066309 *** https://bugs.launchpad.net/bugs/2066309 ** This bug has been marked a duplicate of bug 2066309 freezing, acting eratic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2066310 Title: freezing, acting eratic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2066310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2066203] [NEW] Libraries compiled without Shadow Stack support
Am Mon, 20 May 2024 23:51:15 - schrieb Marcos Alano <2066...@bugs.launchpad.net>: > [6399376a4e90] main audio output warning: cannot load module `/usr/lib/x86_64-linux-gnu/vlc/plugins/audio_output/libpulse_plugin.so' (/lib/x86_64-linux-gnu/libmpg123.so.0: rebuild shared object with SHSTK support enabled) Regarding libmpg123, you either need to disable assembly optimizations (build with generic decoders only), I presume, or someone provide a patch that adds SHSTK to them. I don't know which implementation of shadow stacks glibc/gcc is using in that setup. I've read up on the concept and so far only figured that this is part of a spiral that complicates ABI and makes providing assembly-optimized functions ever harder. This would be fine if compilers finally would be smart enough to evade the need to do so. Last time I checked, hand-tuned AVX decoding was still a lot more efficient. We already handle IBT, I think, with indirect jumps landing only in C wrapper functions. I wonder if we could also limit the shadow stack impact to those with some compiler/linker flags. The assembly routines are rather strict math, many years old now without much of attack surface. All parsing of input is before them in C. They just do lots of multiplication/addition. One might try to write a set of optimizations using intrinsics for modern CPUs that then also get the treatment of shadow stacks or the next shiny security measure. Porting the AVX code to GCC (and/or other) inline ASM might also work for some platforms. (Still, I am wondering why pulseaudio output should need MPEG decoding.) Alrighty then, Thomas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/2066203 Title: Libraries compiled without Shadow Stack support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/2066203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066315] Re: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored
Hello Marco, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2066315 Title: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2066315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
