[Bug 633101] Re: Duplicity is failing with an assertion error when looking for a non-existent manifest file

2012-05-09 Thread Peter Meier
I'm having the same problem from time to time: Local and Remote metadata are synchronized, no sync needed. Traceback (most recent call last): File "/usr/bin/duplicity", line 1377, in ? with_tempdir(main) File "/usr/bin/duplicity", line 1370, in with_tempdir fn() File "/usr/bin/duplic

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-09 Thread Peter Meier
Imho this is upstream Bug# 42723 -> https://bugzilla.kernel.org/show_bug.cgi?id=42723 I went back to 11.04 with 3.0.0-19-generic which works fine and without any problems for nearly a week now. ** Bug watch added: Linux Kernel Bug Tracker #42723 http://bugzilla.kernel.org/show_bug.cgi?id=42723

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-02 Thread Peter Meier
Unfortunately it also happened with the upstream kernel: [14081.450885] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:741: group 904, 32254 clusters in bitmap, 32258 in gd [14081.450895] Aborting journal on device dm-1-8. [14081.451151] EXT4-fs (dm-1): Remounting filesystem read-only [14081

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-01 Thread Peter Meier
I'm now running a 3.4 kernel. Will report back if there are problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about th

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-01 Thread Peter Meier
** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/992424/+attachment/3122163/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-01 Thread Peter Meier
$ cat /proc/version_signature Ubuntu 3.2.0-24.37-generic 3.2.14 $ uname -a Linux foo 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://

[Bug 992424] Re: ext4 filesystem errors on SSD disk

2012-05-01 Thread Peter Meier
** Attachment added: "lspci-vnn" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/992424/+attachment/3122164/+files/lspci-vnn.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Titl

[Bug 992424] [NEW] ext4 filesystem errors on SSD disk

2012-05-01 Thread Peter Meier
Public bug reported: After Upgrading from 11.10 to 12.04 I quickly got EXT4 Filesystem errors on my root-fs, which will result in / being remounted as readonly. How to reproduce: 1. Boot 12.04 with latest 12.04 kernel (3.2.0.24.26) 2. Start some io-heavy (probably write-intensive) task, like syn

[Bug 218887] Re: pidgin-libnotify don't work anymore

2008-05-14 Thread Peter Meier
I can confirm this bug. What I found out so far is that: Sometimes I can enable the plugin when trying to enable it several times. It will then be enabled for the rest of the started session. However if I close pidgin and start it again the plugin is again disabled. Earlier I had to restart the

[Bug 157269] Re: Can't call method "mail" on an undefined value at /usr/lib/subversion/hook-scripts/commit-email.pl line 605.

2007-12-21 Thread Peter Meier
I can confirm this issue. Anybody have already fixed it? -- Can't call method "mail" on an undefined value at /usr/lib/subversion/hook-scripts/commit-email.pl line 605. https://bugs.launchpad.net/bugs/157269 You received this bug notification because you are a member of Ubuntu Bugs, which is the

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG