Thanks for the bug report.
Next time the freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ System freeze
** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Summary changed:
- Autorotation of screen does not work on wayland, but on X
+ [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
BTW, "ConditionPathIsDirectory" is not new. It's been there for two
years already in Ubuntu 20.04.
If you have experienced a regression then more often that would come
from a kernel update so please try some different kernel versions.
** Also affects: linux (Ubuntu)
Importance: Undecided
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1960709
When reporting bugs in the future please use apport by using 'ubuntu-
bu
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
Sony WF-XB700 Bluetooth headset not detect
Thanks for the bug report.
I can see two problems here, though am not sure if either is the main
issue:
* Timeout, server 21.0.0.52 not responding. Whatever that is, if it's a
server the machine depends on then it might cause a startup failure.
* CurrentDmesg.txt seems to suggest file system cor
Thanks for the bug report. The final entry in your kernel log shows that
the Intel GPU tried and failed to update the screen:
[ 1216.206745] i915 :00:02.0: [drm] *ERROR* Atomic update failure on
pipe A (start=73567 end=73568) time 940 us, min 1073, max 1079, scanline
start 1033, end 1097
So m
** Also affects: libusb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net/bugs/1960768
Title:
fwupd crash on stop
Status in OE
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
[Sony WI-C310] [I
Jonas,
In comment #5 do you mean the fix was released to Ubuntu, or the fix is
only in the Mesa PPA from comment #3?
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** No longer affects: linux (Ubuntu)
** No longer affects: kubuntu-meta (Ubuntu)
** No longer affects: xorg (Ubuntu)
**
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1960448
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Given the message in your kernel log:
Bluetooth: hci0: Ignoring error of Inquiry Cancel command
A similar problem with the same message was a kernel regression:
https://bbs.archlinux.org/viewtopic.php?id=259954
Maybe not related to this bug, but still a reminder that it might be a
kernel re
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seed
This is still on my TODO list but low priority. The reason being this
kind of bug has been observed with every release on a variety of
hardware. I think it fails in more cases than it succeeds, and has
always done so.
If by chance a developer has access to the same specific headset then
the proble
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
This is an ongoing problem with the Nvidia drivers. Now tracking in bug
1876632.
** This bug has been marked a duplicate of bug 1876632
[nvidia] Corrupted/missing shell textures when switching users or r
Sorry, this bug is very old and this version of Ubuntu isn't supported
any more. If you think you have a similar issue, please file a new bug.
** Package changed: fedora => libgweather4 (Ubuntu)
** No longer affects: libgweather4 (Ubuntu)
--
You received this bug notification because you are a
** Changed in: gnome-desktop (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-desktop (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libgweather4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
Julian - correct I was using apt-cacher-ng as per sbuild instructions
here https://wiki.ubuntu.com/SimpleSbuild
Sorry - I've no idea how to configure squid-deb-proxy with sbuild. So
I've deleted my sbuild chroots & disabled using the .mk-sbuildrc proxy.
Installing from a ppa no longer shows 503
For over a decade now, at least, users have continually been puzzled by
this silent refusal. Again, in most contexts, that indicates a failure
of the interface.
Viewed 1.1M times
https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it
Viewed 62k t
It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling
of jobs doesn't stop with an error unless --abort-on-error is specified.
Instead the parser will keep track of the last error and return that
there was an error, but it will keep processing the rest of the jobs.
We did not cl
Nearly anything would be better than the current state of silent
failure. At present, probably many thousands of Ubuntu systems are
reporting the following:
root@system:/home# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculati
It seems you use apt-cacher-ng, please try if the issue reproduces
without it, and if so, if it happens with a known good proxy like squid
(e.g. using deb-squid-proxy).
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Marking as Opinion as David explained why that is not a thing we can
reasonably determine.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.
capture of top output, such CPU use seems suspicious
** Attachment added: "Peek 2022-02-13 18-50.gif"
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+attachment/5560703/+files/Peek%202022-02-13%2018-50.gif
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
`upower --monitor-detail` has shown noninsane battery info twice and is
silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not
all the time, but most of the time it is somehow top user of CPU)
Computer become noticeably laggy recently, `upowerd` is so far so
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1420395 is similar
but with distinct symptoms - here too many updates appear to be not the
cause of insane CPU use
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in
Wow, a reply on a bug report after 6 years! I did not mean this to be
negative, just surprised that I got a response this late. I forgot all
about it, but this brings a lot back. Back then, I was mostly wondering
what was in the mind of someone to change a user-modifiable config
file..
But anyway,
** Description changed:
When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6,
screen rotates properly under X, but not under Wayland.
Also the lock screen rotation option is missing in the top-right menu under
Wayland. It exists in X.
- `iio-sensor-proxy` is loaded corr
Public bug reported:
When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6,
screen rotates properly under X, but not under Wayland.
Also the lock screen rotation option is missing in the top-right menu under
Wayland. It exists in X.
`iio-sensor-proxy` is loaded correctly:
``
Public bug reported:
before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn
off about 3 times.. And all will be freeze it needs to shutdown keeping
pressed the I/O button
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.
Public bug reported:
/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol
lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol:
wl_proxy_marshal_flags
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
Can you provide a complete (preferably real) example of what output you
would expect?
Honestly, I don't see this working as in the general case the reason is
not simple – its at least my experience from staring at debug output for
hours to figure such things out in the development branches of a
di
I'm a bit confused:
* On the one hand, this bug is *not* marked is fixed in AppArmor
upstream; the only reason it was marked as "Fix Released" for Ubuntu is
the pile of kludges added in /lib/apparmor/functions, that I migrated to
rc.apparmor.functions upstream a few years back.
* On the other han
All tests passed already.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in r
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1960582
Title:
[critical] dpkg error while processing
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.5) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
garli/2.1-3build1 (armhf)
fpc/3.0.4+dfsg-23 (armhf)
lazarus/2.0.6+dfsg-3 (armhf)
libuv1/1.34.2-1ubuntu1.3 (i386)
ikiwiki
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.5) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
garli/2.1-3build1 (armhf)
fpc/3.0.4+dfsg-23 (armhf)
lazarus/2.0.6+dfsg-3 (armhf)
libuv1/1.34.2-1ubuntu1.3 (i386)
ikiwiki
38 matches
Mail list logo
