[Bug 1451525] Re: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcur
Reported upstream at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=861974. ** Bug watch added: Debian Bug tracker #861974 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861974 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451525 Title: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-gnutls- dev:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1451525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451525] Re: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcur
libcurl4-openssl-dev:amd64 and libcurl4-openssl-dev:i386 both want to install /usr/bin/curl-config, but the file varies unnecessarily by architecture. mark@mela zsh% shasum -a 256 libcurl4-openssl-dev_7.52.1-4ubuntu1.1_*/data/usr/bin/curl-config 223e5aa695ab4f5ce24b41397ee828f59240c5252075de9e4b4d730fa333bc12 libcurl4-openssl-dev_7.52.1-4ubuntu1.1_amd64/data/usr/bin/curl-config 283beb056326c71097e6d109db85f92e1768c9fc3847bb0541812ff2afda3dba libcurl4-openssl-dev_7.52.1-4ubuntu1.1_i386/data/usr/bin/curl-config They only differ in a small and insignificant part of the string in the line that follows --configure in this script. mark@mela zsh% diff -U1 libcurl4-openssl-dev_7.52.1-4ubuntu1.1_*/data/usr/bin/curl-config --- libcurl4-openssl-dev_7.52.1-4ubuntu1.1_amd64/data/usr/bin/curl-config 2017-04-17 20:20:57.0 + +++ libcurl4-openssl-dev_7.52.1-4ubuntu1.1_i386/data/usr/bin/curl-config 2017-04-17 20:20:57.0 + @@ -157,3 +157,3 @@ --configure) -echo " … 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/curl-5aqeqB/curl-7.52.1=. …'" +echo " … 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/curl-95csPZ/curl-7.52.1=. …'" ;; Those randomly generated directory names, /build/curl-5aqeqB vs. /build /curl-95csPZ, are causing each architecture’s curl-config to differ. They’re also not helping anyone at all being carried all the way through to the shipping /usr/bin/curl-config. This is also https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1565498, https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1513693. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451525 Title: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-gnutls- dev:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1451525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565498] Re: package libcurl4-gnutls-dev (not installed) failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4
This is a duplicate. The bug is explained in https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1451525/comments/3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565498 Title: package libcurl4-gnutls-dev (not installed) failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-gnutls-dev:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1565498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513693] Re: package libcurl4-openssl-dev 7.43.0-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl
This is a duplicate. The bug is explained in https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1451525/comments/3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513693 Title: package libcurl4-openssl-dev 7.43.0-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-openssl- dev:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1513693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876783] Re: Incorrect unknown LVM metadata header errors when running update-grub
*** This bug is a duplicate of bug 452350 *** https://bugs.launchpad.net/bugs/452350 ** This bug has been marked a duplicate of bug 452350 Unknown LVM metadata header -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876783 Title: Incorrect unknown LVM metadata header errors when running update- grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/876783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452350] Re: Unknown LVM metadata header
I don’t believe there’s any bug with GRUB here. In my case, I found “leftover” PV headers on /dev/sda1 and /dev/sdb1 at offset 0x200 (sector 1). I suspect that these were created in a similar way to what Mike Hobbs experienced in https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350 . I saw this with the 11.10 Alternate installer; I didn’t like the what “auto” did but I guess by the time I switched to “manual,” the PV headers had been written. In my current installation, /dev/sda1 and /dev/sdb1 are in a RAID mirror set that shows up at /dev/md0, which is used as an LVM PV. The PV headers at /dev/sda1 and /dev/sdb1 offset 0x200 (grub_lvm_label_header with LABELONE magic) referenced metadata expected at offset 0x1000, but because /dev/sda1 and /dev/sdb1 are RAID members and version 1.2, the RAID superblock (grub_raid_super_1x or linux/raid/md_p.h mdp_superblock_1 with MD_SB_MAGIC magic) was written at that offset. This doesn’t match the LVM MD metadata, which would be grub_lvm_mda_header with GRUB_LVM_FMTT_MAGIC magic. GRUB was correct to issue the “unknown LVM metadata header” error because it did find an LVM label pointing to something other than LVM metadata. The problem was that the LVM label didn’t belong there at all. In my case, I was able to remove the label by brute force (although I wouldn’t recommend doing this) by running dd if=/dev/zero of=/dev/sda1 bs=512 count=2, and repeating for /dev/sdb1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/452350 Title: Unknown LVM metadata header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505452] Re: eeepc_laptop module not loading on kernel 2.6.32
After adding acpi_osi=Linux, you lose notifications for the brightness keys (Fn-F5 and Fn-F6). To get them back, add acpi_backlight=vendor. -- eeepc_laptop module not loading on kernel 2.6.32 https://bugs.launchpad.net/bugs/505452 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 99547] Re: [apport] depmod crashed with SIGSEGV in strcmp()
This bug is not fixed in Jaunty. module-init-tools 3.7 (or 3.7preANYTHING) doesn't contain a complete fix for the problem. depmod module-init-tools 3.7-pre9 still crashes in strcmp with SIGSEGV for me on Januty when I have a broken module present. (The module is a truncated DKMS module, I don't know how it happened and it doesn't really matter either, it's just a good testcase for this bug.) m...@ebony bash$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 9.04 Release:9.04 Codename: jaunty m...@ebony bash$ /sbin/depmod --version module-init-tools 3.7-pre9 m...@ebony bash$ /sbin/depmod Segmentation fault Great. For this demonstration, I pulled the current source from |bzr checkout http://bazaar.launchpad.net/~ubuntu-core-dev/module-init-tools/ubuntu| (which is actually based on 3.8) and confirmed that the bug is present. m...@ebony bash$ gdb depmod GNU gdb 6.8-debian [...] (gdb) run Starting program: .../obj/depmod Program received signal SIGSEGV, Segmentation fault. 0x7f37de8676a0 in strcmp () from /lib/libc.so.6 (gdb) bt #0 0x7f37de8676a0 in strcmp () from /lib/libc.so.6 #1 0x0040a7ec in get_section64 (file=0x7f37de1ab000, fsize=0, secname=0x40d610 __ksymtab_strings, secsize=0x7fffe6d77458, conv=0) at ../src/elf_core.c:35 #2 0x00405bf3 in load_section64 (hdr=0x7f37de1ab000, secname=0x40d610 __ksymtab_strings, secsize=0x7fffe6d77458, conv=0) at ../src/moduleops_core.c:7 #3 0x00405c24 in load_symbols64 (module=0xe31320) at ../src/moduleops_core.c:17 #4 0x00403132 in parse_modules (list=0xe43020) at ../src/depmod.c:675 #5 0x00404b4a in main (argc=1, argv=0x7fffe6d777f8) at ../src/depmod.c:1288 Therefore, this problem would still be present in Karmic as it stands now. The real problem here is that upstream module-init-tools does not do proper bounds checking prior to 3.9. Look at load_section in 3.7/moduleops_core.c. It assumes that the ELF file is as big as it needs to be, which is not a safe assumption. In 3.8/moduleops_core.c, load_section calls to elf_core.c's get_section, which introduces the possibility for bounds checking, but it is bypassed because load_section always passes 0 for |fsize|. Finally, in 3.9/elfops_core.c, load_section passes the entire module struct to get_section, which now always enforces bounds checking to ensure that it doesn't attempt to read unmapped memory beyond the end of the file. m...@ebony bash$ 3.7.obj/depmod -n modules.dep ls -l modules.dep Segmentation fault m...@ebony bash$ 3.8.obj/depmod -n modules.dep ls -l modules.dep Segmentation fault m...@ebony bash$ 3.9.obj/depmod -n modules.dep ls -l modules.dep WARNING: Couldn't find symtab and strtab in module /lib/modules/2.6.28-13-generic/updates/dkms/nvidia.ko -rw-r--r-- 1 mark mark 1822960 2009-07-07 23:18 modules.dep That warning (non-fatal) is far more useful than crashing without producing a modules.dep file. With the broken (3.7 or 3.8) depmod, I was suffering through this on every apt-get invocation: Setting up linux-image-2.6.28-13-generic (2.6.28-13.45) ... Running depmod. Failed to run depmod dpkg: error processing linux-image-2.6.28-13-generic (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.28-13-generic E: Sub-process /usr/bin/dpkg returned an error code (1) This essentially left the system in an indeterminate and potentially unstable state. With a fixed (3.9) depmod, a warning would be produced, but the broken module would not cause any further problems for the rest of the system aside from being unusable itself. I recommend shipping module-init-tools 3.9 with Karmic to alleviate these problems. ** Changed in: module-init-tools (Ubuntu) Status: Fix Released = Incomplete ** Changed in: module-init-tools (Ubuntu) Status: Incomplete = New -- [apport] depmod crashed with SIGSEGV in strcmp() https://bugs.launchpad.net/bugs/99547 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 360870] [NEW] libstdc++.so link in amd64 ia32-libs is wrong
Public bug reported: Binary package hint: ia32-libs This bug is present in Ubuntu 9.04 (Jaunty Jackalope) on amd64 in ia32-libs 2.7ubuntu4 or lib32stdc++6 4.3.3-5ubuntu4. ia32-libs contains a libstdc++.so symbolic link for 32-bit C++ development. The symbolic link points to libstdc++.so.5. A 32-bit libstdc++.so.6 is installed as well, by virtue of ia32-libs' dependency on lib32stdc++6. m...@ebony bash$ ls -l /usr/lib32/libstdc++.so* lrwxrwxrwx 1 root root 14 2009-04-12 20:36 /usr/lib32/libstdc++.so - libstdc++.so.5 lrwxrwxrwx 1 root root 18 2009-04-12 20:36 /usr/lib32/libstdc++.so.5 - libstdc++.so.5.0.7 -rw-r--r-- 1 root root 737192 2008-05-10 02:18 /usr/lib32/libstdc++.so.5.0.7 lrwxrwxrwx 1 root root 19 2009-04-12 20:36 /usr/lib32/libstdc++.so.6 - libstdc++.so.6.0.10 -rw-r--r-- 1 root root 950424 2009-03-16 21:03 /usr/lib32/libstdc++.so.6.0.10 However, the installed C++ headers are from libstdc++6. libstdc++6-4.3-dev is installed. These headers expect to be linked against libstdc++6, and are incompatible with libstdc++5. Simple C++ compilations fail. For example, although it is possible to build the attached test.cc in 64-bit mode, a 32-bit compilation fails: m...@ebony bash$ g++ -m32 test.cc -o test /tmp/cc0c9S5e.o: In function `std::_Rb_tree_const_iteratorstd::pairchar const* const, int ::operator--()': test.cc:(.text._ZNSt23_Rb_tree_const_iteratorISt4pairIKPKciEEmmEv[std::_Rb_tree_const_iteratorstd::pairchar const* const, int ::operator--()]+0xf): undefined reference to `std::_Rb_tree_decrement(std::_Rb_tree_node_base const*)' [...] /tmp/cc0c9S5e.o: In function `std::_Rb_tree_iteratorstd::pairchar const* const, int ::operator++()': test.cc:(.text._ZNSt17_Rb_tree_iteratorISt4pairIKPKciEEppEv[std::_Rb_tree_iteratorstd::pairchar const* const, int ::operator++()]+0xf): undefined reference to `std::_Rb_tree_increment(std::_Rb_tree_node_base*)' collect2: ld returned 1 exit status The libstdc++ headers are expecting these requirements to be satisfied by libstdc++6, but since the /usr/lib32/libstdc++.so symbolic link points to the incompatible libstdc++5, the link results in unresolved symbols. A symbolic link from /usr/lib/gcc/x86_64-linux-gnu/4.3/32/libstdc++.so should be pointed at ../../../../../lib32/libstdc++.so.6. This mimics the symbolic link placed by libstdc++6-4.3-dev in /usr/lib/gcc/x86_64 -linux-gnu/4.3. This symbolic link should be provided by the lib32stdc++6. Placing this symbolic link manually allows the above C++ compilation to succeed without incident. At the same time, the symbolic link at /usr/lib32/libstdc++.so should be removed from ia32-libs. No C++ development should take place using libstdc++5 on this system, whose installed headers expect libstdc++6. ** Affects: ia32-libs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 jaunty -- libstdc++.so link in amd64 ia32-libs is wrong https://bugs.launchpad.net/bugs/360870 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 360870] Re: libstdc++.so link in amd64 ia32-libs is wrong
** Attachment added: test.cc http://launchpadlibrarian.net/25369155/test.cc ** Tags added: amd64 jaunty -- libstdc++.so link in amd64 ia32-libs is wrong https://bugs.launchpad.net/bugs/360870 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
