[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Actually zfs-2.0.2-1ubuntu5, zfs-kmod-2.0.3-8ubuntu5. I'm not sure who to create corruption, but I have plenty of it causing processes to kernel panic. https://github.com/openzfs/zfs/issues/11474 contains some instructions on how to create a corrupted file using wine. Even after this fixed zfs hits, those of us with scrambled file systems are going to need help in clearing out the mess :( So please don't close this bug until there is a mitigation process as well as a fix to zfs to stop it happening further. Does using an encrypted pool have any impact on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Does the fact that this is an encrypted pool have any impact on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Downgrading these libraries did not fix it for me. One canary is to look at the state of the updatedb.mlocate process which goes into live hang as it hits the file that is currently faulty. Thus for example: 2728 ?DNs0:01 /usr/bin/updatedb.mlocate Using lsof one can find out which is the faulty file but, if you try to ls the directory with the file in, then you terminal live hangs. And if you try to delete the directory containing the faulty file, then that silently fails, leaving the directory and the live hang should you try to read it. It's said that this bug relates to 1906476 and via that to https://github.com/openzfs/zfs/issues/11474 but I think I have that one fixed with zfs_recover=1. But the syslog message is very similar: Aug 11 10:13:45 silmh9 kernel: [ 242.531205] INFO: task updatedb.mlocat:2728 blocked for more than 120 seconds. Aug 11 10:13:45 silmh9 kernel: [ 242.531211] Tainted: P U O 5.13.0-13-generic #13-Ubuntu Aug 11 10:13:45 silmh9 kernel: [ 242.531212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 11 10:13:45 silmh9 kernel: [ 242.531213] task:updatedb.mlocat state:D stack:0 pid: 2728 ppid: 1 flags:0x4220 Aug 11 10:13:45 silmh9 kernel: [ 242.531216] Call Trace: Aug 11 10:13:45 silmh9 kernel: [ 242.531221] __schedule+0x268/0x680 Aug 11 10:13:45 silmh9 kernel: [ 242.531225] ? arch_local_irq_enable+0xb/0xd Aug 11 10:13:45 silmh9 kernel: [ 242.531228] schedule+0x4f/0xc0 Aug 11 10:13:45 silmh9 kernel: [ 242.531231] spl_panic+0xfa/0xfc [spl] Aug 11 10:13:45 silmh9 kernel: [ 242.531238] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531287] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531313] ? __raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531339] ? dmu_buf_replace_user+0x65/0x80 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531367] ? dmu_buf_set_user+0x13/0x20 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531393] ? dmu_buf_set_user_ie+0x15/0x20 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531420] zfs_znode_sa_init+0xd9/0xe0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531479] zfs_znode_alloc+0x101/0x560 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531536] ? dmu_buf_unlock_parent+0x5d/0x90 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531564] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531590] ? dbuf_read_impl.constprop.0+0x316/0x3e0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531616] ? __cond_resched+0x1a/0x50 Aug 11 10:13:45 silmh9 kernel: [ 242.531618] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531620] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531642] ? __cond_resched+0x1a/0x50 Aug 11 10:13:45 silmh9 kernel: [ 242.531644] ? down_read+0x13/0x90 Aug 11 10:13:45 silmh9 kernel: [ 242.531645] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531646] ? queued_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531680] ? do_raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531712] ? __raw_callee_save___native_queued_spin_unlock+0x15/0x23 Aug 11 10:13:45 silmh9 kernel: [ 242.531713] ? dmu_object_info_from_dnode+0x8e/0xa0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531742] zfs_zget+0x237/0x280 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531796] zfs_dirent_lock+0x42a/0x570 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531850] zfs_dirlook+0x91/0x2a0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531902] zfs_lookup+0x1fb/0x3f0 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.531954] zpl_lookup+0xcb/0x230 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.532007] __lookup_slow+0x84/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532009] walk_component+0x141/0x1b0 Aug 11 10:13:45 silmh9 kernel: [ 242.532010] ? dput+0x5c/0x180 Aug 11 10:13:45 silmh9 kernel: [ 242.532012] path_lookupat+0x6e/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532013] filename_lookup+0xbb/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532015] ? __check_object_size.part.0+0x128/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532017] ? __check_object_size+0x1c/0x20 Aug 11 10:13:45 silmh9 kernel: [ 242.532018] ? strncpy_from_user+0x44/0x150 Aug 11 10:13:45 silmh9 kernel: [ 242.532020] ? __raw_spin_unlock+0x9/0x10 [zfs] Aug 11 10:13:45 silmh9 kernel: [ 242.532066] user_path_at_empty+0x59/0x90 Aug 11 10:13:45 silmh9 kernel: [ 242.532068] vfs_statx+0x7a/0x120 Aug 11 10:13:45 silmh9 kernel: [ 242.532070] __do_sys_newlstat+0x3e/0x70 Aug 11 10:13:45 silmh9 kernel: [ 242.532072] ? __secure_computing+0x42/0xe0 Aug 11 10:13:45 silmh9 kernel: [ 242.532073] ? syscall_trace_enter.constprop.0+0xa0/0x1c0 Aug 11 10:13:45 silmh9 kernel: [ 242.532075] __x64_sys_newlstat+0x16/0x20 Aug 11 10:13:45 silmh9 kernel: [ 242.532076] do_syscall_64+0x61/0xb
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Actually zfs-2.0.2-1ubuntu5, zfs-kmod-2.0.3-8ubuntu5. I'm not sure who to create corruption, but I have plenty of it causing processes to kernel panic. https://github.com/openzfs/zfs/issues/11474 contains some instructions on how to create a corrupted file using wine. Even after this fixed zfs hits, those of us with scrambled file systems are going to need help in clearing out the mess :( So please don't close this bug until there is a mitigation process as well as a fix to zfs to stop it happening further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
Is there a way to clear the corruption without having to do a fresh install? This bug is crippling me on hirsuite, kernel 5.13.0-12. zfs-2.0.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888797] Re: missing luahbtex
Norbert, ping. It sounds you were so close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1888797] Re: missing luahbtex
Daer Norbert, > > Thank you Norbert. That would be great. I think your running the PPA > > would be a far better solution. > > Fine with me! I could help the Ubuntu people also for their versions, > but I don't **run** for them. If they would ask ... Sure. > Hmmm, the page I linked > > https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#versioning > has *rather clear* version number explanations. They expect some > ppa > string to be contained. My guess would have been > 2020.20200327.54578-4ppa1~ubuntu20.04 > or so ... But you want the ppa version to always precede the Debian version so: 2020.20200327.54578-4~ppa1-ubuntu20.04 ? Yours, Martin > > WDYT? > > Best > > Norbert > > -- > PREINING Norbert https://www.preining.info > Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888797 > > Title: > missing luahbtex > > Status in texlive-base package in Ubuntu: > New > > Bug description: > I'm trying to install luahbtex. texlive-luatex implies it includes the > corresponding luahbtex CTAN package, but the only filename containing > the characters hb, installed by texlive-luatex is man1/luahbtex.1.gz > which makes no reference to luahbtex within it. > > Yours, wanting to use luahbtex, please. > TIA > PS I tried to report this against texlive-luatex but ubuntu-bug wouldn't > let me. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: texlive-luatex 2019.20200218-1 > ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 > Uname: Linux 5.4.0-40-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Fri Jul 24 13:49:10 2020 > InstallationDate: Installed on 2018-04-23 (822 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180421.1) > PackageArchitecture: all > SourcePackage: texlive-base > UpgradeStatus: Upgraded to focal on 2020-05-13 (71 days ago) > modified.conffile..etc.default.apport: [modified] > mtime.conffile..etc.default.apport: 2020-04-26T13:30:20.884695 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888797] Re: missing luahbtex
I do notice I and fighting with /usr/local/lib leakage into my build. Thank you Norbert. That would be great. I think your running the PPA would be a far better solution. The current (2019) version is 2019.20190605.51237-3build2 in the main repo So might I suggest 2020.20200327.54578-4~ubuntu20.04 ? This follows a convention followed by a number of ppas of having the ubuntu version in the version number. But you can put any suffix you like there. There are no strong rules about it for a ppa. HTH, Yours, Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888797] Re: missing luahbtex
Thanks. Yes, it would be great if texlive 2020 was in Ubuntu 20.04. But I doubt it will happen given the feature packages for 20.04 are fixed now. I downloaded texlive-bin 2020 and tried to debuild. But I have harfbuzz 2.6.4 and there seems to be some mismatch in xetex over whether harfbuzz-icu is needed or not. The packaging files imply that all reference to harfbuzz-icu was removed in 2019, but there is code in texk/web2c/xetexdir/XeTeXLayoutInterface.cpp that if harfbuzz is greater than 2.5, then it should use harfbuzz-icu. I wonder if you can help me out of my confusion. If I get this to build well, I may be up for putting up a PPA for it. TIA, Yours, Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888797] [NEW] missing luahbtex
Public bug reported: I'm trying to install luahbtex. texlive-luatex implies it includes the corresponding luahbtex CTAN package, but the only filename containing the characters hb, installed by texlive-luatex is man1/luahbtex.1.gz which makes no reference to luahbtex within it. Yours, wanting to use luahbtex, please. TIA PS I tried to report this against texlive-luatex but ubuntu-bug wouldn't let me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-luatex 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 24 13:49:10 2020 InstallationDate: Installed on 2018-04-23 (822 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-05-13 (71 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-04-26T13:30:20.884695 ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1888797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771631] [NEW] missing build dependency stops fancy plugin from building
Public bug reported: As released to 18.10, claws-mail 3.16 fails to include the fancy plugin (or is that claws-mail-extras, it's all the same source package). 3.16 has fixed the fancy rendering problem. All that needs to happen is that it be built for ubuntu. The required build dependency is libwebkitgtk- dev and probably libwebkitgtk-1.0-0 to go with it. Now we can have html rendering back :) ** Affects: claws-mail (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/1771631 Title: missing build dependency stops fancy plugin from building To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1771631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603845] Re: kernel 4.4.0-31 install broken
Still a problem in 4.4.0-34 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603845 Title: kernel 4.4.0-31 install broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1603845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()
When I ran the test, I got not failure. But I did notice that when I ran the test using valgrind (still with no failure) valgrind reported a number of memory problems in python3.4. No errors were reported from anywhere in gtk or lower (pango, graphite, etc.). The command I used to test was: valgrind --log-file=ubiquity.log ubiquity --greeter Maybe a fixed python has fixed this bug? Please retest with newer python3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303516 Title: ubiquity crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/harfbuzz/+bug/1303516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()
In addition. If this is a memory corruption bug, is running the test under valgrind of any use? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303516 Title: ubiquity crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/harfbuzz/+bug/1303516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()
A couple of initial queries: Is there any way we can find out what the font was that was being initialised when the crash occurred? I ask because if the font isn't a graphite font, then what was causing a graphite font to try to be created? Looking at the input text being Burmese, I'll assume it's font linked Padauk. The ppm value of 15024 being passed here in the source stack trace is suspicious (even if divided by 64 it's still 234pt which is a bg font). Not that such a big value alone would cause the crash. But has some corruption occurred earlier? #4 0x7f3d808922d2 in gr_make_font_with_ops (ppm=15024, appFontHandle=0x67d0d10, font_ops=font_ops@entry=0x7fff72772f50, face=0x2512f20) at /build/buildd/graphite2-1.2.4/src/gr_font.cpp:52 In the main stack trace, the size value here looks suitably crazy but that could be due to some wandering in the long tall grass (although *how* anyone can get malloc to crash quite so impressively is an interesting question in its own right): #0 _int_malloc (av=0x7f3d8aa5c760 , bytes=1824) at malloc.c:3489 iters = nb = 1840 idx = 76 bin = victim = 0x67ec860 size = 39582418614272 Is this implying a post free memory access to mess up the free list? Are there any other reasons that malloc could go crazy like this? I assume a modern malloc doesn't do anything nice like use the last element on the free list for the next malloc? So the corruption and following usage could be far apart? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303516 Title: ubiquity crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/harfbuzz/+bug/1303516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279660] Re: luks+lvm+btrfs raid1 confuses linux
In keeping with a similar bug #890779, I am assuming this is a udisks/udev issue. But the encryption aspect and the inability for it to take down the lvm to release the encryption may be from somewhere else. ** Package changed: ubuntu => udisks (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279660 Title: luks+lvm+btrfs raid1 confuses linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1279660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890779] Re: btrfs mounts in raid1 are shown twice
still present in saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890779 Title: btrfs mounts in raid1 are shown twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/890779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279660] [NEW] luks+lvm+btrfs raid1 confuses linux
Public bug reported: I created a luks encrypted partition on an external drive, and put lvm with a single group and two volumes into the partition. I then used mkfs.btrfs to create a raid1 (-d raid1 -m raid1) mirror of the two lvm volume devices. After rebooting (yes, it's that bad) and plugging in the external drive again, two drives appear on the list of available drives, even though they are a raid pair. If you click on one then it mounts OK. If you click the other or click to mount again the mounter will mount the device again in another directory of /media. If I then unmount those manually I can't stop the drive using disks or lock the encrypted partition (this probably being the cause of the other). If I give up and unplug, then the two block devices for the lvm volumes remains and I can't replug later without a reboot. I raise this bug since I can imagine that down the line, this could become a common use case if btrfs isn't going to support direct encryption for those wanting self healing, encrypted, compressed, browsable backups. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: btrfs luks lvm mount -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279660 Title: luks+lvm+btrfs raid1 confuses linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1279660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166125] Re: Broken fonts for Gtk based applications
pango-graphite and its dependent libgraphite3 should be removed from any dependencies and from the repos. The replacement (libgraphite2-3, yeh I know it's a funny order) integrates with harfbuzz-ng. I'm assuming that pango uses harfbuzz rather than its own shaping modules now? I don't know the procedure to withdraw a package from the repos from a particular release but I would suggest withdrawing pango-graphite and libgraphite3 from raring, saucy and subsequent releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166125 Title: Broken fonts for Gtk based applications To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1166125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364657] [NEW] trang fails to run properly
Public bug reported: Binary package hint: trang trang seems to be built wrongly: On jaunty. When run I get this error: trang lift.rng lift.xsd Exception in thread "main" java.lang.NullPointerException at org.relaxng.datatype.helpers.DatatypeLibraryLoader$Service$Loader2.getResources(libgcj_bc.so.1) at org.relaxng.datatype.helpers.DatatypeLibraryLoader$Service.(libgcj_bc.so.1) at org.relaxng.datatype.helpers.DatatypeLibraryLoader.(libgcj_bc.so.1) at com.thaiopensource.relaxng.input.parse.ParseInputFormat.load(trang) at com.thaiopensource.relaxng.translate.Driver.doMain(trang) at com.thaiopensource.relaxng.translate.Driver.main(trang) and when I pdebuild the source package I get the warning: dpkg-shlibdeps: warning: /usr/lib/libgcj_bc.so.1 has an unexpected SONAME (libgcj.so.90) (among other warnings) ** Affects: trang (Ubuntu) Importance: Undecided Status: New -- trang fails to run properly https://bugs.launchpad.net/bugs/364657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185470] Re: iwl3945 not functioning : microcode error
kernel 2.6.24-16, dell d620, iwl3945 v 1.2.0, dmesg output as given above with microcode failure. Installed linux-backports- modules-2.6.24-16-generic from main binary repositorty and dmesg reports iwl3945 v 1.2.5. Still with the same microcode error. The md5sums for the microcode are no different from previous versions. dmesg output from modprobe included. ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/13505207/dmesg.log -- iwl3945 not functioning : microcode error https://bugs.launchpad.net/bugs/185470 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188866] [NEW] pdebuild with --debbuildopts fails
Public bug reported: running pdebuild without --debbuildopts results in an empty DEBBUILDOPTS and so pbuilder is run with an empty --debuildopts parameter and trys to take the following .dsc file resulting in there being no required .dsc reference on the pbuilder command line. ProblemType: Bug Architecture: i386 Date: Mon Feb 4 15:54:55 2008 DistroRelease: Ubuntu 7.10 NonfreeKernelModules: vmnet vmmon Uname: Linux sil-mh4 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug -- pdebuild with --debbuildopts fails https://bugs.launchpad.net/bugs/188866 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
