Public bug reported:
During an upgrade from 23.10 to 24.04, while investigating a config
conflict in an interactive sub shell I used ^C to discard the current
command in that shell. Instead of the shell receiving the interrupt
signal and responding in the way it normally did, some other process
I've been running the ubuntu generic kernel (5.13.0-28-generic) for the
last 33 days without the issue reoccurring, so I think this can be
closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942619
https://bugzilla.mozilla.org/show_bug.cgi?id=1756170
** Bug watch added: Mozilla Bugzilla #1756170
https://bugzilla.mozilla.org/show_bug.cgi?id=1756170
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At the moment it's "Yaru-dark / Yaru" and the issue remains.
I was using a third party theme when I first encountered this. I
switched back to Yaru before filing this bug, but about:support was
still showing the third party theme. After resetting the theme it's
showing "Yaru-dark / Yaru".
I did
Public bug reported:
After the FF 96 upgrade I can't distinguish focused and unfocused FF
windows from their client side decorations.
Previously the distinction was subtle, but not impossible.
The attached image shows two windows, the one on the left has focus.
The only way you can tell this is
I initially thought this was a snapd issue (hey, snapd stole my zfs
mounts!), but I think those are supposed to be bind mounts.
I also looked at the zfsutils-linux changelog and recent patches but
didn't see anything that seemed suspicious to me.
--
You received this bug notification because
Here are the mountpoints, after I moved them out of
/var/lib/snapd/hostfs.
: kai@cakepile kai; zfs mount -l
square/postgresql /var/lib/postgresql-square
square/docker /var/lib/docker-square
square/avahi-captures /mnt/avahi-captures
square/mn
Public bug reported:
After a reboot, my zfs datasets all mounted under /var/lib/snapd/hostfs,
exclusively.
This is on a 20.04 machine. It has received package updates, but no
reboots for 4.5 months.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: focal
--
You
Public bug reported:
I am currently traveling and have observed the time zone being set
correctly when I connect to a network and then reset to my home time
zone a short while later.
Automatic Time Zone is enabled in settings.
Logs indicate the reset is coming from /usr/libexec/gsd-datetime. I
This issue in evolution-data-server seems to describe the problem.
https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276
** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #276
https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276
--
You
This is still happening after upgrading to 21.10. The calendar reminder
I saw today and last night was canceled several weeks ago. When I looked
in the topbar calendar dropdown, the event did not appear there.
It's unclear to me if this is a gnome-shell issue or a gnome-calendar
issue or maybe
After 20 days with the mainline 5.14.0 kernel, I have not seen a
reoccurrence this behavior.
There was one "WARNING: ... decide_linksettings [amdgpu]" kernel
message, but the inability to bring the display port monitors back up
did not occur.
--
You received this bug notification because you
I have booted and installed the mainline kernel. I don't have a recipe
to reproduce the problem, and sometimes weeks go by between occurrences.
I will follow up here when it happens again or check back in a few weeks
if it does not.
--
You received this bug notification because you are a member
This happened again today. I have discovered that recovery by
suspend/resume is possible.
** Summary changed:
- WARNING: CPU: 11 PID: 3608 at
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529
decide_link_settings+0x1ab/0x1d0 [amdgpu]
+ WARNING: ...
** Attachment added: "journalctl -t kernel -g
'drm.*ERROR|WARNING.*amdgpu|Linux.version|PM: suspend.exit'"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+attachment/5522834/+files/amdgpu-stability-hilites.txt
--
You received this bug notification because you are a member of
Public bug reported:
This has hit me twice in the last 24 hours.
Displays come in and out of power saving, without actually displaying
anything. The console doesn't become usable. It seems to be
unrecoverable, shutdown gets stuck somewhere and I end up having to hit
the reset button.
This is a
This is still happening in 21.04, most recently with a repeating
calendar event instance that was canceled over a week ago. The desktop
has been rebooted in the interim.
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I use google calendar. Events are created and updated via the browser.
The calendar feed is configured through settings/online accounts. I can
see upcoming events in the calendar drop down. The calendar and desktop
are configured for the same timezone, and alerts normally
I've also had this problem with the flameshot icon disappearing after
upgrading to 20.04.
Reverting to gnome-shell-extension-appindicator 33-1 has fixed it for
now, but having broken dependencies isn't good (even if things seem to
be working).
Comments on
I haven't experienced this hang since 2020-01-12 (as far back as my logs
go), so I think the upstream fix probably made it into the 19.10 and
20.04 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am running the 5.4.0-32-generic kernel from focal-proposed, and rtkit-
daemon seems to be working normally now.
: kai@dipper kai; uname -r
5.4.0-32-generic
: kai@dipper kai; journalctl -b0 -u rtkit-daemon
-- Logs begin at Fri 2020-01-03 16:35:36 EST, end at Tue 2020-05-19 11:02:23
EDT. --
May
In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled. It was
only disabled for the lowlatency kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed
Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the
cause of this:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=9b039fc517876d312e7fa0955571101a299c91f5
Some discussion of this WRT lowlatency kernel is here:
The full log is the best I can offer unless I figure out how to
reproduce this (it hasn't even re-occurred randomly). If you skip the
first 50 lines and ignore the libinput errors, it's entirely errors
produced during or immediately after a freeze.
gnome-shell-extension-prefs shows the following
>From top, just now (gnome-shell has not been freezing during this
session):
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
In logs I have going back 6 months the errors "Attempting to run a JS
callback during garbage collection." and "The offending callback was
..." only appear on one other date.
There is a similar message "Attempting to call back into JSAPI during
the sweeping phase of GC." that appears more
** Attachment added: "GnomeShellNormalLog.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367201/+files/GnomeShellNormalLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This happened soon after logging in. The entire desktop (mouse cursor
included) would freeze for maybe 30 seconds at a time. The activities
screen seemed to trigger it. The dock appeared empty.
After a few minutes of this I rebooted and things seem to be alright
now.
At this point it's just these log messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
after upgrade to
In a virtual machine I can reproduce this by installing pulseaudio and
docker.io.
I'm attaching a Vagrantfile that reproduces the issue for me.
:; vagrant up
:; vagrant ssh -t -- journalctl -u rtkit-daemon
** Attachment added: "vagrantfile to reproduce issue"
Public bug reported:
These errors started right after upgrading to 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rtkit 0.12-4
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
I'm unable to resubmit the retraced crash report using the linked
instructions. A message in the journal says "Crash already reported."
I can try submitting a new report if the problem reoccurs.
Below is the content of StacktraceSource. I'm attaching the more
detailed ThreadStacktrace.
#0
Adding StacktraceSource as an attachment since it got folded in my
previous comment.
** Attachment added: "StacktraceSource"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+attachment/5309905/+files/StacktraceSource
--
You received this bug notification because you are a
Sorry, I'm not very familiar with apport or what the ubuntu error
collection system does with crash files.
I've been able to get an actual stack trace using apport-retrace here.
Is that useful if I resubmit with that?
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
This crash happened as I was changing the batteries for my wireless
mouse. Needing to change the batteries in the middle of a session is
routine and has not lead to this failure previously.
There is a crash report, with the following oops id:
Public bug reported:
This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have
logs going back to mid august. The message is repeated for each
calendar at various times.
Nov 06 13:49:13 dipper gnome-calendar[8681]:
source_credentials_required_cb: Failed to authenticate 'Kai Gro
Reported upstream
https://bugs.freedesktop.org/show_bug.cgi?id=112221
** Bug watch added: freedesktop.org Bugzilla #112221
https://bugs.freedesktop.org/show_bug.cgi?id=112221
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am using a Radeon RX 580. This setup was stable with Ubuntu 19.04.
Since upgrading to 19.10 it's failed to resume from S3 sleep 3 times out
of 15. The console will be unresponsive, but the machine is still
accessible over the network.
Here are some of the errors from
** Description changed:
Pulseaudio has started preferring the "HDMI / Displayport" sink instead
of the USB audio device I have speakers connected to. I'm pretty sure
this behavior change coincided with upgrading from Ubuntu 19.04 to
19.10.
I've tried using set-default-sink in
Public bug reported:
Pulseaudio has started preferring the "HDMI / Displayport" sink instead
of the USB audio device I have speakers connected to. I'm pretty sure
this behavior change coincided with upgrading from Ubuntu 19.04 to
19.10.
I've tried using set-default-sink in default.pa, but it
Public bug reported:
I tried to use the gnome magnifier after updating to 19.10 today. After
enabling zoom from the control panel, I could no longer send mouse input
anywhere other than the desktop. This made it impossible to turn zoom
off using the mouse and it doesn't seem to be possible to
I am experiencing this after upgrading to 19.10 and enabling fractional
scaling on wayland. The extra cursor appears at 125%/150% scaling and
disappears at 100% scaling.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been keeping a log of what order I connect and disconnect devices
to this laptop and whether it causes the server to hang.
Disconnecting the video, then the inputs, quickly seems to cause the
server to hang. When I pause before disconnecting the inputs or if I
disconnect the inputs first
Public bug reported:
The logs from this report are from a disconnect, but a similar symptom
occurs when connecting sometimes. I will try to confirm this next time
it happens.
Keyboard hangs, but magic sysrq works.
I'm pretty sure this started when I upgraded to the 12.04 beta.
Possibly the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972852
Title:
X server hangs when connecting or disconnecting external monitor and
input devices
To manage notifications about this bug go to:
Public bug reported:
Background:
These key bindings worked fine in 12.04beta1 from March 2nd until I updated on
March 13th. Before March 2nd I was using gnome-shell, without compiz.
Steps:
1. Run unity --reset --replace
2. In keyboard control panel (or in the CCSM Desktop Wall page), change
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959803
Title:
Desktop switcher does not hide when keybindings are changed from
Ctrl+Alt+Arrow to Meta+[hjkl]
To manage notifications about this bug
Public bug reported:
After updating to 12.04 beta1, mysql service was broken.
I noticed my fan turn on a while after running sudo service mysql status
(never completed).
:; sudo strace -f -p 1
Process 1 attached - interrupt to quit
pipe([1022, 1023]) = 0
open(/dev/ptmx,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947591
Title:
init ran out of file descriptors, spinning while trying to start a
broken service
To manage notifications about this bug go to:
Thanks for the hint, D. Since filing this bug, I have rebooted my
machine and cheese is no longer crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890343
Title:
Cheese crashes on start
Public bug reported:
I'm including a backtrace. I didn't find a -dbg package for cheese
itself, so I don't know if this will be useful.
1) If the problem is reproducible?
Yes
- If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
# Run cheese
:;
** Attachment added: gdb-cheese.txt
https://bugs.launchpad.net/bugs/890343/+attachment/2596764/+files/gdb-cheese.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890343
Title:
Cheese crashes
I have this problem as well. This is with a jabber account configured
to use the server talk.google.com.
--
empathy throws untrusted certificate warning on google chat services using
google apps (non-google domains)
https://bugs.launchpad.net/bugs/640018
You received this bug notification
Public bug reported:
Binary package hint: makedumpfile
Description:Ubuntu 9.10
Release:9.10
makedumpfile:
Installed: 1.3.3-0ubuntu4
Candidate: 1.3.3-0ubuntu4
Version table:
*** 1.3.3-0ubuntu4 0
500 http://us.archive.ubuntu.com karmic/main Packages
100
** Patch added: Update LATEST_VERSION #define in makedumpfile.h
http://launchpadlibrarian.net/39251750/makedumpfile-LATEST_VERSION.patch
--
makedumpfile won't dump 2.6.31 kernels
https://bugs.launchpad.net/bugs/522438
You received this bug notification because you are a member of Ubuntu
55 matches
Mail list logo
