[Bug 2081625] Re: Removing libfuse2 also removes flatpak
> I believe Flatpak does not need libfuse2 to function I believe it does. You can check for yourself with "apt-cache show flatpak" – look for the mentioning of libfuse2 in the Depends line (or use grep). (Not running Ubuntu myself, but I checked against the jammy universe Packages file on a mirror. In newer release it will be libfuse3) ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081625 Title: Removing libfuse2 also removes flatpak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2081625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081195] [NEW] logging to `/var/log/tomcat9/catalina.out` is duplicated to `/var/log/syslog`
Public bug reported:
Ubuntu Release :: `lsb_release -rd`:
> Description: Ubuntu 22.04.5 LTS
> Release: 22.04
Package version :: `apt-cache policy tomcat9`:
> tomcat9:
> Installed: 9.0.58-1ubuntu0.1
> Candidate: 9.0.58-1ubuntu0.1
> Version table:
> *** 9.0.58-1ubuntu0.1 500
> 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu
> jammy-updates/universe amd64 Packages
> 100 /var/lib/dpkg/status
> 9.0.58-1 500
> 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu jammy/universe
> amd64 Packages
What I expected to happen:
The default `/etc/rsyslog.d/tomcat9.conf` (replicated below) _intends_
to send `tomcat9` logging to `/var/log/tomcat9/catalina.out` (according
to the `action(...)` directive) and - nowhere else - (according to the
`stop` directive):
```
# Send Tomcat messages to catalina.out when using systemd
$template
TomcatFormat,"[%timegenerated:::date-year%-%timegenerated:::date-month%-%timegenerated:::date-day%
%timegenerated:::date-hour%:%timegenerated:::date-minute%:%timegenerated:::date-second%]
[%syslogseverity-text%]%msg%\n"
:programname, startswith, "tomcat9" {
action(type="omfile" file="/var/log/tomcat9/catalina.out"
Template="TomcatFormat" fileCreateMode="0640")
stop
}
```
What happened instead:
However, because this file's name (`tomcat9.conf`) causes it to be
processed _after_ `/etc/rsyslog.d/50-default.conf` tomcat9's logs are
still being sent to `/var/log/syslog`.
Why? Because the latter file has this directive:
```
+*.*;auth,authpriv.none -/var/log/syslog
```
Solution:
If `tomcat9.conf` was renamed - say - to `30-tomcat9.conf` for instance,
it would get processed _before_ `50-default.conf` and _then_ the `stop`
directive would have the intended effect.
** Affects: tomcat9 (Ubuntu)
Importance: Undecided
Status: New
** Tags: syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081195
Title:
logging to `/var/log/tomcat9/catalina.out` is duplicated to
`/var/log/syslog`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/2081195/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] Re: [SRU] add debian/patches/install-missing-files.patch from upstream
** Attachment added: "lp2076432-verification.txt" https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+attachment/5819174/+files/lp2076432-verification.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076432 Title: [SRU] add debian/patches/install-missing-files.patch from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] Re: [SRU] add debian/patches/install-missing-files.patch from upstream
Hi, the verification has been done, and the tests as per the description were successful, I have attached on comment #10 the verification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076432 Title: [SRU] add debian/patches/install-missing-files.patch from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080527] Re: smb protocol missing in dolphin
I confirm it works in Dolphin with the 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/2080527 Title: smb protocol missing in dolphin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/2080527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066184] Re: [24.04] Display won't suspend after monitor sleep delay
Just wanted to confirm I see the same issue with Wayland sessions. With X session, the monitor does suspend as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066184 Title: [24.04] Display won't suspend after monitor sleep delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autosuspend/+bug/2066184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078533] Re: Realtek b851 Wifi Card Doesn't work
OK, I got it fixed but I'm not 100% sure how it was fixed. Earlier I followed your instruction (Turned it off, disconnected power, held power button for 30 seconds), turned it on and it wasn't working. I then went into the BIOS, reset to defaults and tested it but the WiFi card was still not working. Today I decided to open the laptop up to try and find the CMOS battery, but it looks like you need to disassemble about 90% of this laptop just to get to the CMOS battery (I'm assuming it's behind the motherboard like some other ASUS laptops, because it's not visible when I open the cover). I then decided to close it up without fully disassembling it and write back to you what I'd done so far, however I noticed that the WiFi was suddenly working. Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078533 Title: Realtek b851 Wifi Card Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-config/+bug/2078533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074]
(In reply to Amin Bandali [:bandali] from comment #23) > (In reply to david from comment #22) > > Same probleme here with ubuntu 24.04.1, and firefox snap. > > > > "Failed to connect to the native host." > > Hello, could you please provide more information about this? > > - Is this a fresh Ubuntu 24.04 LTS installation? Or did you upgrade from an > existing Ubuntu release to this one? (If yes, from which version?) > - Please open a terminal, run the following commands, and provide the output > here: > ``` > apt list --installed | grep xdg-desktop-portal > apt-cache policy xdg-desktop-portal > snap version > ``` > - Which Firefox version are you using? > - Which Firefox add-on are you trying to use here? And did you add a manifest > for it under the `~/.mozilla/native-messaging-hosts/` directory? > - Are there any more error or warning messages in the logs beyond the one > line you provided? > > Thanks. Hi, - This is not a fresh ubuntu install (its a upgraded version from ubuntu 22.04 LTS), BUT, I'm using a fresh account to test (new user, new /home). - This is the output of the commands: apt list --installed | grep xdg-desktop-portal xdg-desktop-portal-gtk/noble,now 1.15.1-1build2 amd64 [installed,automatic] xdg-desktop-portal-kde/noble,now 5.27.11-0ubuntu3 amd64 [installed,automatic] xdg-desktop-portal/noble-updates,now 1.18.4-1ubuntu2 amd64 [installed,automatic] apt-cache policy xdg-desktop-portal xdg-desktop-portal: Installed: 1.18.4-1ubuntu2 Candidate: 1.18.4-1ubuntu2 Version table: *** 1.18.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.18.3-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu noble/main amd64 Packages snap version snap2.63.1+24.04 snapd 2.63.1+24.04 series 16 ubuntu 24.04 kernel 6.8.0-41-generic - Firefox version is 130.0 (64-bit) - The firefox addon I'm trying to use is: https://addons.mozilla.org/en-US/firefox/addon/plasma-integration/. I did **not** add a manifest for it under ~/.mozilla/native-messaging-hosts/ directory. - On the extension console, I can see the messages: Invalid url undefined action_popup.js:86:33 Failed to check for whether media controls are blocked NO_ORIGINS action_popup.js:279:17 and in about:debugging#/runtime/this-firefox i see: Warning details Reading manifest: Warning processing key: An unexpected property was found in the WebExtension manifest. if I try to reload the addon I get: Host disconnected An unexpected error occurred extension.js:204:17 Not auto-restarting host as we haven't received any message from it before. Check that it's working/installed correctly extension.js:226:21 Background event page was not terminated on idle because a DevTools toolbox is attached to the extension. _generated_background_page.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074]
Same probleme here with ubuntu 24.04.1, and firefox snap. "Failed to connect to the native host." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
Hi @hectorcao, Good to know. Thanks for the info! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
Hi, Will the fix be merged into 24.04? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070371 Title: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2070371/+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
Hi, I have verified that the patch is indeed now functioning and enabling max_age_days does not output any error, and the log files are cleared. I did not capture the output of `ls /var/log/libvirt/*` log at the time of VM creation, but I did see the files there, and now they are gone. lp-2072647-proposed-install-setup.txt has the installation and setup steps of virtlogd/libvirt lp-2072647-verification.txt has the verification that there are no errors and logs are cleared. -- 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
** Attachment added: "lp-2072647-verification.txt" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5816748/+files/lp-2072647-verification.txt -- 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
** Attachment added: "lp-2072647-proposed-install-setup.txt" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5816747/+files/lp-2072647-proposed-install-setup.txt -- 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 2035993] Re: [needs-packaging] himmelblau needs packaging
See my himmelblau ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035993 Title: [needs-packaging] himmelblau needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2035993/+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
armhf tests have now passed [1] and there isn't any other regression reported [1] https://autopkgtest.ubuntu.com/run/66f2d865-76ba-4ebd-936a-d79a8660608e -- 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 2078533] Re: Realtek b851 Wifi Card Doesn't work
output of dmesg on pastebin: https://pastebin.com/bDr3eeke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078533 Title: Realtek b851 Wifi Card Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-config/+bug/2078533/+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
The regression doesn't seem related to the change that we are introducing, tests have been re-triggered by Dariusz Gadomski as per my request. -- 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 2078917] Re: Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17
** Package changed: mdadm (Ubuntu) => kernel-package (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078917 Title: Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2078917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] Re: [SRU] add debian/patches/install-missing-files.patch from upstream
I have added more information in the description of the ticket,
hopefully this clarifies better what we are trying to fix and the test
cases, hence re-subscribing sponsors.
** Description changed:
[ Impact ]
- * Currently the rally package in Jammy and previous versions of Ubuntu do
not contain the
-necessary migration scripts in rally/common/db/migrations/versions/.
- * This SRU aims to backport the same modification made upstream [1] [2] on
rally package 3.3.0-2
-which can be seen on the debdiff on the ubuntu source as well [3] [4]
-
+ * Currently one is unable to create the rally database with the command
'rally db create' as it will output the following error:
+# rally db create
+ Creating database: sqlite:tmp/rally.sqlite
+ Command failed, please check log for more info
+ 2024-09-06 07:49:41.246 7972 CRITICAL rally [-] Unhandled error:
alembic.util.exc.CommandError: No config file
'/usr/lib/python3/dist-packages/rally/common/db/alembic.ini' found, or file has
no '[alembic]' section
+ 2024-09-06 07:49:41.246 7972 ERROR rally Traceback (most recent call last):
+ 2024-09-06 07:49:41.246 7972 ERROR rally File "/usr/bin/rally", line 10, in
+ 2024-09-06 07:49:41.246 7972 ERROR rally sys.exit(main())
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/rally/cli/main.py", line 40, in main
+ 2024-09-06 07:49:41.246 7972 ERROR rally return cliutils.run(sys.argv,
categories)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/rally/cli/cliutils.py", line 669, in run
+ 2024-09-06 07:49:41.246 7972 ERROR rally ret = fn(*fn_args, **fn_kwargs)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/rally/cli/commands/db.py", line 44, in create
+ 2024-09-06 07:49:41.246 7972 ERROR rally db.schema.schema_create()
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/rally/common/db/schema.py", line 139, in
schema_create
+ 2024-09-06 07:49:41.246 7972 ERROR rally schema_stamp("head",
config=config)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/rally/common/db/schema.py", line 152, in
schema_stamp
+ 2024-09-06 07:49:41.246 7972 ERROR rally return
alembic.command.stamp(config, revision)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/alembic/command.py", line 579, in stamp
+ 2024-09-06 07:49:41.246 7972 ERROR rally script =
ScriptDirectory.from_config(config)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/alembic/script/base.py", line 150, in
from_config
+ 2024-09-06 07:49:41.246 7972 ERROR rally script_location =
config.get_main_option("script_location")
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/alembic/config.py", line 309, in get_main_option
+ 2024-09-06 07:49:41.246 7972 ERROR rally return
self.get_section_option(self.config_ini_section, name, default)
+ 2024-09-06 07:49:41.246 7972 ERROR rally File
"/usr/lib/python3/dist-packages/alembic/config.py", line 282, in
get_section_option
+ 2024-09-06 07:49:41.246 7972 ERROR rally raise util.CommandError(
+ 2024-09-06 07:49:41.246 7972 ERROR rally alembic.util.exc.CommandError: No
config file '/usr/lib/python3/dist-packages/rally/common/db/alembic.ini' found,
or file has no '[alembic]' section
+ 2024-09-06 07:49:41.246 7972 ERROR rally
+
+ * Currently the rally package in Jammy and previous versions of Ubuntu do
not contain the
+ necessary migration scripts in rally/common/db/migrations/versions/ to
create the database.
+ * This SRU aims to backport the same modification made upstream [1] [2] on
rally package 3.3.0-2
+ which can be seen on the debdiff on the ubuntu source as well [3] [4]
+
[ Test Plan ]
- * Ensure the files under
/usr/lib/python3/dist-packages/rally/common/db/migrations/versions/
-do exist.
+ * Ensure the files under
/usr/lib/python3/dist-packages/rally/common/db/migrations/versions/
+ do exist.
+ * run the command 'rally db create' and 'rally db upgrade' which should
output the following:
+ # rally db create
+ Creating database: sqlite:tmp/rally.sqlite
+ Database created successfully
+# rally db upgrade
+ Upgrading database: sqlite:tmp/rally.SQLite
+ Database is already up to date
+ * query the database with 'sqlite3 /tmp/rally.sqlite' and run the command
'.tables' inside the sqlite3 cli to ensure tables are created.
+# sqlite3 /tmp/rally.sqlite
+SQLite version 3.37.2 2022-01-06 13:25:41
+Enter ".help" for usage hints.
+sqlite> .tables
+alembic_version subtasks verificationsworkloads
+envs tags verifiers
+platformstasksworkloaddata
+
[ Where problems could occur ]
- * Since this is just adding static fil
[Bug 2064906] Re: White screen and Screen Flickering
Since I've modified my /etc/default/grub to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1 nvidia- drm.fbdev=1 amdgpu.sg_display=0" and reinstalled grub I haven't had the issue again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064906 Title: White screen and Screen Flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078917] [NEW] Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17
Public bug reported: Description: Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P + NVidia L40 GPU in slot17. There is a random write to VF BAR0's memory region that causes the kernel got MCE error. Version-Release number : Ubuntu 24.04 How reproducible: Each time Steps to reproduce - PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS - Run a fresh install on a DL380a server with 2P with GPU (NVidia L40) in slot17 Expected results No MCE and run installation w/o problem Actual results The kernel got MCE errors. Additional info: We have tracked this issue with RHEL9.4, it's caused by the following pathes. cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge (v6.8-rc1) 388d76175bd9 perf/x86/intel/uncore: Support IIO free-running counters on GNR (v6.8-rc1) 632c4bf6d007 perf/x86/intel/uncore: Support Granite Rapids (v6.8-rc1) b560e0cd882b perf/x86/uncore: Use u64 to replace unsigned for the uncore offsets array (v6.8-rc1) cf35791476fc perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO format of SPR (v6.8-rc1) ** Affects: mdadm (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/2078917 Title: Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2078917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078917] Re: Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17
Intel gave us a patch set that resolves the issue. https://lore.kernel.org/lkml/20240614134631.1092359-1-kan.li...@linux.intel.com/#r The following patches are required. f8a86a9bb5f7 perf/x86/intel/uncore: Support HBM and CXL PMON counters (v6.11-rc1) 15a4bd51853b perf/x86/uncore: Cleanup unused unit structure (v6.11-rc1) f76a8420444b perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (v6.11-rc1) b1d9ea2e1ca4 perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (v6.11-rc1) 80580dae65b9 perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (v6.11-rc1) 585463fee642 perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (v6.11-rc1) c74443d92f68 perf/x86/uncore: Support per PMU cpumask (v6.11-rc1) 0007f3932592 perf/x86/uncore: Save the unit control address of all units (v6.11-rc1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078917 Title: Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + NVidia L40 GPU in slot17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2078917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
Having the same issue with external monitor occasional flicker. Moving the mouse stops the flicker when it occurs. Happens every 15 to 30 minutes. Adding intel_iommu=igfx_off to /etc/default/grub resolved the issue for me too. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=igfx_off" VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2064906] Re: White screen and Screen Flickering
I believe this is related to the issue: [15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340399] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.340523] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413008] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413405] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413602] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.413734] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488278] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.488855] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15868.489002] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [15891.489272] amd_iommu_report_page_fault: 124770 callbacks suppressed [15891.489280] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c0 flags=0x] [15891.489298] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c01000 flags=0x] [15891.489309] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c02000 flags=0x] [15891.489319] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c03000 flags=0x] [15891.489328] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c04000 flags=0x] [15891.489338] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c05000 flags=0x] [15891.489347] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c06000 flags=0x] [15891.489357] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c07000 flags=0x] [15891.489366] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c1 flags=0x] [15891.489376] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c24000 flags=0x] [15896.519458] amd_iommu_report_page_fault: 46926 callbacks suppressed [15896.519472] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15896.519492] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15896.519503] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15896.519513] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15896.519522] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15896.519531] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15896.519541] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f6000 flags=0x] [15896.519551] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f7000 flags=0x] [15896.519561] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f8000 flags=0x] [15896.519570] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x4c68000 flags=0x] [15901.549675] amd_iommu_report_page_fault: 79773 callbacks suppressed [15901.549687] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f flags=0x] [15901.549708] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f1000 flags=0x] [15901.549719] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f2000 flags=0x] [15901.549738] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f3000 flags=0x] [15901.549748] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f4000 flags=0x] [15901.549759] amdgpu :65:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0x47f5000 flags=0x] [15901.549771] amdgpu
[Bug 2078533] Re: Realtek b851 Wifi Card Doesn't work
Done. It said something along the lines of Apport no additional data collected once I authorised access. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078533 Title: Realtek b851 Wifi Card Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-config/+bug/2078533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064906] Re: White screen and Screen Flickering
I also have this problem with an Acer Nitro 17 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics 6.8.0-41-generic Nvidia 4060 32GB Ubuntu 24.04.1 LTS I can sometimes trigger it by using OrcaSlicer and manipulating 3D objects I'm going to print. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064906 Title: White screen and Screen Flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078533] [NEW] Realtek b851 Wifi Card Doesn't work
Public bug reported: I recently bought an ASUS X1504VAP-NJ815W and attempted to install a fresh Kubuntu LTS 24.04.1. Nearly everything works except the Wifi driver. No Wifi connection ability shows in the Network-config. I am able to connect it to the internet using a USB to Ethernet device. After conducting fault finding with jeremy31 on ubuntuforums.org, he's recommended to raise the bug report here. The output from the Wireless Info Script is located here: https://pastebin.com/x0SAGqty The original Ubuntu Forums post is located here: https://ubuntuforums.org/showthread.php?t=2500135 I also raised the same question on Ask Ubuntu and the URL for this is here: https://askubuntu.com/questions/1524301/realtek-b851-wifi-card-doesnt-work-in-ubuntu Any help would be greatly appreciated. ** Affects: network-config (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/2078533 Title: Realtek b851 Wifi Card Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-config/+bug/2078533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078448] [NEW] 3rd party (PostgreSQL) package shouldn't be removed, upgrade tool wants to remove it thoug and is blocked by that
Public bug reported: I have PostgreSQL 12 installed from PostgreSQL repository with partman extension. Upgrade tool wants to remove it for some strange reason and crashes ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Aug 30 13:10:31 2024 InstallationDate: Installed on 2018-06-06 (2276 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-08-30 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy 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/2078448 Title: 3rd party (PostgreSQL) package shouldn't be removed, upgrade tool wants to remove it thoug and is blocked by that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066035] Re: KWM Switch causes logout
Not sure what is the root cause but there seems to be a problem in the interaction between Nvidia driver and /usr/libexec/gdm-x-session. I couldn't say if it's originating from Nvidia proprietary driver or in the way Gnome talks to it... Here is an extract from the logs. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2066035/+attachment/5810209/+files/gnome_x_bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066035 Title: KWM Switch causes logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2066035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077976] [NEW] mlxbf_livefish: driver build fails if CONFIG_ACPI not set
Public bug reported: SRU Justification: [Impact] The mlxbf_livefish driver depends on CONFIG_ACPI but that requirement is not specified in the driver's Kconfig. So, any attempt to build a kernel with CONFIG_ACPI not set and CONFIG_MLXBF_LIVEFISH set will result in a build error. [Fix] * Update the Kconfig file in drivers/platform/mellanox to specify the CONFIG_ACPI dependency [Test Case] * Clear CONFIG_ACPI in kernel configuration * Verify there is no option to configure mlxbf_livefish driver * Verify that no build errors result [Regression Potential] * no known regression. ** 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/2077976 Title: mlxbf_livefish: driver build fails if CONFIG_ACPI not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2077976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077836] [NEW] PDF Arranger fails to start due to user site packages
Public bug reported: Hello, I'm one of the upstream maintainers of PDF Arranger and we got some complaints from ubuntu users which were unable to start the apt/deb package in ubuntu 22.04. This is most likely due to incompatible pikepdf versions which the users installed via pip. To mitigate this, I suggest you patch the /usr/bin/pdfarranger entry script to add a `-s` flag (better yet `-sP` as soon as the Python version supports it) to the python interpreter call in the first line (shebang). This should prevent python to load incompatible module versions from the home directory. I do not have a solutions for users which installed stuff via "sudo pip", I guess they just made a mistake using their admin privileges which we can not work around. From my point of view it would be much better if users would get more recent versions of pikepdf (>= 6 should be enough) and PDF Arranger (the newer the better) but that might not be possible with a LTS version. (We got a few bug reports for stuff that has been fixed for a long time upstream and newer PDF Arranger versions are compatible with newer pikepdf versions users might accidentally install.) Thanks for your work as package mantainer and let me know if I can be of assistance. David To the reports: https://github.com/pdfarranger/pdfarranger/discussions/1017 ** Affects: pdfarranger (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/2077836 Title: PDF Arranger fails to start due to user site packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfarranger/+bug/2077836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077655] [NEW] document save pc sleepmode
Public bug reported: when try to save document laptop goes into sleepmode screen dims libreoffice unconciuos ** Affects: libreoffice (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/2077655 Title: document save pc sleepmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2077655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072775] Re: Fastmail's WebDav, CalDav and CardDav is buggy
I installed gnome-online-accounts 3.50.4-0ubuntu2 in Ubuntu 24.04, but it still doesn't seem to fix the issue. This is what worked for me: I open GNOME's settings, navigated to Online Accounts, clicked "Calendar, Contacts and Files | WebDAV", and entered these details: Server Address: https://webdav.fastmail.com/ Username: Your Email address (e.g. usern...@domain.tld) Password: Your DAV (CalDAV/CardDAV/WebDAV) app password Now I can see Fastmail files in Nautilus, I can see Fastmail calendars in GNOME Calendar, and I can see Fastmail contacts in GNOME Contacts. I had to leave the "Files", "Calendar (CalDAV)" and "Contacts (CardDAV)" fields blank for it to work correctly. Otherwise, I would get a "Try again" error, or a SIGSEGV (Address boundary error) crash. For me, this bug is now fixed, since there now is a way to get Fastmail to work. If I have more time, I may report the other bugs upstream. -- 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 2073390] Re: SRU: backport GCC 14 to 24.04 LTS
We require gcc 14.2 minimum for our project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073390 Title: SRU: backport GCC 14 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-14/+bug/2073390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077083] Re: Secure boot to grub broken by Windows 2024/08 upgrades
** Tags added: dual-boot grub sbat secure-boot shim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077083 Title: Secure boot to grub broken by Windows 2024/08 upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2077083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077083] Re: Secure boot to grub broken by Windows 2024/08 upgrades
https://forums.linuxmint.com/viewtopic.php?t=427297 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077083 Title: Secure boot to grub broken by Windows 2024/08 upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2077083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077083] Re: Secure boot to grub broken by Windows 2024/08 upgrades
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077083 Title: Secure boot to grub broken by Windows 2024/08 upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2077083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] Re: [SRU] add debian/patches/install-missing-files.patch from upstream
Initially this was a request to have those scripts available in order to run the db migrations run properly for rally, I will investigate further and get back with a better action/test plan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076432 Title: [SRU] add debian/patches/install-missing-files.patch from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+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
Hi Mitchel, Thanks for the update. I'm happy to hear the fix is now in Oracular. Dan, I have now uploaded a debdiff with a different changelog. Let me know if the format is okay. -- 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
** Patch added: "lp2072647-noble-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5805655/+files/lp2072647-noble-libvirt.debdiff -- 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 2072775] Re: Fastmail's WebDav, CalDav and CardDav is buggy
I can't find gnome-online-accounts 3.50.4-0ubuntu2 in the noble-proposed repositories, so I haven't been able to test this yet. -- 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 2076535] [NEW] package linux-headers-6.8.0-40-generic 6.8.0-40.40 failed to install/upgrade: installed linux-headers-6.8.0-40-generic package post-installation script subprocess returned error ex
Public bug reported: Nothing to provide - update was being installed in the background apparently. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-40-generic 6.8.0-40.40 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:david 2643 F pipewire /dev/snd/controlC0: david 2649 F wireplumber /dev/snd/controlC1: david 2649 F wireplumber /dev/snd/controlC2: david 2649 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown Date: Fri Aug 9 06:12:04 2024 ErrorMessage: installed linux-headers-6.8.0-40-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-06-11 (61 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Apple Inc. MacBookPro14,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic root=UUID=77953b49-2b6a-4542-8a6e-f667c3c3581a ro quiet splash init_on_alloc=0 vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-40-generic 6.8.0-40.40 failed to install/upgrade: installed linux-headers-6.8.0-40-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2024 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 529.120.1.0.0 dmi.board.name: Mac-B4831CEBD52A0C4C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B4831CEBD52A0C4C dmi.modalias: dmi:bvnAppleInc.:bvr529.120.1.0.0:bd03/14/2024:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** 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/2076535 Title: package linux-headers-6.8.0-40-generic 6.8.0-40.40 failed to install/upgrade: installed linux-headers-6.8.0-40-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/2076535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] Re: [SRU] add debian/patches/install-missing-files.patch from upstream
** Patch added: "lp2076432.debdiff" https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+attachment/5804116/+files/lp2076432.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076432 Title: [SRU] add debian/patches/install-missing-files.patch from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076432] [NEW] [SRU] add debian/patches/install-missing-files.patch from upstream
Public bug reported: [ Impact ] * Currently the rally package in Jammy and previous versions of Ubuntu do not contain the necessary migration scripts in rally/common/db/migrations/versions/. * This SRU aims to backport the same modification made upstream [1] [2] on rally package 3.3.0-2 which can be seen on the debdiff on the ubuntu source as well [3] [4] [ Test Plan ] * Ensure the files under /usr/lib/python3/dist-packages/rally/common/db/migrations/versions/ do exist. [ Where problems could occur ] * Since this is just adding static files to the package, but not taking any action on them, there should be no risks associated with this change. [1] https://metadata.ftp-master.debian.org/changelogs//main/r/rally/rally_3.3.0-2_changelog [2] https://sources.debian.org/patches/rally/3.3.0-2/install-missing-files.patch/ [3] https://launchpad.net/ubuntu/+source/rally/3.3.0-2 [4] https://launchpadlibrarian.net/664611856/rally_3.3.0-1_3.3.0-2.diff.gz ** Affects: rally (Ubuntu) Importance: Undecided Assignee: David Negreira (dnegreira) Status: In Progress ** Affects: rally (Ubuntu Jammy) Importance: Undecided Assignee: David Negreira (dnegreira) Status: In Progress ** Changed in: rally (Ubuntu) Assignee: (unassigned) => David Negreira (dnegreira) ** Changed in: rally (Ubuntu) Status: New => In Progress ** Also affects: rally (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: rally (Ubuntu Jammy) Assignee: (unassigned) => David Negreira (dnegreira) ** Changed in: rally (Ubuntu Jammy) Status: New => 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/2076432 Title: [SRU] add debian/patches/install-missing-files.patch from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rally/+bug/2076432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076317] [NEW] Enable systemd-logind API in compilation options
Public bug reported: Hello, I've been made to understand that brightnessctl should not require root privileges to effectively modify the screen's brightness, but ubuntu's version still is not usable without tweaking the environment a bit. According to the readme, 3 ways are available, but the least demanding for users would be to enable the systemd-logind API in the binary, no longer requiring users to add themselves into the video/input groups, nor having the binary as a setuid binary. It seems this should be doable through the update of the compilation options of the binary, via the make define `-D ENABLE_SYSTEMD`. That being said, for future proofness, brightnessctl's master branch seems to rely on a new approach based on a configure script which takes a CLI option instead. ** Affects: brightnessctl (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/2076317 Title: Enable systemd-logind API in compilation options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brightnessctl/+bug/2076317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
@kees Thanks for jumping on this thread! From a technical perspective I agree with you, but I would reason that it's not really a change one would want end-users of the Ubuntu LTS kernel to implement. It comes back to the reasoning mentioned by @Andy in #70 and @Gustav in #73: a kernel update on a LTS kernel really shouldn't break previously running software, and I would add that a normal package update via apt shouldn't require the user to have to tinker with the kernel boot parameters before getting a working system again. Unless there is some way for the package upgrade to automatically alter the boot parameters? (Although even if possible, this is probably not desired behaviour from a package upgrade either) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
@mruffell Perhaps I'm missing something, but the kernel discussion thread you linked specifically ends with "The CVE has now been rejected, thanks for the review!". Surely that means that the Ubuntu team can revert the commit then? (unless you are of the opinion that the security vulnerability the commit addresses is serious enough that the change has to be kept regardless of CVE status?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074123] [NEW] mlxbf_gige: packets received before RX path fully init
Public bug reported: SRU Justification: [Impact] During the reboot and power cycle testing, QA found an intermittent issue where "oob_net0" interface would experience RX MAC errors and fail to get a DHCP-assigned IP. There is a small window where packets can be received before the RX path is fully initialized, sometimes resulting in RX errors or RX ring full condition. [Fix] * Disable MAC RX filters in driver's probe() and only enable these RX filters in driver's open() when all initialization is completed. [Test Case] * On BlueField-2 and BlueField-3, do reboot and power cycle testing * Check that "oob_net0" interface is up, IP is assigned, and there are no RX errors. [Regression Potential] * no known regression. ** 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/2074123 Title: mlxbf_gige: packets received before RX path fully init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2074123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066087] Re: KDE Discover crashes once open after clicking on Apps or Modules (update issue ?)
I just started seeing the same behavior. Yesterday I added flathub to the flatpak remote list. I was able to work around it by disabling the discover flatpak plug-in. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066087 Title: KDE Discover crashes once open after clicking on Apps or Modules (update issue ?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2066087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Guru meditation on VM start
@Kevin yes. It really depends on the extent of changes between major versions of virtualbox as to whether it will _always_ be required, but it is at least necessary in the 6.1 -> 7 migration case. AFAICT Oracle never released an official VM migration guide with the release of virtualbox 7, but based on the bug reports on Stack Overflow, the Virtualbox threads, and my own experience, I think its safe to say that the Windows Guest Additions driver in 6.1 is definitely not compatible with Virtualbox 7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Guru meditation on VM start
@Kevin you need to remove (uninstall) the guest additions from the VM before upgrading to virtualbox 7. (This is true when migrating any VM between major virtualbox versions - even if both work correctly with the same kernel version on the Host). Shortly: 1. Boot Windows Guest VM with Virtualbox 6.1 (and an older Linux kernel to get around the original issue). 2. Remove (uninstall) the Guest additions. (As a sanity check, it may be worth ensuring that your guest VM can boot without the Guest additions installed; if not, adjust the client VM config as required). 3. Uninstall virtualbox 6.1 and the virtualbox 6.1 extension pack 4. Install virtualbox 7 (and the virutalbox 7 extension pack if required) 5. Boot the Windows Guest VM in virtualbox 7 Note: Setting the paravirtualization interface to the "default" option in virtualbox 7 may result in the guest VM perpetually booting into repair mode. Set the paravirtualization explicitely to "Hyper-V" (what Windows actually requires) or "KVM" (this option worked in my case - haven't explicitely tested Hyper-V yet) 6. Install the virtualbox 7 guest additions in your guest VM again. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Guru meditation on VM start
@Kevin you need to remove (uninstall) the guest additions from the VM before upgrading to virtualbox 7. (This is true when migrating any VM between major virtualbox versions - even if both work correctly with the same kernel version on the Host). Shortly: 1. Boot Windows Guest VM with Virtualbox 6.1 (and an older Linux kernel to get around the original issue). 2. Remove (uninstall) the Guest additions. (As a sanity check, it may be worth ensuring that your guest VM can boot without the Guest additions installed; if not, adjust the client VM config as required). 3. Uninstall virtualbox 6.1 and the virtualbox 6.1 extension pack 4. Install virtualbox 7 (and the virutalbox 7 extension pack if required) 5. Boot the Windows Guest VM in virtualbox 7 Note: Setting the paravirtualization interface to the "default" option in virtualbox 7 may result in the guest VM perpetually booting into repair mode. Set the paravirtualization explicitely to "Hyper-V" (what Windows actually requires) or "KVM" (this option worked in my case - haven't explicitely tested Hyper-V yet) 6. Install the virtualbox 7 guest additions in your guest VM again. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Guru meditation on VM start
For what its worth: I have the same issue with Ubuntu 22.04.4 LTS (Desktop). Working kernel (i.e. VM in Virtualbox 6.1 boots): Linux 5.15.0-1061-gke Broken kernel (i.e. VM no longer boots): Linux 5.15.0-1062-gke Workaround: Installed Virtualbox 7 from the Oracle PPA repository and migrated VM with some teething problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+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
Hi Heitor Thanks for your comment/review, I have now added a debdiff for oracular as well as modified the the origin to point to the commit where the fix is done upstream, so this is now ready to be reviewed again, hence I re-subscribed ubuntu-sponsors. -- 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
debdiff for oracular ** Patch added: "lp2072647-oracular-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5798329/+files/lp2072647-oracular-libvirt.debdiff -- 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
debdiff for noble ** Patch removed: "lp2072647-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5795865/+files/lp2072647-libvirt.debdiff ** Patch added: "lp2072647-noble-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5798328/+files/lp2072647-noble-libvirt.debdiff -- 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 2054395] Re: [sru] sos upstream 4.7.2
Hi Alejandro, On the --all-logs issue: Unfortunately we only caught the bug after the 4.7.2 release, so it is already being reported and worked on upstream on the bug you linked. For the secrets in sunbeam/ceilometer we have raised the upstream bug https://github.com/sosreport/sos/issues/3713 to fix it. Thank you for your time testing and providing feedback. ** Bug watch added: github.com/sosreport/sos/issues #3713 https://github.com/sosreport/sos/issues/3713 -- 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.2 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 2066293] Re: External screen Flickering in Ubuntu 24.04
Thanks Daniel, i will log my own report. it was the first time form me here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066293 Title: External screen Flickering in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2066293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066293] Re: External screen Flickering in Ubuntu 24.04
Flickering Display after upgrade from Ubuntu 23.10 to 24.04 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+bug/2066293/+attachment/5797276/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066293 Title: External screen Flickering in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2066293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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
[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
[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 in
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
