[Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed f
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 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed f
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.html. I pressed Alt-F2 and then r, and that stopped the logging without a reboot! I'd still like to know why this suddenly keeps happening. 21.04 is due out in a few weeks and I'm hoping that will fix it. -- 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: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed f
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: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`
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 connection to Xorg) after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`
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 Xorg) after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`
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: Mar 17 20:35:29 scruffy gnome-shell[9529]: Object St.Bin (0x5558975eac80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Mar 17 20:35:29 scruffy gnome-shell[9529]: == Stack trace for context 0x555888e95220 == Mar 17 20:35:29 scruffy gnome-shell[9529]: #0 7ffddf081900 I /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1ee0192a1240 @ 208) These 3 lines were being repeated dozens of times a second, and started at the same time I did the upgrade. I didn't know how else to stop them so I rebooted. After rebooting the system seems fine again. -- 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 Xorg) after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`
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/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/1915481 Title: [nvidia] gnome crashes after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`
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.20.10.1), python3-twisted-bin:amd64 (18.9.0-11, 18.9.0-11ubuntu0.20.10.1), wpasupplicant:amd64 (2:2.9-1ubuntu8.1, 2:2.9-1ubuntu8.2) End-Date: 2021-03-03 19:17:23 And here's the latest entry in /var/log/apt/term.log: Log started: 2021-03-03 19:16:46 (Reading database ... 479992 files and directories currently installed.) Preparing to unpack .../python3-twisted-bin_18.9.0-11ubuntu0.20.10.1_amd64.deb ... Unpacking python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) ... Preparing to unpack .../python3-twisted_18.9.0-11ubuntu0.20.10.1_all.deb ... Unpacking python3-twisted (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) ... Preparing to unpack .../wpasupplicant_2%3a2.9-1ubuntu8.2_amd64.deb ... Unpacking wpasupplicant (2:2.9-1ubuntu8.2) over (2:2.9-1ubuntu8.1) ... Setting up python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) ... Setting up wpasupplicant (2:2.9-1ubuntu8.2) ... Setting up python3-twisted (18.9.0-11ubuntu0.20.10.1) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for dbus (1.12.20-1ubuntu1) ... Log ended: 2021-03-03 19:17:23 I'll attach the output of journalctl -b0 > journal.txt Note that the times seem a bit off to me. They seem to say I started the update at 19:16:46, but according to journal.txt I ran `apt update` at 19:15:52. I think I ran `apt upgrade` earlier than 19:16:46 because the first stack trace for gnome-shell is at 19:16:21. One other odd thing is that while I got a new gnome login prompt fairly quickly, it took me about half a dozen login attempts before I could successfully login. I didn't get any errors; rather, the screen would go blank and then I'd get the login prompt again. There was nothing new under /var/crash, nor under https://errors.ubuntu.com/user/ID. -- 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 after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: gnome crashes after running `apt upgrade`
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: gnome crashes after running `apt upgrade`
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 different set of packages than the last time. Also gnome-shell was updated on January 20, and the crashes have continued to happen since then. But the last time I rebooted was after a crash, so I just ran `journalctl -b-1 > prevjournal.txt` and I've attached the results. -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: gnome crashes after running `apt upgrade`
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915481 Title: gnome crashes after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: gnome crashes after running `apt upgrade`
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: https://errors.ubuntu.com/oops/16d604a2-501b-11eb-8b96-fa163e6cac46 Just to be clear, is the workaround from step 3 simply "comment out line 23 from /etc/apport/crashdb.conf and reboot"? There are a lot of other suggestion in that bug report and I wanted to doublecheck that that's all I need to do. As for reproducing the crash, it's probably impossible to exactly reproduce it since it only happens when I'm running `apt upgrade` to install new packages, and these particular new packages have already been upgraded. The best I can do is make the change, reboot, and wait for it to happen again with some new set of packages. -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] Re: gnome crashes after running `apt upgrade`
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.launchpad.net/bugs/1915481 Title: gnome crashes after running `apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915481] [NEW] gnome crashes after running `apt upgrade`
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:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core- launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1875163] Re: rdiff-backup crashes when running backup
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: https://lists.nongnu.org/archive/html/rdiff-backup- users/2020-04/msg00041.html > So a stable release update of rdiff-backup 2.0.5 to Ubuntu 20.04 LTS > (Focal) would close this issue? It seems that way. > Could you try using the 2.0.5 version from https://launchpad.net/~rdiff- > backup/+archive/ubuntu/rdiff-backup-backports and verify if it fixes the > issue? I'll try, but unfortunately I'm dealing with some serious family issues right now that are occupying a lot of my time. It might be a week or two before I can work on it. > > Landing a stable release update in Ubuntu 20.04 requires very good > grounds: https://wiki.ubuntu.com/StableReleaseUpdates > > If 2.0.5 is urgently needed in Ubuntu 20.04, please help us document the > motivations for it here. Totally understandable. Walt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875163 Title: rdiff-backup crashes when running backup To manage notifications about this bug go to: https://bugs.launchpad.net/rdiff-backup/+bug/1875163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875163] Re: rdiff-backup crashes when running backup
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 it never made it into 20.04. Since the files that were causing the errors for me were all in /run, my fix was just to add /run to my list of excluded directories. That was an easy decision for me since I probably should have been excluding them anyway. Good luck! ** Bug watch added: github.com/rdiff-backup/rdiff-backup/issues #310 https://github.com/rdiff-backup/rdiff-backup/issues/310 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875163 Title: rdiff-backup crashes when running backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/1875163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875163] Re: rdiff-backup crashes when running backup
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' ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/1000/keybase/kbfs' ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/141/gvfs' I'm not really sure what's wrong with the first 3. Maybe they're odd because they're in /run? The final file does really look like it might be corrupted. At any rate it looks like the easy fix on my end is to exclude /run from my backups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875163 Title: rdiff-backup crashes when running backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/1875163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875163] Re: rdiff-backup crashes when running backup
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 finishes I'll rerun the backup in the debugger and report back on what I find. Hopefully that will let me set up a simple test case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875163 Title: rdiff-backup crashes when running backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/1875163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875163] [NEW] rdiff-backup crashes when running backup
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 UpdateError: 'home/waltman/.cache/keybase/keybase.service.log' Updated mirror temp file '/backup/scruffy/home/waltman/.cache/keybase/rdiff-backup.tmp.15973' does not match source UpdateError: 'home/waltman/.irssi/db/messages.sqlite' Updated mirror temp file '/backup/scruffy/home/waltman/.irssi/db/rdiff-backup.tmp.56956' does not match source UpdateError: 'run/rpc_pipefs/gssd/clntXX/info' Updated mirror temp file '/backup/scruffy/run/rpc_pipefs/gssd/clntXX/rdiff-backup.tmp.84241' does not match source UpdateError: 'run/snapd/ns/discord.mnt' [Errno 22] Invalid argument UpdateError: 'run/snapd/ns/lxd.mnt' [Errno 22] Invalid argument Exception 'sequence item 0: expected str instance, bytes found' raised of class '': File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 390, in error_check_Main Main(arglist) File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 412, in Main take_action(rps) File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 348, in take_action Backup(rps[0], rps[1]) File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 434, in Backup backup.Mirror_and_increment(rpin, rpout, incdir) File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 55, in Mirror_and_increment DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath) File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 279, in patch_and_increment for diff in rorpiter.FillInIter(source_diffiter, dest_rpath): File "/usr/lib/python3/dist-packages/rdiff_backup/rorpiter.py", line 202, in FillInIter for rp in rpiter: File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 114, in get_diffs for dest_sig in dest_sigiter: File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 196, in get_sigs for src_rorp, dest_rorp in cls.CCPP: File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 361, in __next__ source_rorp, dest_rorp = next(self.iter)
[Bug 1848621] Re: [snap] lost all passwords on 19.10 when chromium-browser deb was replaced by a snap
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 Title: [snap] lost all passwords on 19.10 when chromium-browser deb was replaced by a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848891] [NEW] supertuxkart loses config and progress in 19.04 -> 19.10 update
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 suggested copying 0.8.2/ to config-0.10/. That got me most of the way there, but some things are still not working. In particular the supertux difficulty is locked, and I've lost all my high scores. ** Affects: supertuxkart (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/1848891 Title: supertuxkart loses config and progress in 19.04 -> 19.10 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/supertuxkart/+bug/1848891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727868] [NEW] New windows are unfocused and go below current window
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 Gnome 3, which is new in 17.10. Ubuntu users upgrading from earlier versions should not be assumed to be familiar Gnome 3, nor with how to tweak Gnome settings. The Release Notes should indicate this change and document how to turn it off. Also, and more importantly, there needs to actually be a way to restore the previous behavior. If there is, I've been unable to find it in Settings, gnome-tweak-tool, or dconf-editor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 17:43:57 2017 InstallationDate: Installed on 2016-12-27 (303 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-10-20 (6 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727868 Title: New windows are unfocused and go below current window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726638] [NEW] some programs are missing icons in 17.10
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.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 19:35:45 2017 DistUpgraded: 2017-10-20 10:51:35,135 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.10.0-37-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-12-27 (300 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ssd--vg-root--lv ro SourcePackage: x11-apps UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726638 Title: some programs are missing icons in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1726638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682864] [NEW] fail2ban should remove references to imap3 in 17.04
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 -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl -- stdout: b'' 2017-04-13 21:37:04,274 fail2ban.action [2565]: ERROR iptables -w -N f2b-postfix-sasl iptables -w -A f2b-postfix-sasl -j RETURN iptables -w -I INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl -- stderr: b"iptabl es v1.6.0: invalid port/service `imap3' specified\nTry `iptables -h' or 'iptables --help' for more information.\n" 2017-04-13 21:37:04,278 fail2ban.action [2565]: ERROR iptables -w -N f2b-postfix-sasl iptables -w -A f2b-postfix-sasl -j RETURN iptables -w -I INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl -- returned 2 2017-04-13 21:37:04,279 fail2ban.actions[2565]: ERROR Failed to start jail 'postfix-sasl' action 'iptables-multiport': Err or starting action The fail2ban package should be updated to remove references to the removed protocols. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: fail2ban 0.9.6-1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Apr 14 12:11:57 2017 InstallationDate: Installed on 2016-12-27 (108 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: fail2ban UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) ** Affects: fail2ban (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682864 Title: fail2ban should remove references to imap3 in 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1682864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682696] [NEW] apcupsd installer silently overwrites apcupsd.conf
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 variables. Here are the changes I needed to make to get it working again: % diff apcupsd.conf.bad apcupsd.conf 32c32 < UPSCABLE usb --- > UPSCABLE smart 89c89 < UPSTYPE usb --- > UPSTYPE apcsmart ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apcupsd 3.14.14-0.3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Apr 13 22:20:45 2017 InstallationDate: Installed on 2016-12-27 (107 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: apcupsd UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) modified.conffile..etc.default.apcupsd: # Defaults for apcupsd initscript # Apcupsd-devel internal configuration # APCACCESS=/sbin/apcaccess ISCONFIGURED=yes mtime.conffile..etc.apcupsd.apcupsd.conf: 2017-04-13T22:02:30.799643 mtime.conffile..etc.default.apcupsd: 2017-04-13T21:55:02.693712 ** Affects: apcupsd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682696 Title: apcupsd installer silently overwrites apcupsd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1682696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656856] [NEW] fail2ban looks in wrong log for postfix
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) 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/1656856 Title: fail2ban looks in wrong log for postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511824] Re: Can't login as ordinary user with lightdm
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 find the drivers. See https://ubuntuforums.org/showthread.php?t=2349132 for more information. Of course this doesn't explain why it was looking for pam_kwallet.so, which I suspect is a separate issue. -- 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: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1511824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511824] Re: Can't login as ordinary user with lightdm
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: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1511824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511824] Re: Can't login as ordinary user with lightdm
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/1511824 Title: Can't login as ordinary user with lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1511824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
