** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1998207
Title:
netplan network-man
"GNOME on Wayland" shows the same behavior as "Ubuntu on Wayland" after
installing the package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/186
Title:
ibus-daemon 170%
Hmm.. OK. So I assume those connections would normally (not using the
netplan integration) be created in /run/NetworkManager/system-
connections/...?
So I think we need to find a way to detect NMS_KEYFILE_STORAGE_TYPE_RUN,
or respectively ignore any connections that are not of
NMS_KEYFILE_STORAGE_
Actually, https://developer-old.gnome.org/NetworkManager/stable/nm-dbus-
types.html#NMSettingsConnectionFlags suggests this could possibly be
avoided, by checking for `!is_external`, too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
andreas, directx-headers was dropped instead, and that upload rejected,
so the current version in proposed builds and is ready for updates.
sorry for the hassle, this was supposed to be the correct path to follow
all along :)
--
You received this bug notification because you are a member of Ubunt
This bug was fixed in the package mesa - 22.0.5-0ubuntu0.3
---
mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium
* crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix
can get through to updates.
mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium
* crocus-fix-leak-i
This bug was fixed in the package mesa - 22.0.5-0ubuntu0.3
---
mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium
* crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix
can get through to updates.
mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium
* crocus-fix-leak-i
nope, reopening so that this will be fixed via the kinetic backport
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launch
** Changed in: ibus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/186
Title:
ibus-daemon 170% CPU when using Flatpak Endeavour
Changing the check as suggested to:
if (!is_volatile && !is_nm_generated && !is_external) {
...
does help and netplan files for tun0 and tun1 are not written anymore.
But, when I create a VPN connection I still have problems.
$ network-manager.nmcli c import type openvpn file
$ network-manager.
Thanks for your testing and detailed analysis!
So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?
Does running 'nmcli connection reload' after the connection profile for
the VPN connection (tun2?) got w
As per description it looks like this bug is also about backporting to Jammy.
Should Jammy need to be added to the Affects table?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/
Hi!
Seeing this line:
Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27)
makes me think you either are trying to upgrade directly from Trusty
(which would be weird given your install medium is Jammy), or have
third-party packages on your system, most likely installed through
Hello Timo, or anyone else affected,
Accepted llvm-toolchain-15 into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-15/1:15.0.6-3~ubuntu0.22.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing th
> So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?
Hm, not sure if we mean the same. That two connections (tun2 and
) appear after connecting to the VPN is expected. NM
recognizes tun2 as "external" as
You have been subscribed to a public bug:
The HP Pro x360 435 G9 has LED indicators built into the F5 key and F8
key to indicate that the Speakers (F5) and Microphone (F8) are muted.
Pressing F5 correctly toggles the output of sound off and on, but the
indicator LED never illuminates. Pressing F8
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2002393
Title:
Speaker Mute and Microphone Mute LED indicators not wo
To reproduce the problem, this should be enough:
1. Create a connection to an OpenVPN server
2. Start the connection. The OpenVPN plugin will create a tunnel interface.
3. "nmcli c" should show a tunX connection and the VPN connection. "nmcli d"
should show tunX as a external connection.
4. Dis
** Also affects: evolution (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: evolution (Ubuntu Jammy)
** Changed in: libcanberra (Ubuntu)
Status: Triaged => In Progress
Thanks! I've added the "!is_external" check to my latest development
patch revision at:
https://github.com/slyon/NetworkManager/commits/netplan-nm-1.40
So this bug report is now mostly about comment #10, where the openvpn
client/plugin is creating a temporary tunX device, which is displayed as
"ex
> Why are you setting d->object to NULL in on_object_disposed? By doing
that you are introducing memory leak, no?
Well the point was that I didn't want this to happen when last reference
was removed, but this can't really happen in a sane setup unless
something played some dirty game with the obje
it's changelog doesn't refer to this bug, so there's little point
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1999336
Title:
New bugfix release 22.2.5
Status in mesa pack
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I compared the upstream release 2011d to 2011j and found the relevant
change:
https://github.com/eggert/tz/commit/7bf85c80a63f31e97134d75313736b792bcd94c6
According to that commit Egypt abandoned DST in 2011. So n
** Changed in: tzdata (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1899343
Title:
tzdata sets /etc/timezone to `/UTC`, not `Et
Knowing the current debconf tzdata code, Steve's statement is still
true. Since there is not enough information to further debug, I am
closing this bug as invalid. If you can reproduce this misbehavior,
please reopen this bug or open a new one.
** Changed in: tzdata (Ubuntu)
Status: Incompl
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On package upgrade, tzdata reads the /etc/localtime symlink. If
/etc/localtime pointed to
/usr/share/zoneinfo/America/Indiana/Indianapolis before the package
upgrade, it is a tzdata bug. Otherwise the problem lies
The dmesg output shows the issue:
[ 1551.176168] sd 2:0:0:0: [sda] Unhandled error code
[ 1551.176172] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 1551.176178] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 2f 93 58 00 00 04 00 00
[ 1551.176193] end_request: I/O error, dev s
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log line:
```
open2: fork failed: Cannot allocate memory at
/usr/share/perl5/Debconf/ConfModule.pm line 59.
```
So your system ran out of memory. Therefore it's not a bug in tzdata.
** Ch
I can reproduce this issue on Ubuntu 18.04 "xenial" (with tzdata
2021a-0ubuntu0.16.04 and coreutils 8.25-2ubuntu3~16.04) by running:
```
TZ=America/Los_Angeles date -d "Sun Mar 12 02:38:57 UTC 2017"
```
The date command is shipped by the coreutils package.
This bug is fixed in coreutils 8.28-1ub
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The bug was reported against an Ubuntu version that
reached end-of-life. Sadly I found no error message in the provided log
that could explain the exit status of 1. Therefore I am marking this bug
as invalid. Feel f
*** This bug is a duplicate of bug 1672111 ***
https://bugs.launchpad.net/bugs/1672111
Relevant dpkg terminal log lines:
```
Current default time zone: 'Australia/Melbourne'
date: invalid date 'Sun Oct 6 02:23:37 UTC 2019'
dpkg: error processing package tzdata (--configure):
subprocess inst
*** This bug is a duplicate of bug 1672111 ***
https://bugs.launchpad.net/bugs/1672111
Relevant dpkg terminal log lines:
```
Current default time zone: 'America/Denver'
date: invalid date 'Sun Mar 10 02:41:21 UTC 2019'
dpkg: error processing package tzdata (--configure):
subprocess installed
*** This bug is a duplicate of bug 1672111 ***
https://bugs.launchpad.net/bugs/1672111
Relevant dpkg terminal log lines:
```
Current default time zone: 'Europe/London'
date: invalid date 'Sun Mar 25 01:58:44 UTC 2018'
dpkg: error processing package tzdata (--configure):
subprocess installed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The bug was reported against an Ubuntu version that
reached end-of-life. Sadly I found no error message in the provided log
that could explain the exit status of 1. Therefore I am marking this bug
as invalid. Feel f
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The bug was reported against an Ubuntu version that
reached end-of-life. Sadly I found no error message in the provided log
that could explain the exit status of 1. Therefore I am marking this bug
as invalid. Maybe
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The relevant part of VarLogDistupgradeApttermlog:
```
Setting up tzdata (2011l-0ubuntu0.11.04) ...
debconf: DbDriver "config": could not open /var/cache/debconf/config.dat
dpkg: error processing tzdata (--configur
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2018e-0ubuntu0.18.04) ...
Use of uninitialized value $reply in scalar chomp at
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log:
```
Paramétrage de tzdata (2011j-0ubuntu0.11.04) ...
Current default time zone: 'Europe/Paris'
Segmentation fault
```
According to the log, debconf was successful and some C binary crashed.
Maybe t
** Tags added: trusty
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1648556
Title:
package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade:
s
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2015g-0ubuntu0.15.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2015d-0ubuntu0.15.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2015a-0ubuntu0.14.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2014c-0ubuntu0.13.10) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2013g-0ubuntu0.12.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2014a-0ubuntu0.13.10) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2012b-0ubuntu0.11.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2016f-0ubuntu0.14.04) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2016d-0ubuntu0.15.10) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log lines:
```
Setting up tzdata (2017c-0ubuntu0.14.04) ...
Use of uninitialized value $reply in s
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log lines:
```
Setting up tzdata (2017b-2) ...
Use of uninitialized value $reply in scalar chomp a
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2016c-0ubuntu0.15.10) ...
Use of uninitialized value $reply in scalar chomp at
*** This bug is a duplicate of bug 1648556 ***
https://bugs.launchpad.net/bugs/1648556
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant log lines:
```
Setting up tzdata (2016b-0ubuntu0.14.04) ...
Use of uninitialized value $reply in scalar chomp at
** Tags added: artful bionic natty precise saucy wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1648556
Title:
package tzdata 2016j-0ubuntu0.16.04 failed to install/up
*** This bug is a duplicate of bug 1800065 ***
https://bugs.launchpad.net/bugs/1800065
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log lines:
```
Setting up tzdata (2021e-0ubuntu0.20.04) ...
Use of uninitialized value $ret in str
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tzdata (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 1800065 ***
https://bugs.launchpad.net/bugs/1800065
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log lines:
```
Setting up tzdata (2018g-0ubuntu0.18.10) ...
Use of uninitialized value $ret in str
** Description changed:
- Al momento de actualizar aplicaciones desde el actualizador marca este
- error y detiene la actualización.
+ The tzdata package fails to upgrade:
+
+ ```
+ Setting up tzdata (2018f-0ubuntu0.18.10) ...
+ Use of uninitialized value $ret in string eq at
/usr/share/perl5/De
** Tags added: focal
** Changed in: tzdata (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1800065
Title:
package tzdata 2018f-0
Lukasz is correct, we should be diligent in backporting the upstream patches.
In regards to testing it's important to ensure apparmor and its new features
work as intended with no errors in logs.
As well as apparmor not quitting after a restart. All three effected LP's
should be thoroughly tes
Public bug reported:
In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc-selinux-
segfault.sh to selinux-segfault.sh . This changes debian/tests/upstream
to reflect the change.
** Affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
Public bug reported:
After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
can only boot into recovery mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
This bug was fixed in the package ubuntustudio-default-settings -
22.04.26.1
---
ubuntustudio-default-settings (22.04.26.1) jammy; urgency=medium
* Revert changes for Jammy for driver manager (LP: #1965439)
-- Erich Eickmeyer Fri, 08 Jul 2022 21:05:27
-0700
** Changed in: ubunt
This bug was fixed in the package software-properties - 0.99.22.4
---
software-properties (0.99.22.4) jammy; urgency=medium
* cloudarchive: Enable support for the Antelope Ubuntu Cloud Archive on
22.04 (LP: #1996067).
-- Corey Bryant Wed, 09 Nov 2022 09:29:26
-0500
** Chang
The verification of the Stable Release Update for software-properties
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package openssh - 1:8.9p1-3ubuntu0.1
---
openssh (1:8.9p1-3ubuntu0.1) jammy; urgency=medium
* d/p/fix-poll-spin.patch: Fix poll(2) spin when a channel's output
fd closes without data in the channel buffer.
(LP: #1986521)
-- Bryce Harrington Tue,
The verification of the Stable Release Update for openssh has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
> # new python script to create vim profiles with
>
> python create-apparmor.vim.py
For the records: create-apparmor.vim.py exists since years, and ...
> # generates a new file called apparmor.vim.in
... it uses apparmor.vim.in as _input_ and generates the apparmor.vim
file (syntax highlighting
Public bug reported:
[Impact]
On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core
driver's own configuration of subordinate interfaces. When the kernel wins this
race, the device cannot be renamed as udev has attempted, and this causes
systemd-network-online.target to ti
hi Lena, actually yes, I can reproduce the same issue with a nitrokey 3A
NFC. I also have an older yubikey 5A but I cannot test with it as its
firmware does not support user verification, only user presence.
** Changed in: openssh (Ubuntu)
Status: Incomplete => New
--
You received this bu
You have been subscribed to a public bug:
Using Ubuntu 22.04 (very recent fresh installation)
QT applications use X11 by default instead of Wayland. This leads to
incomplete menus and all sorts of graphical glitches. The workaround is
to add export QT_QPA_PLATFORM=wayland to .profile. As for the
** Changed in: tzdata (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/772024
Title:
tzdata update keeps changing my timezone
** Changed in: tzdata (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/599466
Title:
tzdata refers to Americas as "America"
** Project changed: launchpad => qtbase-opensource-src (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/2002450
Title:
QT applications don't respect e
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal logs:
```
Setting up tzdata (2016j-0ubuntu0.14.04) ...
Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot
to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Enc
*** This bug is a duplicate of bug 1672111 ***
https://bugs.launchpad.net/bugs/1672111
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Sadly I found no error message in the provided log that
could explain the exit status of 1, but this could be a duplicate o
** Summary changed:
- Bug in Europe/Russia timezones
+ Slow Europe/Russia timezone
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/868395
Title:
Slow Europe/Moscow timezone
Can be reproduces with just setting the TZ environment variable:
```
apt install -y gcc tzdata
printf '#include \n#include \n\nint main() {\n time_t t =
time(0);\n int i;\n struct tm result;\n for(i=0; i < 1000; i++)\n
localtime_r(&t, &result);\n puts(ctime(&t));\n return 0;\n}\n' > bug.c
gc
** Summary changed:
- Slow Europe/Moscow timezone
+ localtime_r multiple times slower for Europe/Moscow timezone
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/868395
Title:
Forwarded to the upstream mailing list:
https://mm.icann.org/pipermail/tz/2023-January/032522.html
** Changed in: tzdata (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ub
Not just Russia - on 22.04:
$ time TZ=Etc/UTC ./bug
Tue Jan 10 23:46:13 2023
real0m0.537s
user0m0.529s
sys 0m0.004s
$ time TZ=Europe/Berlin ./bug
Wed Jan 11 00:46:31 2023
real0m0.677s
user0m0.670s
sys 0m0.004s
$ time TZ=Europe/Moscow ./bug
Wed Jan 11 02:46:50 2023
rea
See https://sourceware.org/bugzilla/show_bug.cgi?id=15943.
** Bug watch added: Sourceware.org Bugzilla #15943
https://sourceware.org/bugzilla/show_bug.cgi?id=15943
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in
Thanks for the bug report.
The problem preventing Xorg from loading appears to be:
intel: waited 2020 ms for i915.ko driver to load
But 'intel' is an old buggy driver that nobody should be using. Please
remove any custom configs in /root/xorg.conf.new and
/usr/share/X11/xorg.conf.d that are lo
** Changed in: fwknop (Ubuntu)
Status: New => Fix Released
** Changed in: fwknop (Ubuntu)
Assignee: (unassigned) => François Marier (fmarier)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
cont
mesa backport will get in proposed soon
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/
85 matches
Mail list logo
