[Bug 2072792] Re: Several python errors when updating/upgrading. Started after upgrading to 24.04.
Don't know why it was happening, but it was only for the App Grid app. I hardly use it anyway, so I deleted it. Error gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072792 Title: Several python errors when updating/upgrading. Started after upgrading to 24.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2072792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072792] [NEW] Several python errors when updating/upgrading. Started after upgrading to 24.04.
Public bug reported: File "/usr/share/appgrid/appdata.py", line 167, in rebuild_db() File "/usr/share/appgrid/appdata.py", line 62, in rebuild_db for pkgname in get_apt_pkgnames(): ^^ File "/usr/share/appgrid/appdata/apps/aptapp.py", line 250, in get_apt_pkgnames is_digits(ij.split(base)[1])) or ^^ ValueError: empty separator Traceback (most recent call last): File "/usr/share/appgrid/appdata.py", line 167, in rebuild_db() File "/usr/share/appgrid/appdata.py", line 62, in rebuild_db for pkgname in get_apt_pkgnames(): ^^ File "/usr/share/appgrid/appdata/apps/aptapp.py", line 250, in get_apt_pkgnames is_digits(ij.split(base)[1])) or ^^ ValueError: empty separator dpkg: error processing package appgrid (--configure): installed appgrid package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: appgrid E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.18 [origin: unknown] ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Thu Jul 11 14:26:25 2024 InstallationDate: Installed on 2023-12-19 (205 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-06-15 (26 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade noble third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072792 Title: Several python errors when updating/upgrading. Started after upgrading to 24.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2072792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072775] [NEW] Fastmail's WebDav, CalDav and CardDav is buggy
Public bug reported: Even though GNOME Online Accounts now natively supports WebDav, CalDav and CardDav, it doesn't work with Fastmail. This bug was recognised upstream, and has been fixed upstream in 3.50.1. Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the Ubuntu 24.04 "updates" or "backports" repositories? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-online-accounts 3.50.0-4ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 15:15:21 2024 InstallationDate: Installed on 2021-06-24 (1113 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+attachment/5796207/+files/Dependencies.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+attachment/5796209/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072775 Title: Fastmail's WebDav, CalDav and CardDav is buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072706] [NEW] bash: pwd and prompt don't update after deleting current working directory
Public bug reported: When a directory is deleted while the user is inside it, the terminal should automatically return to the parent directory. Expected behaviour When a directory is deleted while the user is inside it, the terminal should automatically return to the parent directory. ``` user@domain:~/test$ mkdir ~/test && cd ~/test && touch foo && ls foo user@domain:~/test$ rm -r ~/test user@domain:~/$ ``` Actual behaviour The terminal remains in the deleted directory's path, even though the directory no longer exists. Steps to reproduce the behaviour Create a new directory and navigate into it: ``` user@domain:~/test$ mkdir ~/test && cd ~/test && touch foo && ls foo ``` Delete the directory while still inside it: ``` user@domain:~/test$ rm -r ~/test ``` MATE general version 1.26.0 Package version 1.26.0 Linux Distribution Ubuntu MATE 22.04 Link to bugreport of your Distribution (requirement) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072706 Title: bash: pwd and prompt don't update after deleting current working directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] Re: [SRU] virtlogd not rotating logs properly
** Patch added: "lp2072647-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5795865/+files/lp2072647-libvirt.debdiff ** Description changed: [Impact] - When one enables max_age_days on /etc/libvirt/virtlogd.conf, for + When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: - [Test Case] 1) Launch a couple of dummy VMs to ensure that there are some logs in /var/log/libvirt 2) Edit /etc/libvirt/virtlogd.conf and ensure that the max_age_days setting is uncommented as per the following: -max_age_days = 1 - 3) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) - 4) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: -Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' + max_age_days = 1 + 3) sudo systemctl restart virtlogd + 4) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) + 5) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: + Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' [Where problems could occur] - + There could be some issues with virtlogd, but the code path only executes when max_age_days is different than 0. - In the event of a regression, one could disable the setting by commenting max_age_days. + In the event of a regression, one could disable the setting by commenting max_age_days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: [SRU] virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] Re: [SRU] virtlogd not rotating logs properly
** Summary changed: - virtlogd not rotating logs properly + [SRU] virtlogd not rotating logs properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: [SRU] virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] Re: virtlogd not rotating logs properly
** Description changed: - When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example - by setting it to max_age_days = 1, the log files are not rotated + [Impact] + + When one enables max_age_days on /etc/libvirt/virtlogd.conf, for + example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: - Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse - rotated index from '' + + [Test Case] - There is a patch upstream [1] with the fix, and this is the placeholder - LP to backport that change into Ubuntu while I work on the backport - effort. + 1) Launch a couple of dummy VMs to ensure that there are some logs in /var/log/libvirt + 2) Edit /etc/libvirt/virtlogd.conf and ensure that the max_age_days setting is uncommented as per the following: +max_age_days = 1 + 3) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) + 4) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: +Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' - - [1] https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/ZWZ7GFFLZTCMWDUUB3X4FFK4YT5LW4OA/ + [Where problems could occur] + + There could be some issues with virtlogd, but the code path only executes when max_age_days is different than 0. + In the event of a regression, one could disable the setting by commenting max_age_days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] [NEW] virtlogd not rotating logs properly
Public bug reported: When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' There is a patch upstream [1] with the fix, and this is the placeholder LP to backport that change into Ubuntu while I work on the backport effort. [1] https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/ZWZ7GFFLZTCMWDUUB3X4FFK4YT5LW4OA/ ** Affects: libvirt (Ubuntu) Importance: Undecided Assignee: David Negreira (dnegreira) Status: New ** Affects: libvirt (Ubuntu Noble) Importance: Undecided Assignee: David Negreira (dnegreira) Status: New ** Also affects: libvirt (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Noble) Assignee: (unassigned) => David Negreira (dnegreira) ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => David Negreira (dnegreira) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046313] Re: Shutter crashes upon startup 'shutter' terminated by signal SIGSEGV (Address boundary error)
Ubuntu 24.04 (Noble Numbat) repositories contain shutter 0.99.2-4 , and not 0.99.5. It looks like shutter 0.99.5 is only included in the repositories of Ubuntu 24.10 (Oracular Oriole), which is three months away from being released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046313 Title: Shutter crashes upon startup 'shutter' terminated by signal SIGSEGV (Address boundary error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/2046313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
A simple fix is... ``` pip install --break-system-packages pyasynchat pyasyncore ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: USB sticks used with ‘Startup Disk Creator’ not reusable?
Thanks very much, Chris and Chris, for your detailed thoughts. I left the stick with the IT Support at work (and I won't be back there for a few days), and I'd prefer to show them your suggestion about the partitions and see what they might come up with (though I saw them playing around with the partitions while they tried to find a solution). I've only had two USB sticks cark it (out of quite a few sticks I've used) in the past. The IT Support at work did look for an external lock switch, which there wasn't - as Chris G said, they are pretty rare. I only had one stick where that was a facility, and that was years ago. Interesting suggestion to wipe a new thumb drive and recreate your own partition from the beginning. I might do that when I next use a new drive (perhaps the one I've bought in order to install the latest LTS), but I need to find a reliable Windows program to create the installer on that USB stick - I've read about 'Etcher'. I'll let you know when the IT guys at work get to the USB stick again. Cheers David On Mon, Jul 1, 2024, at 12:31 AM, Chris Robinson wrote: > > Actually, I've never had a problem with a thumb drive that couldn't be fixed. > > There IS a problem with the partition table placed there at the factory > format on some thumb drives. From memory, it was a bug with the way the > original DOS programs did partition table formats. It wasn't a problem until > FAT32, but for some reason Linux systems can have problems with drives that > previously worked fine. It usually pops up after you format the partition. > > What I'd recommend is to use DD to write zeros to the first couple of KB. > This will overwrite the partition table. You'll then need to recreate a > FAT32 partition and format it. > > `dd if=/dev/zero of=/dev/sdX bs=4K > > Change sdX to the device name for the unmounted thumb drive. Do NOT get this > wrong because any device written to will be very difficult to recover if you > haven't previously made a copy.` > The usual problem I came across was that the drive could not be accessed at > all, even to partition or format until the partition table was erased. I've > heard of similar problems to David's as well. > > If you don't want to mess around with DD (huge potential for disaster if you > write nulls to the wrong drive) then you could try using the disks program, > delete the partition table (make sure that gets written, maybe exit the > program to commit the write) and then recreate a new compliant FAT32 > partition. I've heard of that working, but of course is not possible in > cases where the device can't be accessed or written to. > > I'll be interested to know this solves the problem, because it would mean > that thumb drive manufacturers are still using a very, very, old spec. for > partition tables. I pretty routinely wipe any new thumb drive and create my > own partition, and like I said I've never had a problem with any thumb drive > ever. Some of them are tiny ones that must be a couple of decades old that > still get used to transfer a few files to another computer somewhere. > > Chris > > > > > > On Sunday, 30 June 2024 at 11:29:20 pm AEST, Chris Guiver > wrote: > > > G'day David > > > Should a USB stick that was used with ‘Startup Disk Creator’ be able to be > > reformatted for everyday read/write work again? > > Yes, however USB thumb-drives are really just cheap media; built to a low > price without any error checking, and they fail. I suspect your thumb-drive > has failed; even if not the whole device, enough of it that the contents can > no longer be changed. > > There are some USB drives which can be triggered to be RO (Read Only), but > they are/were rare (more expensive) and usually have a somewhat disguised > button/slide that prevents writing if the slider is in the protect mode. Your > USB 'stick' could be one of these, but only someone seeing the device will be > able to tell you (and they weren't common, so aren't often recognized) > > The write of an ISO to a thumb-drive does cause the image itself to be > written as READ ONLY, but that is only to prevent corruption, and that RO > cannot prevent a reformat; as its purpose is only to protect the image from > CHANGE, nor erasure. > > Again, I think your USB flash/thumb-drive is just faulty... I'm throwing out > 2-5 per year because they no longer can be trusted (I always DIFF or confirm > a write to thumb-drive is perfect before I trust it, and those thumb-drives > are failing my checks) It's a cheap consumable media, and every write to it > can destroy it. > > Chris g. > > > On Sun, Jun 30, 2024 at 11:01 PM David wrote: >> Hi folks >> >> In the past I had
[Bug 2071640] [NEW] python3-future 0.18.2 is not compatible with Python 3.12
Public bug reported: $ python3 -c 'from future import standard_library' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/future/standard_library/__init__.py", line 65, in import imp ModuleNotFoundError: No module named 'imp' Python 3.12 support was added upstream in v1.0.0: https://github.com/PythonCharmers/python-future/commit/ba1cc505f1cb8eb0dfe495174f05aaec5a01eef3 ** Affects: python-future (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071640 Title: python3-future 0.18.2 is not compatible with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-future/+bug/2071640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064850] Re: ubuntu noble install error warnings in noble
This is likely due to missing Python 3.12 support upstream: $ python3 -c '"(\r\n|\r|\n)\Z"' :1: SyntaxWarning: invalid escape sequence '\Z' $ python3.11 -c '"(\r\n|\r|\n)\Z"' # installed via pyenv $ It was added in 1.0.0: https://github.com/PythonCharmers/python-future/pull/632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064850 Title: ubuntu noble install error warnings in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-future/+bug/2064850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
USB sticks used with ‘Startup Disk Creator’ not reusable?
Hi folks In the past I had 20.04 LTS installed on an old laptop and when 22.04 LTS became available I used the application in Ubuntu called ‘Startup Disk Creator’ to write the new ISO image to a USB stick in order to do a clean install of 22.04 LTS. That process worked fine, the USB stick did the job fine. Earlier this year the laptop stopped working and I had it repaired professionally, new SSD instead of the hard drive. They put Windows onto it so that they could check things. I don’t have another Ubuntu machine on which to use ‘Startup Disk Creator’ again, so I’ll be looking for a Windows option for creating a USB for installing from. It was then that I examined the USB stick for the first time since I had used ‘Startup Disk Creator’ a couple of years back or so for the install of 22.04 LTS. I understood that ‘Startup Disk Creator’ had formatted the USB stick for its purposes, and figured that in Windows I could reformat it with FAT32 or exFAT in order to use the stick again for another purpose. Windows couldn’t format it, saying that the stick is ‘write-protected’. The IT Support staff at my workplace have not been able to remove the write-protection and get the stick usable again with any of their tools. They used some sort of partition manager tool, and tried via a Mac laptop too. It feels a bit like how people described non-reusable CDs and DVDs as beer-coasters in the past. Is this outcome something that ‘Startup Disk Creator’ is known for, or have I just had bad luck? Should a USB stick that was used with ‘Startup Disk Creator’ be able to be reformatted for everyday read/write work again? Cheers David -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
[Bug 2066030] Re: Package "diffuse" has a dependency on package "python3-distutils-extra" which is not automatically installed.
I have the same issue referenced in this bug report. The previous version that shipped with mantic (0.8.2-1 built from Debian) does correctly depend on python3-distutils, however python3-distutils was dropped from the noble repo. Accordingly the Ubuntu maintainer of the package incremented the version number to 0.8.2-1ubuntu1 and removed the dependency. The problem with that is the fact that diffuse 0.8.2 depends on the distutils Python module hasn't changed. I can see that the new version 0.9.0 from the developer removes all use of distutils, solving the issue once and for all on all future versions of Ubuntu (i.e. 24.10+) that ship the new version; however LTS users will have continue to have this dependency issue until 26.04. I'm not familiar with Ubuntu packaging procedure, regardless I hope a solution can be found beyond downloading the source package and manually editing the control file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066030 Title: Package "diffuse" has a dependency on package "python3-distutils- extra" which is not automatically installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffuse/+bug/2066030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070389] [NEW] python3-ipywidgets error output when installing with apt-get
Public bug reported: lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 apt-cache policy python3-ipywidgets python3-ipywidgets: Installed: 8.1.1-2 Candidate: 8.1.1-2 Version table: *** 8.1.1-2 500 500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Excerpt from apt-get output when installing python3-nose: Setting up python3-ipywidgets (8.1.1-2) ... /usr/lib/python3/dist-packages/ipywidgets/widgets/tests/test_traits.py:61: SyntaxWarning: invalid escape sequence '\.' 'var(--my-color-\.)', # CSS variable with escaped characters ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: python3-ipywidgets 8.1.1-2 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 25 15:37:03 2024 InstallationDate: Installed on 2024-06-25 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423) PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: ipywidgets UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ipywidgets (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070389 Title: python3-ipywidgets error output when installing with apt-get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/2070389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070388] [NEW] python3-nose error output when installing with apt-get
Public bug reported:
lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
apt-cache policy python3-nose
python3-nose:
Installed: 1.3.7-12
Candidate: 1.3.7-12
Version table:
*** 1.3.7-12 500
500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
Excerpt from apt-get output when installing python3-nose:
Setting up python3-nose (1.3.7-12) ...
/usr/lib/python3/dist-packages/nose/config.py:142: SyntaxWarning: invalid
escape sequence '\.'
"""nose configuration.
/usr/lib/python3/dist-packages/nose/ext/dtcompat.py:686: SyntaxWarning: invalid
escape sequence '\S'
_INDENT_RE = re.compile('^([ ]*)(?=\S)', re.MULTILINE)
/usr/lib/python3/dist-packages/nose/ext/dtcompat.py:1021: SyntaxWarning:
invalid escape sequence '\s'
pat = re.compile('(^|.*:)\s*\w*("|\')')
/usr/lib/python3/dist-packages/nose/ext/dtcompat.py:1430: SyntaxWarning:
invalid escape sequence '\s'
want = re.sub('(?m)^%s\s*?$' % re.escape(BLANKLINE_MARKER),
/usr/lib/python3/dist-packages/nose/ext/dtcompat.py:1434: SyntaxWarning:
invalid escape sequence '\s'
got = re.sub('(?m)^\s*?$', '', got)
/usr/lib/python3/dist-packages/nose/inspector.py:110: SyntaxWarning: invalid
escape sequence '\ '
"""Find lines in home that are inspectable.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3-nose 1.3.7-12
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jun 25 15:29:11 2024
Dependencies:
python3-pkg-resources 68.1.2-2ubuntu1
python3-zombie-imp 0.0.2-2
InstallationDate: Installed on 2024-06-25 (0 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64
(20240423)
PackageArchitecture: all
ProcEnviron:
LANG=en_GB.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: nose
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nose (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070388
Title:
python3-nose error output when installing with apt-get
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nose/+bug/2070388/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070300] Re: Software updater; Could not get a lock
Has been hanging like this for several weeks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070300 Title: Software updater; Could not get a lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2070300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070300] [NEW] Software updater; Could not get a lock
Public bug reported: up grader hangs 24.04 LTS ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.18 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:1000:82309:2024-06-22 11:42:13.464745784 -0700:2024-06-22 11:41:42.692293669 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.crash 644:1000:1000:0:2024-06-22 11:42:13.464745784 -0700:2024-06-22 11:42:13.464745784 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.upload 600:111:117:5:2024-06-22 12:57:37.330901555 -0700:2024-06-22 11:42:13.532746783 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 10:06:30 2024 InstallationDate: Installed on 2018-05-05 (2242 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/fish TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070300 Title: Software updater; Could not get a lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2070300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070297] [NEW] Software updater; Could not get a lock
Public bug reported: Ubuntu Software updater fails due to another piece of software being open. Cannot see any software version in Noble Robat being open. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.18 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:1000:82309:2024-06-22 11:42:13.464745784 -0700:2024-06-22 11:41:42.692293669 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.crash 644:1000:1000:0:2024-06-22 11:42:13.464745784 -0700:2024-06-22 11:42:13.464745784 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.upload 600:111:117:5:2024-06-22 12:57:37.330901555 -0700:2024-06-22 11:42:13.532746783 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 09:25:14 2024 InstallationDate: Installed on 2018-05-05 (2242 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/fish TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070297 Title: Software updater; Could not get a lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2070297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069944] [NEW] Text Editor on Ubuntutu 24.04 the copy entry in the context menu does not copy the selected text. Ctrl+C works
Public bug reported: Text Editor 46.1 UBUNTU 24.04 When selecting text and clicking on "Copy" inside the context menu (right click), No text is copied into the copy buffer. When you do a paste you get the previous text from another copy operation from a different application. ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069944 Title: Text Editor on Ubuntutu 24.04 the copy entry in the context menu does not copy the selected text. Ctrl+C works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2069944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069777] [NEW] mlxbf_pmc: bring in latest 6.8 upstream commits
Public bug reported: SRU Justification: [Impact] There are currently five upstream commits for Nvidia's mlxbf_pmc driver that are present in upstream, but not in the NV-Kernels 24.04 repo. These five commits provide several important fixes and a patch for style cleanup. [Fix] Cherry pick the following five commits from upstream linux: Dan Carpenter7c8772fef2c2 platform/mellanox: mlxbf-pmc: fix signedness bugs Luiz Capitulino c0459eeb64e9 platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks Luiz Capitulino 0d46439bda37 platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr optional Shravan Kumar Ramani 1ae9ffd303c2 platform/mellanox: mlxbf-pmc: Cleanup signed/unsigned mix-up Shravan Kumar Ramani fd23023e2aaa platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types [Test Cases] * Verify mlxbf_pmc driver loads properly on BlueField-2 and BlueField-3 platforms * Exercise mlxbf_pmc driver functionality via sysfs reads and writes. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069777 Title: mlxbf_pmc: bring in latest 6.8 upstream commits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2069777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069540] [NEW] Software updater; Could not get a lock;2404;LTS
Public bug reported: (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/gimp/2.0/help" because it would affect the host in "/var/lib/snapd" update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme" because it would affect the host in "/var/lib/snapd" update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/xubuntu-docs" because it would affect the host in "/var/lib/snapd ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.18 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:1000:92179:2024-06-12 12:43:25.578529424 -0700:2024-06-12 12:42:55.752597435 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.crash 644:1000:1000:0:2024-06-12 12:43:25.582530036 -0700:2024-06-12 12:43:25.582530036 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.upload 600:111:117:5:2024-06-12 13:43:42.492025422 -0700:2024-06-12 12:43:25.626536768 -0700:/var/crash/_usr_bin_classicmenu-indicator.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:11:04 2024 InstallationDate: Installed on 2018-05-05 (2234 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/fish TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069540 Title: Software updater; Could not get a lock;2404;LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2069540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068754] Re: Bang & Olufsen Cisco 980 not working on AX211 on 22.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => The Sutton Team (sutton-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068754 Title: Bang & Olufsen Cisco 980 not working on AX211 on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068754] [NEW] Bang & Olufsen Cisco 980 not working on AX211 on 22.04
Public bug reported: Tested the AX211 on the X1 Carbon 11 using 24.04 and it is working but Cisco would like the changes to be back ported to 22.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Bang & Olufsen Cisco 980 not working on AX211 on 22.041 in 22.04 + Bang & Olufsen Cisco 980 not working on AX211 on 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068754 Title: Bang & Olufsen Cisco 980 not working on AX211 on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
Okay! See https://gitlab.com/duplicity/duplicity/-/issues/824 for the fix and a test script. None of the previously mentioned workarounds (from thirteen years ago!) work. --ignore-errors does nothing in the currently released version due to a programming error. ** Bug watch added: gitlab.com/duplicity/duplicity/-/issues #824 https://gitlab.com/duplicity/duplicity/-/issues/824 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
In my case it turns out that two of the volumes were truncated somehow. Not sure if this is the sort of filesystem corruption that can occur when a removable volume is disconnected without unmounting it, but that would probably make sense. Unfortunately the deja-dup GUI has no way to recover from this problem and gives you no options on how to skip the affected files, it just reports the difftar file name which is less than helpful. I had to go decrypt and look through the manifest as noted above to figure out which files needed to be skipped when restoring (in this case, there was only one file, a very large audio recording that was thankfully backed up elsewhere). Nor does duplicity or deja-dup do anything to detect that this problem might exist when adding incremental backups (the truncated volumes were in a full backup from two months ago with several incrementals since). In the appears that I can restore from the command line (the links in a comment above from *thirteen years ago* are obviously no longer valid) using the --exclude option to duplicity. Truly deja-dup is an overly simplified GUI, having some options and robustness is not a luxury when dealing with important data. Amazing that neither of these pieces of software seem to have improved since then. Perhaps backups aren't important to developers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Attention Upgrading noble systems Attention Jul
hello Julian I'm still getting getting for cache lock: [Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 30973 (unattended-upgr)] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
Still a problem in 2024! (though the backup in question was made with 23.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
We would also like to look at the latest sosreport command that was run before crashing, can you share the latest /tmp/sos. so that we can inspect what is there? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
Hi, Thank you for the report! Do you mind testing and verify if you run into the same issue with the latest Ubuntu kernel? It should be 6.8.0-35.35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068071] [NEW] package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error ex
Public bug reported: Bug report was waiting when I started using the computer in the morning. No idea what it is about, sorry. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-35-generic 6.8.0-35.35 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_6_8_0_31_31_generic_104 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:david 4171 F pipewire /dev/snd/controlC0: david 4174 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Jun 5 06:58:11 2024 ErrorMessage: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2021-06-16 (1085 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20VK001CAU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=6c94f9a7-6ba0-496d-abcc-72b4e2c82feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.12-1ubuntu7 SourcePackage: linux Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-05-28 (7 days ago) dmi.bios.date: 11/06/2023 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET55W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VK001CAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR1FET55W(1.29):bd11/06/2023:br1.29:efr1.18:svnLENOVO:pn20VK001CAU:pvrThinkPadL13YogaGen2:rvnLENOVO:rn20VK001CAU:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20VK_BU_Think_FM_ThinkPadL13YogaGen2: dmi.product.family: ThinkPad L13 Yoga Gen 2 dmi.product.name: 20VK001CAU dmi.product.sku: LENOVO_MT_20VK_BU_Think_FM_ThinkPad L13 Yoga Gen 2 dmi.product.version: ThinkPad L13 Yoga Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068071 Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068067] [NEW] mlxbf_gige: bring in latest 6.x upstream commits
Public bug reported: SRU Justification: [Impact] There are currently four upstream commits for Nvidia's mlxbf_gige driver that are present in upstream, but not in the NV-Kernels 24.04 repo. These four commits provide three fixes and one feature (display of pause frame counters). [Fix] Cherry pick the following four commits from upstream linux: Linux 6.9.0 -> 09ba28e1cd3c David Thompson mlxbf_gige: stop interface during shutdown Linux 6.8.0 -> f7442a634ac0 David Thompson mlxbf_gige: call request_irq() after NAPI initialized Linux 6.8.0 -> d6c30c5a168f David Thompson mlxbf_gige: stop PHY during open() error paths Linux 6.8.0 -> c22341619852 David Thompson mlxbf_gige: add support to display pause frame counters [Test Cases] * Exercise reboot testing in a loop, verifying oob_net0 interface comes up * Enable kdump and verify that any triggered kernel dump does not crash mlxbf_gige driver * Exercise the new feature by running "ethtool -I -a oob_net0" before and after heavy traffic is sent into the oob_net0 interface. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068067 Title: mlxbf_gige: bring in latest 6.x upstream commits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2068067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063534] Re: "Social" lens icon missing from Dash
Is this "Won't Fix" categorically or only for a particular release? Does anyone have a better pointer for issue discussion/troubleshooting if this bug is being abandoned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063534 Title: "Social" lens icon missing from Dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1063534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067173] [NEW] W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details.
Public bug reported: W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target Packages (main/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target Translations (main/i18n/Translation-en_CA) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target DEP-11-icons-hidpi (main/dep11/icons-64...@2.tar) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:46, W:Target Packages (universe/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target Packages (universe/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target Translations (universe/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target Translations (universe/i18n/Translation-en_CA) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target DEP-11 (universe/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target DEP-11 (universe/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target DEP-11-icons-small (universe/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target DEP-11-icons (universe/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target DEP-11-icons-hidpi (universe/dep11/icons-64...@2.tar) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target CNF (universe/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:16 and /etc/apt/sources.list:46, W:Target Packages (multiverse/binary- amd64/Packages) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target Packages (multiverse/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target Translations (multiverse/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target Translations (multiverse/i18n/Translation-en_CA) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target DEP-11 (multiverse/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target DEP-11 (multiverse/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target DEP-11-icons-small (multiverse/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target DEP-11-icons (multiverse/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target DEP-11-icons-hidpi (multiverse/dep11/icons-64...@2.tar) is configured multiple times in /etc/apt/sources.list:26 and /etc/apt/sources.list:46, W:Target CNF (multiverse/cnf/Commands-amd64) is configured multiple times
Re: [Bug 2015017] Please test proposed package
Can confirm that this fixes the problem for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
** Changed in: openssl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[USN-6663-3] OpenSSL update
== Ubuntu Security Notice USN-6663-3 May 23, 2024 openssl update == A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 24.04 LTS Summary: Add implicit rejection in PKCS#1 v1.5 in OpenSSL. Software Description: - openssl: Secure Socket Layer (SSL) cryptographic library and tools Details: USN-6663-1 provided a security update for OpenSSL. This update provides the corresponding update for Ubuntu 24.04 LTS. Original advisory details: As a security improvement, OpenSSL will now return deterministic random bytes instead of an error when detecting wrong padding in PKCS#1 v1.5 RSA to prevent its use in possible Bleichenbacher timing attacks. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 24.04 LTS libssl-doc 3.0.13-0ubuntu3.1 libssl3t64 3.0.13-0ubuntu3.1 openssl 3.0.13-0ubuntu3.1 After a standard system update you need to reboot your computer to make all the necessary changes. References: https://ubuntu.com/security/notices/USN-6663-3 https://ubuntu.com/security/notices/USN-6663-1 https://launchpad.net/bugs/2054090 Package Information: https://launchpad.net/ubuntu/+source/openssl/3.0.13-0ubuntu3.1 OpenPGP_0x96F770C739BC5ACE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
[Bug 2066341] [NEW] Could not calculate the upgrade
Public bug reported: Could not calculate the upgrade ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed May 22 13:23:13 2024 InstallationDate: Installed on 2024-02-10 (102 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-05-22 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066341 Title: Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059953] Re: MAAS machine commissioning fails in "20-dhcp-unconfigured-ifaces "
Temporary workaround I used: Create a custom commissioning script "10-maas-extra-packages" with the contents: ``` #!/bin/bash apt update apt -y install isc-dhcp-client ``` This gets executed prior to 20-maas-02-dhcp-unconfigured-interfaces, which then runs successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059953 Title: MAAS machine commissioning fails in "20-dhcp-unconfigured-ifaces " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/2059953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065175] Re: In music-folder sometimes by clicking properties of a file, nautilus freezes
I'm also having this issue. I've seen it happen with flac files and mp3 files. The problem happens every time but only with certain files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065175 Title: In music-folder sometimes by clicking properties of a file, nautilus freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065511] Re: Android Studio and Files (file manager) flicker
I've been experimenting with various drivers and seems like I found a
workaround by downgrading Nvidia driver to
{NVIDIA-Server-Driver-metapackage-from-nvidia-driver470-server-(proprietary)}
from the driver535
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065511
Title:
Android Studio and Files (file manager) flicker
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065511/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I don't use autologin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064192] Re: Unable to resize windows
I don't use Autologin and have the same problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
Thank you, thank you! Appreciate the explanation of the long delay - I think one of the graphviz maintainers said something like "graphviz has gone through multiple different versioning schemes, all of them confusing" and the 2.42.4 release happened right around the point when they stopped explicitly saying "no this one is really actually a release". I'll sign up for some software anger management in the future :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065511] [NEW] Android Studio and Files (file manager) flicker
Public bug reported: Since the last kernel update to version .28, I've been experiencing extreme flickering in Android Studio and other apps. This prompted me to update most of my software, including Nvidia drivers, which didn't resolve the issue. Downgrading to the previous kernel version .26 during startup eliminates the issue. Additionally, there is a lag in the Terminal, which I'm not sure is related, but it also doesn't occur on the previous kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 11 22:37:52 2024 DistUpgraded: 2022-08-17 23:28:25,893 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 5.15.0-106-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-26-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA104 [GeForce RTX 3070] [1043:87c1] InstallationDate: Installed on 2020-12-30 (1228 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=7dbfeb24-66bc-4e2a-afb7-f7540262d282 ro iommu=pt amd_iommu=on vfio-pci.ids=1b73:1100 kvm.ignore_msrs=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-17 (633 days ago) dmi.bios.date: 04/19/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4501 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII DARK HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4501:bd04/19/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIDARKHERO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 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 jammy possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065511 Title: Android Studio and Files (file manager) flicker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2065511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2015017] Re: [SRU] scaling is wrong in SVG output
Sure, no problem at all! Thanks for the gracious reply, sorry about my frustration this morning. You can see the problem with this dotfile by running these commands - the figure will obviously be clipped (it should have 9 nodes but you can only see 6): dot -Tsvg fst.dot open fst.svg I've attached the resulting SVG file as well. Note also that if you render to PDF, PNG, etc, you won't see the clipping. ** Attachment added: "fst.svg" https://bugs.launchpad.net/bugs/2015017/+attachment/5777430/+files/fst.svg ** Attachment added: "fst.dot" https://bugs.launchpad.net/bugs/2015017/+attachment/5777431/+files/fst.dot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
** Attachment added: "fst.dot" https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+attachment/5777432/+files/fst.dot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915635] Re: Update graphviz to latest version
Delete "me too" comment that was me-tooing myself and perhaps too flamey. But the question remains... At the very least you (or Debian) could upgrade to 2.42.4, released (checks calendar) four years ago, which fixes a bunch of bugs and is not even a *minor* release: https://forum.graphviz.org/t/graphviz- version-2-42-4-has-been-released/17 It's pretty hard to find it on Graphviz website/gitlab (because, like, four years!) but here, I found it: https://gitlab.com/graphviz/graphviz/-/releases/2.42.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915635 Title: Update graphviz to latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1915635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915635] Re: Update graphviz to latest version
I'm going to be super annoying and add a me too comment here. It's really unacceptable that Ubuntu and Debian continue to publish a version *THAT IS NOT EVEN AVAILABLE UPSTREAM ANYMORE*. What is the hold-up here? Is there some serious problem with the more recent versions? If so please say what it is. Is it just lack of resources? If so, sorry to be a pest. For what it's worth I did in fact contribute a fix to the problem which bothers me the most... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915635 Title: Update graphviz to latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1915635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: scaling is wrong in SVG output
I hate to be a jerk but it's been almost a year, and I even provided a complete fix and patch. Meanwhile, *Graphviz no longer even publishes the source code for version 2.42.2* This would seem to be a serious Debian policy violation! The bug HAS BEEN FIXED UPSTREAM FOR FOUR YEARS NOW. Either apply this patch or update the Graphviz packages, or find someone who will do it, please, please, please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Make proposed available by default? [was: Setting NotAutomatic for hirsute+1-proposed]
On 5/3/24 22:08, Seth Arnold wrote: But, I also expect very few of our users would use -proposed. What percentage do you expect? I'm guessing less than 1%. Instead of configuring proposed by default, I suggest that we should make this work: $ sudo add-apt-repository proposed Unable to handle repository shortcut 'proposed' Let's also not lose sight of the fact that if proposed had been enabled by default with the current LTS release, the xz exposure and impact would have been a lot broader than it was, and also a lot harder to clean up and retract from. As it was, the customer I support mirrored -proposed into their internal aptly during the Feb 28-March 30 window when the exploited versions of xz packages were resident in noble-proposed, and some of their machines had it deployed as part of internal automation. They had to go through a manual exercise to delete the pocket from their mirror and specifically the xz-utils packages for a daily span of 30 days of mirroring and resilver all of their aptly package lists to redact that and remove their own potential for exposure. Let's err on the side of being a bit more cautious here, so we don't leave ourselves open to another possible 'adventure' that could sneak through unnoticed, before our users/customers are impacted. -proposed explicitly disabled by default has a purpose and requires being manually enabled, and once we flip that position, we may lose the value that explicit testing of packages in -proposed provides. -- David A. Desrosiers Principal Support Engineer (PSE/DSE), Canonical US -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel
tested using 24.04 on X1 Carbon 12 AX211 seems to work using the generic kernel, testing on the AX201 on the Carbon 9 did not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049938 Title: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I've noticed something, maybe this will help: all windows with SSD don't work properly, windows with CSD work as expected. Firefox main window with CSD works, sub-windows without don't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064192] Re: Unable to resize windows
In my test all applications have this problem only GTK4 and libadwaita do not, maybe also GTK3? Firefox with CSD works, but sub-windows without CSD don't work. Maybe this is related to SSD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065158] [NEW] libdwarf-dev is old, please update to v0.9.2 (released at Apr 3, 2024)
Public bug reported: libdwarf-dev version on Ubuntu repositories is from 2021 and contains numerous security bugs and missing functionality. Please update to a newer version of libdwarf (see https://github.com/davea42/libdwarf- code). ** Affects: dwarfutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065158 Title: libdwarf-dev is old, please update to v0.9.2 (released at Apr 3, 2024) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarfutils/+bug/2065158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065072] [NEW] German translation for "Copy" is incorrect in Ubuntu 24.04
Public bug reported: Ubuntu 24.04 GNOME nautilus 46.0 (1:46.0-0ubuntu2) When you try to copy a file it adds (Copy) to the file but since Ubuntu 24.04 with German translations, Nautilus appends "(Kopieren)" to the file name. This is incorrect, as "Kopieren" means "to copy" in German, while the desired behavior would be to use the noun "(Kopie)" meaning "copy". In older Ubuntu versions (22.04, 23.10) this works as expected and appends "(Kopie)" ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065072 Title: German translation for "Copy" is incorrect in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I have also encountered this issue. Also QT and Electron applications have no border/shadow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064905] Re: Dubious output when using regex with apt-cache search
Note the remark ", including virtual package names." in the manpage. bindgen-0.65 has a "Provides: bindgen" (with a version), so it has (also) the virtual package name "bindgen" and that perfectly matches your regex. So, working as intended & documented and hence I am changing the status to opinion (could be a question, but I don't seem to have the rights to do that) ** Changed in: apt (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064905 Title: Dubious output when using regex with apt-cache search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2064905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064192] Re: Unable to resize windows
I have the same problem, can't resize any windows tested with Krita and VSCodium. I don't know if this is related, but sometimes the mouse clicks through the windows to the window below the current one. (only for those that don't resize) basically unusable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064030] [NEW] Byobu 6.5+ autostart broken with fish shell
Public bug reported: Since byobu 6.5, the shell spawned by byobu-shell is started as a login shell using -l (https://github.com/dustinkirkland/byobu/commit/4a2ebccb627055e3605e39d300c6cf23d12939a1). This breaks byobu autostart with fish, as the autostart code in config.fish uses status --is-login to determine if fish runs inside byobu already. The autostart code only executes byobu-launcher if fish is a login shell (and interactive, but that doesn't seem relevant here). As byobu then starts fish again as a login shell, byobu starts again, which leads to tmux refusing to work with "sessions should be nested with care, unset $TMUX to force" and everything quits. I now cannot SSH into my server with byobu 6.5+ and autostart enabled, as byobu immediately quits. This has also been experienced by another user in https://github.com/dustinkirkland/byobu/commit/4a2ebccb627055e3605e39d300c6cf23d12939a1#commitcomment-140698811 ** Affects: byobu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064030 Title: Byobu 6.5+ autostart broken with fish shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/2064030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] [NEW] useradd --extrausers --groups tries to lock /etc/group
Public bug reported: On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063003] Re: package manager could not make changes to the installed system
As the requirement for reproducing is "being offline" it could be that this remove command wants to download packages, which fails. Yes, remove can install packages – specifically the problem resolver can try to fix a broken dependency by installing another provider/or-group member. Controlled by `pkgProblemResolver::FixByInstall` which is enabled by default. Once in a while I wonder if that should have been disabled for remove commands. Or if it was a mistake to resolve an upgrade problem 14y ago with this. Hard to tell if it does more good than bad as that highly depends on the situation. The other "obvious" possibility is that a maintainer script is trying to access the network. Perhaps its intended only on install, but not correctly guarded for the removal case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063003 Title: package manager could not make changes to the installed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062526] Re: DNS for snaps like Firefox and Chromium fails
I can certify that after today's system upgrade (mainly including the 6.8.0-28-lowlatency kernel), booting into the new kernel made the difference between Chromium-browser not working and working (I had previously replaced my Firefox browser with a native version from Mozilla's APT repository because I needed it working, so I could not easily test with that). Definitely a showstopper kind of bug; surprised there weren't more reports to be found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062526 Title: DNS for snaps like Firefox and Chromium fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2062526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs
Also seen on Ubuntu 20.04.6 with latest/stable: 123.0.6312.122 2024-04-15 (2821) 168MB chromium snap. Confirming that if I manually apply the patch given in https://github.com/snapcore/snapd/pull/13857 the issue is fixed. But then when I refreshed chromium to latest/stable: 124.0.6367.60 2024-04-19 (2828) 169MB my patch got stepped on and I needed to reapply it. Don't know when the fix is expected to be incorporated in a snap refresh but until then it's easy enough to manually take care of. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062173 Title: Apparmor denies updating namespace with ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1936678] [NEW] Samsung Laptop support module doesn't load
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062526] [NEW] DNS for snaps like Firefox and Chromium fails
Public bug reported: While this sounds somewhat similar to the currently reported showstopper, none of the workarounds in that report helps for me and all snaps are affected. This started about a week ago. I am currently making do with using the natively installed Epiphany while using Firefox to refer to my login data. There is a report on Stackexchange that sounds like what I experience: https://askubuntu.com/questions/1510668/network-problems-with-snap-apps My own system, however, is not Kubuntu but an Ubuntu Studio variation. Also there have been some very manual recoveries in its history (because the system was completely broken after some updates, I had to boot a recovery system, mount the file system of the broken system and do updates with changed root settings). As a result, I cannot rule out that not all permissions and other package details may be the same as on a pristine system: after all, it would appear that few other people see this problem. However, I am out of my depth regarding how to address this, why the problem suddenly manifested itself about a week ago (the last manual recovery is a few months back) and how to get back to a working system. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: snapd 2.62+24.04build1 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Apr 19 11:27:37 2024 InstallationDate: Installed on 2011-10-14 (4571 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: While this sounds somewhat similar to the currently reported showstopper, none of the workarounds in that report helps for me and all snaps are affected. This started about a week ago. I am currently making do with using the natively installed Epiphany while using Firefox to refer to my login data. There is a report on Stackexchange that sounds like what I experience: https://askubuntu.com/questions/1510668/network-problems-with-snap-apps My own system, however, is not Kubuntu but an Ubuntu Studio variation. Also there have been some very manual recoveries in its history (because the system was completely broken after some updates, I had to boot a recovery system, mount the file system of the broken system and do updates with changed root settings). As a result, I cannot rule out that not all permissions and other - package details may be other than on a pristine system: after all, it + package details may be the same as on a pristine system: after all, it would appear that few other people see this problem. However, I am out of my depth regarding how to address this, why the problem suddenly manifested itself about a week ago (the last manual recovery is a few months back) and how to get back to a working system. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: snapd 2.62+24.04build1 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Apr 19 11:27:37 2024 InstallationDate: Installed on 2011-10-14 (4571 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062526 Title: DNS for snaps like Firefox and Chromium fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2062526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062177] [NEW] Remmina crashes after RDP connection
Public bug reported:
When connecting with RDP Remmina crashes. Syslog show the following:
2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001
pid=3214] Successfully activated service 'org.gnome.seahorse.Application'
2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started
app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell.
2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log
all output statements. Turn on more verbose output by using
"G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available
on the Remmina wiki
at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]:
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] -
[freerdp_settings_get_bool]: Invalid key index 0
[FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_int_assert]: FALSE
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637]
2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3
[0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660]
2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3
[0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150]
2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3
[0x70e69420], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3
[0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0]
2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 4:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 5:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 6:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 7:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]:
[13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 8: unresolvable, address=(nil)
2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]:
/usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core
dumped) "$REMMINA" "${@}"
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: remmina 1.4.35+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 18 13:59:31 2024
InstallationDate: Installed on 2022-05-21 (698 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220421)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: remmina
UpgradeStatus: Upgraded to noble on 2024-04-17 (1 days ago)
** Affects: remmina (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 2061834] Re: apt build-dep . fails to parse build dependencies
https://salsa.debian.org/apt- team/apt/-/commit/633f6d67a28b375cf1f225f14d3c926e618d46af ** Changed in: apt (Ubuntu) Status: New => Fix Committed ** Changed in: apt (Ubuntu) Assignee: (unassigned) => David Kalnischkies (donkult) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061834 Title: apt build-dep . fails to parse build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2061834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060929] Re: *resolved* Unable to install opendkim as libmilter is not found
** Changed in: opendkim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060929 Title: *resolved* Unable to install opendkim as libmilter is not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/2060929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061732] [NEW] tmpfs storage config definitions fail
Public bug reported:
Running an install (Jammy) with an install definition that includes
```
autoinstall:
...
storage:
config:
...
- id: tmpfs
type: mount
spec: "none"
path: "/tmp"
fstype: "tmpfs"
options: "mode=1777,nosuid,nodev"
```
Leads to the following error
```
File
"/snap/subiquity/5495/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 1251, in mount_data
raise ValueError(
ValueError: mount entry without 'device' missing: ['fstype'].
({'path': '/tmp', 'options': 'mode=1777,nosuid,nodev', 'spec': 'none', 'id':
'tmpfs', 'type': 'mount'})
```
I traced this back to the curtin invocation in
/var/log/installer/curtin-install/subiquity-partitioning.conf which
contains
```
- path: /tmp
options: mode=1777,nosuid,nodev
spec: none
id: tmpfs
type: mount
```
Critically, the fstype entry has been removed, leading me to believe
that the error is in the subiquity code.
This previously worked with earlier Jammy images.
Currently running subiquity 24.02.1 via the image at
https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/current/
A potentially related bug report from 2023-10-28
https://bugs.launchpad.net/curtin/+bug/2041725
I believe this was broken by this commit
https://github.com/canonical/subiquity/commit/0cc4fdf34893d7420cd3bf5d227b273791dbcdfb
The commit removed the fstype parameter, the new code assumes a device,
which does not work in the case of tmpfs when the device is None.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061732
Title:
tmpfs storage config definitions fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2061732/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060993] [NEW] Startup applications / gnome-session-properties does not persist between logins
Public bug reported: Having installed Guake I tried adding `/usr/bin/guake --hide` to Startup Applications. However, it was not in the list of startup applications when I next booted. I tested logging off and logging on again and found it wasn't persisting between logins. Data I entered was: Name: Guake Command: /usr/bin/guake --hide Comment: Guake terminal I also tried just command=/usr/bin/guake ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-startup-applications 46.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 17:22:47 2024 InstallationDate: Installed on 2024-04-09 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240409) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060993 Title: Startup applications / gnome-session-properties does not persist between logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2060993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060880] Re: squid crashes after update to 4.10-1ubuntu1.10
Testing the new packages now, and have not yet had any segfaults, whereas the 4.10-1ubuntu1.10 started logging faults with a couple of minutes of starting and very regularly (sub-minute) after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060880 Title: squid crashes after update to 4.10-1ubuntu1.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2060880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060797] Re: df says Resource temporarily unavailable after kernel upgrade to 5.15.0-102
I'm seeing the same on Linux Mint 21.1 Cinnamon 5.6.8 with kernel 5.15.0-102. Also noted that Thunderbird crashes on this kernal version if its profiles are mounted via cifs. appears to be a permissions issue kernel: [ 9815.799722] audit: type=1400 audit(1711979062.969:153): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/Working/Thunderbird/profiles.ini" pid=6651 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060797 Title: df says Resource temporarily unavailable after kernel upgrade to 5.15.0-102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2060797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
** Also affects: cloud-archive/yoga Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
Backport to focal-yoga adapted with the patch from Christian ** Attachment added: "libvirt_8.0.0-1ubuntu7.7~cloud1_source.changes" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+attachment/5763330/+files/libvirt_8.0.0-1ubuntu7.7~cloud1_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2028548] Re: fwupd too old to get and install releases for UEFI dbx
Not everyone can boot from a flash drive due to corporate restrictions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028548 Title: fwupd too old to get and install releases for UEFI dbx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2028548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410813] Re: Cannot draw in xournal since 0.4.2.1-1ubuntu1
Could we maybe, like, make "use xinput" be off by default? This bug is now, what, 15 years old? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/410813 Title: Cannot draw in xournal since 0.4.2.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xournal/+bug/410813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
It seems that the usual password keyring called Login is not automatically created in gnome-keyring. In fact there are no credentials of any kind in there on logging in after a clean install. If you change your password via the control panel, the login keyring is then created. However, when you reboot the Login keyring is not automatically unlocked, as it should be. So, any items you have stored in there are not accessible and you are asked for the password when a service needs credentials from it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060667] [NEW] No default keyring and does not unlock on login
Public bug reported: On a fresh install of Ubuntu 24.04 numbat, gnome-keyring does not seem to be properly configured. If I attempt to add an online account via settings > online accounts, after authentication with the online account gnome-keyring prompts me to create a default keyring because one does not exist yet, so I cancelled. Opening gnome-keyring reveals there is no entry under Passwords when I think there should be a "Login" password keyring that's automatically unlocked on login. Setting a new password via settings > system > users creates a new Loging keyring. However, this keyring is not automatically unlocked on login. So, whenever I first use an app after login that uses a keyring, such as connecting to Google drive via Nautilus, I'm prompted for the keyring password. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 12:19:00 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240409) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060667 Title: No default keyring and does not unlock on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
Can confirm this issue still exists with Noble Numbat 24.04 with open- vm-tools 12.3.5-5build1. Is there a plan to resolve this before 24.04 is released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945661] Re: openstack commands fail with GTK3 error
I believe I've nailed this one down, after a day of heads-down testing.
The issue boils down to this bit of code, in /usr/lib/python3/dist-
packages/cmd2.py:
# The extraneous output bug in pyperclip on Linux using xclip was fixed in
more recent versions of pyperclip
if sys.platform.startswith('linux') and pyperclip_ver < 1.6:
# Avoid extraneous output to stderr from xclip when clipboard is empty
at cost of overwriting clipboard contents
pyperclip.copy('')
else:
# Try getting the contents of the clipboard
_ = pyperclip.paste()
Specifically that last line: `_ = pyperclip.paste()`, which assumes a
clipboard exists and has been initialized. In most cases, it has
not/will not be.
The attached diff to cmd2.py will allow these commands to succeed. I
initially added some debug to allow me to see if the clipboard was
accessible or not, and that's how I found this.
Let me know if this is sufficient to SRU into the python3-cmd2 package
to address this.
** Patch added: "cmd2-diff.patch"
https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1945661/+attachment/5761586/+files/cmd2-diff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945661
Title:
openstack commands fail with GTK3 error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1945661/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060137] Re: Gnome freezes on login with X11 and nvidia
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 I'm sorry if I'm wrong, I've now read the problems mentioned but I'm not having any problems related to input delay, when I try to log into the session it freezes and or black screens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060137] [NEW] Gnome freezes on login with X11 and nvidia
Public bug reported: Recently i updated muttter-common(42.9-0ubuntu7) and libmutter(42.9-0ubuntu7), gir1.2-mutter(42.9-0ubuntu7) on Ubuntu 22.04 LTS after which when I try to login the following issue happens but only when I use the nvidia driver and X11 this does not happen when using Wayland or Nouveau driver. The problem is when I try to log in, tested on nvidia drivers 535 and 545. in most cases: Desktop freezes for ~15s, then ~4s black screen, then ~20s grey screen, then works as expected. In some cases: Gnome locks up and needs a hard reset (mouse cursor does not freeze) In rare cases: Works as expected, except high CPU usage There are new error messages in the syslog file that weren't there before: gnome-shell[...]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? gnome-shell[...]: Window manager warning: MetaSyncRing: Too many reboots -- disabling ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
Not sure who all the upstream(s) involved might be, but from my personal PoV at least you can add all the options you like… the topic gets harder if we talk defaults & changing (e.g.) the lists completely (like that tabular verbose-explosion thingy from apk or whatever it was). At some point it might make sense to extended apt-patterns so that current (and future) lists can be expressed in them and then add some more options to format those lists/tables/… at which point we could have different templates and so options/choices galore. I think aptitude has formatting to some extend of its lists. One of my first apt patches that was never merged was actually about reordering/coloring the lists… that failed, so I am very positive that a much bigger yak will be shaved more easily and faster many years later. ;) Precedence of the initial ask is 'can be autoremoved' btw, which is not displayed, displays a full list, an even fuller list in version mode or displays a single line with how many packages could be autoremoved depending on config. P.S.: On a multi-arch system nearly every Depends is a choice even without or-groups: given that you e.g. pick banana:amd64 or banana:i386 for an M-A:foreign banana. And the t64 transition added a quadrillion of real vs. virtual bananas at least until everyone depends on bananat64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059951] [NEW] mlxbf_gige: stop interface during shutdown
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059951 Title: mlxbf_gige: stop interface during shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059337] Re: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded
@chad.smith I used to use "NEEDRESTART_MODE=l" so needrestart would print a list of suggested restarts and I could then run it interactively if I needed to, but now I don't get a choice. needrestart always restarts without asking. So for now I put a bunch of processes to protect in a file in /etc/needrestart/conf.d, as part of my cloud-init user-data of course. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059337 Title: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2059337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059337] Re: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded
I believe the patch referenced above causes other bad behaviors. Specifically, it causes systemd-networkd to be restarted without any sort of prompt whenever a library it links with receives a security update. In my experience restarting systemd-networkd can break active WireGuard tunnels and can cause chronyd to stop polling IPv6 servers. I think the change at issue is adding the flags "-m u" to apt-pinvoke in /etc/apt/apt.conf.d/99needrestart, which also means needrestart now ignores a setting of "NEEDRESTART_MODE=l" in the environment when run from apt. I've started to add systemd-networkd to my needrestart ignore list, but perhaps that should be a default setting, as it is for NetworkManager. I'm testing with Noble in a LXD VM with an image from the ubuntu-daily repository. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059337 Title: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2059337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059310] [NEW] mlxbf_gige: call request_irq() after NAPI initialized
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The RX IRQ handler runs "napi_schedule()" before NAPI is fully initialized via "netif_napi_add()" and "napi_enable()", both which happen later in the open() logic. [Fix] The logic in mlxbf_gige_open() must fully initialize NAPI before any calls to request_irq() execute. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Enable kdump completely * Trigger kdump via "echo c > /proc/sysrq-trigger" * There should be no exceptions from mlxbf_gige driver [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059310 Title: mlxbf_gige: call request_irq() after NAPI initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059279] [NEW] mlxbf_gige: replace SAUCE patch for pause frame counters
Public bug reported: SRU Justification: [Impact] The support for mlxbf_gige pause frame counters was added to Jammy via a SAUCE patch. After upstream review, a small issue was fixed that makes the SAUCE patch different from the upstream commit. [Fix] The fix is to replace the SAUCE patch in the Jammy repo with the upstream equivalent. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Execute the command "ethtool -I -a oob_net0" to get baseline stats * Send heavy traffic into "oob_net0" interface * Re-run the above ethtool command, noting the pause frame counters [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059279 Title: mlxbf_gige: replace SAUCE patch for pause frame counters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055398] Re: Please drop libimath-dev dependency on python3-imath (fixed upstream in Debian)
Thanks Graham for the quick turnaround here! Looks like builds are all green now; any chance to get this merged? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055398 Title: Please drop libimath-dev dependency on python3-imath (fixed upstream in Debian) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imath/+bug/2055398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381808] Re: facebook Restaurant City cannot run
Perched on the picturesque shores of Mykonos, Bagatelle Restaurant offers a tantalizing fusion of Mediterranean flavors and chic ambiance. Renowned for its vibrant atmosphere and delectable cuisine, Bagatelle Mykonos beckons guests to embark on a culinary journey like no other. With a menu crafted from the freshest local ingredients and inspired by the rich culinary heritage of the region, each visit promises an unforgettable experience of indulgence and sophistication amidst the stunning backdrop of Mykonos. https://bagatelle.com/venues/mykonos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/381808 Title: facebook Restaurant City cannot run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ez-ipupdate/+bug/381808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058807] [NEW] Segmentation fault
Public bug reported: Frequently (but not always, haven't figured out what makes the difference) I cannot start modem-manager-gui, getting the following crash output on the console: modem-manager-gui (modem-manager-gui:186352): Gtk-WARNING **: 12:49:10.872: Theme directory places/128 of theme ubuntustudio has no size field (modem-manager-gui:186352): Gtk-WARNING **: 12:49:10.872: Theme directory places/scalable of theme ubuntustudio has no size field Connection manager: Network Manager >= 0.9.0 Modem manager: Modem Manager >= 0.7.0 Segmentation fault at address: 0x5e3ad4a2869e Stack trace: 1. /lib/x86_64-linux-gnu/libc.so.6(+0x1a71da) [0x7415623a71da] 2. /lib/x86_64-linux-gnu/libc.so.6(+0x1a71da) [0x7415623a71da] 3. modem-manager-gui(mmgui_notifications_new+0x1d3) [0x5e3f36422db3] 4. modem-manager-gui(+0x4205e) [0x5e3f3644705e] 5. modem-manager-gui(mmgui_svcmanager_start_services_activation+0x12c) [0x5e3f3642cb2c] 6. modem-manager-gui(+0x27deb) [0x5e3f3642cdeb] 7. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x14a) [0x7415631cd2fa] 8. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x4490c) [0x7415631fc90c] 9. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x35591) [0x7415631ed591] ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: modem-manager-gui 0.0.20-6 ProcVersionSignature: Ubuntu 6.8.0-7.7.1-lowlatency 6.8.0-rc3 Uname: Linux 6.8.0-7-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Mar 23 12:50:13 2024 InstallationDate: Installed on 2011-10-14 (4544 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: modem-manager-gui UpgradeStatus: Upgraded to noble on 2023-11-04 (140 days ago) ** Affects: modem-manager-gui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058807 Title: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/2058807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058491] [NEW] (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process
Public bug reported: Appears to be cross-compiled with both GTK+2 and GTK+3 flags. Fails to start due to error: (mate-appearance-properties:15895): Gtk-ERROR **: 17:02:39.177: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported I know this is coming from a rather old version of Ubuntu 18.04, but there is a reason why I'm running an old installation, and the lack of resources is why I am running Mate. Thought I should at least let you know this is happening. ** Affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058491 Title: (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/2058491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055434] Re: [MIR] pemmican
I reviewed pemmican 1.0.3-0ubuntu1 as checked into noble. This shouldn't be considered a full audit but rather a quick gauge of maintainability. pemmican is a small utility which warns users of power supply issues on the Raspberry Pi 5 platform. - CVE History - No CVEs. This project is a month old though. - Build-Depends - Apart from the typical Python package dependencies: - python3-gi - python3-pyudev - python3-dbus - For documentation: - python3-sphinx - python3-sphinx-rtd-theme - pre/post inst/rm scripts - There are automatically added scripts from dh_python3 and dh_installsystemduser. - Init scripts compile the python scripts with py3compile and enable the systemd services. - Rm scripts for cleanup and removal of the systemd services. - systemd units - /usr/lib/systemd/user/pemmican-monitor.service -> simple systemd unit that runs as the user. - /usr/lib/systemd/user/pemmican-reset.service -> one-shot systemd unit that runs as the user. - dbus services - It dispatches freedesktop DBus notifications. - setuid binaries - None - binaries in PATH - /usr/bin/pemmican-mon -> python script to be run by the systemd unit. It runs MonitorApplication from gui.py - /usr/bin/pemmican-reset -> python script to be run by the systemd unit. It runs ResetApplication from gui.py - /usr/bin/pemmican-cli -> python script to add a MOTD message. It runs cli.py - sudo fragments - None - polkit files - None - udev rules - It monitors power supply-related events on usb/hwmon - unit tests / autopkgtests - The source code includes unit tests. They are run when building the deb package. - Autopkgtests are also the tests. - cron jobs - None - Build logs - Deprecation warning from setuptools because of trying to use 'setup.py install'. - Lintian clean. - Processes spawned - None - Memory management - Nothing out of normal, Python application. - File IO - None - Logging - None - Environment variable usage - It searchs for XDG_CONFIG_HOME, XDG_CONFIG_DIRS and (WAYLAND_)DISPLAY. - Use of privileged functions - None - Use of cryptography / random number sources etc - None - Use of temp files - None - Use of networking - None - Use of WebKit - None - Use of PolicyKit - None - Any significant cppcheck results - None - Any significant Coverity results - None - Any significant shellcheck results - None - Any significant bandit results - None - Any significant govulncheck results - None - Any significant Semgrep results - None The code is widely documented and properly formatted. It contains error and exception handling. Upstream runs the testing suite with GitHub Actions on every commit. Since it's a month old project, we cannot speak about maintainability but the owner is a Canonical engineer. The complete codebase is made by 6 Python files: * power.py -> Opens hardcoded '/proc/device-tree/chosen/power' and reads values. * notify.py -> DBus freedesktop notification handler class, with hardcoded paths and values. * lang.py -> Minimal locale and internationalization loading. * gui.py -> Interaction with the freedesktop notification service to notify the user. * const.py -> Constant variables to be used, uses XDG_CONFIG_ environment variables. * cli.py -> CLI tool to run the same functionality as the systemd units but getting the output as stdout. Overall, the code looks well written and it does not present any security issues. Binaries generated: * pemmican-desktop: Systemd units run as the user, since it uses dh_installsystemduser. It cannot be used to gain privileges. The reset unit queries /proc/device- tree/chosen/power sending a freedesktop notification in case of brownout/not enough current. The monitoring unit monitors udev changes, sending a freedesktop notification in case of undervolt/overcurrent detected. * pemmican-server: It works as a update-motd hook for running the CLI application. Same as the desktop reset one, which queries the information but it adds the message to MOTD in case something is detected. The messages and invocation are hardcoded so no possibility to manipulate the output. Security team ACK for promoting pemmican to main. ** Changed in: pemmican (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: pemmican (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055434 Title: [MIR] pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2055434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Description changed: - [IMPACT] + [ Impact ] - The sos team is pleased to announce the release of sos-4.7.0 This - release focused on expanding support in policies for more and multiple - package managers. + * A new sosreport version is available upstream, and following the + https://wiki.ubuntu.com/SosreportUpdates policy for stable release + exception we will now SRU the sosreport 4.7.0 upstream release. - [TEST PLAN] + * This release introduces a couple of new plugins as well as bugfixes + done between the previous Ubuntu 4.5.6 sosreport version and the new + 4.7.0. - Documentation for Special Cases: - https://wiki.ubuntu.com/SosreportUpdates - [WHERE PROBLEMS COULD OCCUR] + [ Test Plan ] - The changes in sosreport are described below. There are a number of - changes related to report, plugins and policy. The changes in sosreport - content may break existing tooling, so that will need extensive testing. + * The detailed test plan can be found on + https://wiki.ubuntu.com/SosreportUpdates and should be tested by a + couple of users. - ## Global Changes - + Added support for `S3` uploads. + [ Where problems could occur ] - ## Policy Changes - + Fixed `dist_version()` for Ubuntu. + * Some plugins might stop working, and this will show when running + sosreport. - ## Report Changes - + Added a new preset for `app_eda` (Ansible Automation Platform Event Drive Ansible). + * Uploading to S3 needs the python3-boto3 dependency installed. - ### Plugin Changes - + New plugins: `aide`, `app_eda`, `coredump`', `infinidat`, `vectordev`. - + The `networking` plugin now uses a predicate for `ss` commands on Ubuntu. - + Enabled the `kubernetes` plugin for Debian. - + Dropped the `atomic` plugin. - + Fixed an issue with the command predicate for the `lxd` plugin when enabled via a snap. - + The `nvme` plugin now collects additional files per nvme drive on the host. + * If there is an issue with a plugin that is causing instability to the + system, this can be disabled by running 'sosreport -n '. - ## Collect Changes - + Added a transport for `Saltstack`. + * Currently running sos collect with Juju 3 is -not- working, even for + the current 4.5.6 Ubuntu version, we are working upstream on a fix + here: https://github.com/sosreport/sos/pull/3422 this is not part of the + core functionality of sos, and one can still run sos report manually on + the nodes. - ## Cleaner Changes - + `clean` will no longer try to obfuscate words that are 3 characters or less in length. - + `clean` will now properly obfuscate the upload password (if provided) in our own logs. + [ Other Info ] + + * Useful plugins that are now part of 4.7.0 and could do some testing: - For full information on the changes contained in this release, please - refer to the Git commit logs. Further release information and tarballs - are available at: - - https://github.com/sosreport/sos/releases/tag/4.7.0 - - Please report any problems to the sos-devel mailing list, or the GitHub - issue tracker: - - https://github.com/sosreport/sos/issues/ - - The team would like to thank everyone who contributed fixes, new - features, testing, and feedback for this release. + * runtime/lxd We have added an LXD runtime so that we can gather data directly from LXD, same with what one would do with k8s. + * plugins/canonical_livepatch_onprem.py will gather data from livepatch-server + * plugins/ceph.py add Reef release commands and gather microceph data + * plugins/coredump.py will capture coredump info from coredumpctl + * plugins/infinidat.py will gather data from servers that make use if the Infinidat storage solution + * plugins/kubernetes.py will now gather container information from microk8s + * plugins/mellanox_firmware.py will gather data from mellanox devices + * plugins/openstack_masakari.py will gather data from openstack masakari + * plugins/openstack_masakarimonitors.py will gather data from openstack masakari monitors + * plugins/vectordev.py will gather the config from vectordev (cos-proxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.7.0 This release focused on expanding support in policies for more and multiple package managers. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates [WHERE PROBLEMS COULD OCCUR] The changes in sosreport are described below. There are a number of changes related to report, plugins and policy. The changes in sosreport content may break existing tooling, so that will need extensive testing. ## Global Changes + Added support for `S3` uploads. ## Policy Changes + Fixed `dist_version()` for Ubuntu. - + Dropped the `RedHatAtomic` policy. - + Changed the authentication for RHEL uploads to use device auth instead of username/password. ## Report Changes + Added a new preset for `app_eda` (Ansible Automation Platform Event Drive Ansible). ### Plugin Changes + New plugins: `aide`, `app_eda`, `coredump`', `infinidat`, `vectordev`. + The `networking` plugin now uses a predicate for `ss` commands on Ubuntu. + Enabled the `kubernetes` plugin for Debian. + Dropped the `atomic` plugin. + Fixed an issue with the command predicate for the `lxd` plugin when enabled via a snap. + The `nvme` plugin now collects additional files per nvme drive on the host. ## Collect Changes + Added a transport for `Saltstack`. ## Cleaner Changes + `clean` will no longer try to obfuscate words that are 3 characters or less in length. + `clean` will now properly obfuscate the upload password (if provided) in our own logs. For full information on the changes contained in this release, please refer to the Git commit logs. Further release information and tarballs are available at: https://github.com/sosreport/sos/releases/tag/4.7.0 Please report any problems to the sos-devel mailing list, or the GitHub issue tracker: https://github.com/sosreport/sos/issues/ The team would like to thank everyone who contributed fixes, new features, testing, and feedback for this release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047796] Re: autoinstall: user-data validation fails for users or packages if they contain list of object
Is this on its way to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047796 Title: autoinstall: user-data validation fails for users or packages if they contain list of object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2047796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695934] Re: no information about snap updates
Pinging to get this additional attention. Based on casework and personal experience, the ability to conclusively see a longer history of snap changes would be helpful in diagnosing latent symptoms, whether they occur late, get noticed late, or the triage happens late. This is especially important as more and more services are delivered as snaps (i.e. kubelet), where an unplanned restart can be an undesired surprise. `snap changes` seems to be an ideal mechanism for this, where at least the timestamps provided would point us to the proper section of other possible log sources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695934 Title: no information about snap updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1695934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
