I've been running 21.10 since it was released and I haven't had the
problem on it. I honestly don't recall if I still had the issue on
21.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Titl
I'm running Ubuntu 20.10.
But I think I can answer my own question. It just happened again, and
this time all I needed to run was run `apt update`. I didn't even
install anything! A quick google search found this page:
https://www.linuxuprising.com/2020/07/how-to-restart-gnome-shell-from-
command.
This has happened to me twice in the last two days. Until the fix is
available, is there any way to recover from it aside from rebooting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
To be clear, comment #13 appears to be a duplicate of the bug report in
comment #14.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
[nvidia] gnome crashes with Fatal IO errors (lost co
This appears to be a duplicate of
https://bugs.launchpad.net/bugs/1905519
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
[nvidia] gnome crashes with Fatal IO errors (lost connection to
Something different happened tonight, but it feels related so I'm going
to post it with this bug report.
Tonight I did an apt upgrade for a single package -- containerd. Gnome
didn't crash this time, but a short time later I noticed that
/var/log/syslog was filling up with the following messages:
This is the output of journalctl -b0 > journal.txt after a recent crash
of gnome-shell after I ran `sudo apt upgrade`. The problems start at
roughly Mar 03 19:15:58.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5472270/+files
I just had gnome crash on me again while running `sudo apt upgrade`.
Only 3 packages were updated. Here's the latest entry in
/var/log/apt/history.log:
Start-Date: 2021-03-03 19:16:46
Commandline: apt upgrade
Requested-By: waltman (1000)
Upgrade: python3-twisted:amd64 (18.9.0-11, 18.9.0-11ubuntu0
I believe the crash happened at roughly Feb 11 19:42:41.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
gnome crashes after running `apt upgrade`
To manage notifications about this bu
Reproducing the crash exactly is basically impossible -- I have no idea
what I was doing to trigger it on January 6. The crashes I've been
experiencing happen seemingly at random while running `apt update`. It
may well happen again in the future, but based on past experiences it
will be with a diff
Out from running
journalctl -b-1 > prevjournal.txt
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5463784/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Thanks for replying so quickly. Unfortunately step 1 didn't show any
crash reports.
Step 2 doesn't show anything recent, but there were crashes on January 6
that might be relevant. They are:
gnome-control-center:
https://errors.ubuntu.com/oops/28c05820-501b-11eb-9503-fa163e983629
gnome-shell: ht
On second thought, a better title would be "gnome crashes WHILE running
apt upgrade" because it always happens while it's in the middle of
installing the new packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
This is the second time this week this has happened, and perhaps the
tenth time in the past few months. This time the packages it was
updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
libsqlite3-0:amd6
Hi Otto,
On Fri, Sep 11, 2020 at 06:14:08AM -, Otto Kekäläinen wrote:
> The commit that fixed this was in rdiff-backup version 2.0.5, right?
> https://github.com/rdiff-backup/rdiff-backup/commit/1c6b9bcf388bbbef522dd1a752e747a51c6ce004
Hmm, it could be. This is what I based "it was fixed" on:
My apologies. I resolved this locally back in April but I forgot to come
back here and update the ticket when I resolved the problem. This is a
known bug that has been fixed in the rdiff-backup repo:
https://github.com/rdiff-backup/rdiff-backup/issues/310
The code was fixed way back in March, but
I modified get_indexpath() in log.py to catch a TypeError exception and
return the string "TypeError" instead of aborting. It printed 4 errors:
ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/1000/doc'
ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/1000/gvfs'
Lis
I'm afraid I don't know nearly enough Docker to be able to do that. But
I do know Python. I just took a look at the code and I think I should be
able to trap the TypeError exception pretty easily.
I'm currently running `rdiff-backup --check-destination-dir` to undo the
failed backup. Once that fin
Public bug reported:
Here's the output from last night's cronjob:
Subject: Cron if [ -x /backup/scruffy ]; then rdiff-backup
--print-statistics --exclude-filelist /usr/local/etc/rdiff_exclude /
/backup/scruffy; fi
I also had this problem. After running the command suggested above:
snap connect chromium:password-manager-service
it's now working again 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/1848621
Public bug reported:
In 19.04 supertuxkart stores its configuration in
~/.config/supertuxkart/0.8.2/. In 19.10 it's stored in config-0.10/. The
old configuration doesn't seem to be used at all when starting the game
for the first time.
I asked on the #supertuxkart channel on freenode. They sugges
Public bug reported:
When new applications are launched from the terminal in 17.10, the
windows are unfocused and appear below the current window. This is the
opposite of the behavior in (at least) 16.10 and 17.04, where new
windows would appear focused and on top. This appears to be a feature in
Public bug reported:
Several programs in this package, notably xload and xcalc, don't have
icons in the new dock in 17.10. Most of the others (e.g. xclock, xeyes)
do.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: x11-apps 7.7+6ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13
Public bug reported:
Ubuntu 17.04 ships with netbase 5.4, which removes a number of protocols
from /etc/services. One of these is imap3 (220/tcp) which is used by
several entries in /etc/fail2ban/jail.conf. This led to the following
messages in /var/log/fail2ban.log:
iptables -w -I INPUT -p tcp -
Public bug reported:
I upgraded to 17.04 tonight, and when the install finished I started
getting reports that apcupsd could no longer communicate with my UPS.
The problem turned out to be that /etc/apcupsd/apcupsd.conf was silently
overwritten by the installer. It changed the UPSCABLE and UPSTYPE
Public bug reported:
The postfix jails in fail2ban look in the mail.warn log. But the default
install of rsyslog has the mail.warn rule commented out, so nothing gets
logged there. Also I think the messages it's looking for go to mail.log,
not mail.warn.
** Affects: fail2ban (Ubuntu)
Importa
I figured out what my problem was, and since I haven't seen any
solutions anywhere else, hopefully this will be of some use to the next
person. In my case it turned out to be the Nvidia driver, which
installed its modules under /lib/modules/4.8.0-32-generic. When I
upgraded to 4.8.0-34, it couldn't
Sorry, that should be 4.8.0-34 and 4.8.0-32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511824
Title:
Can't login as ordinary user with lightdm
To manage notifications about this bug go to:
htt
I'm seeing the same thing in 16.10, with kernel 4.0.8-34 that just hit
yesterday. When I boot from the previous kernel (4.0.8-32) I can still
login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/151182
29 matches
Mail list logo
