[Bug 1762683] Re: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0)
Also gcc-6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762683 Title: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1762683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762683] Re: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0)
Please change the state back to 'Incomplete', since I don't have the privileges to do so -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762683 Title: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1762683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762683] Re: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0)
I'm still seeing this problem for both 7.4.0-1ubuntu1~18.04.1 and 8.3.0-6ubuntu1~18.04.1. I've confirmed with the reproduction case posted on the GCC bug as well: phil@machine:~/python_module$ g++ --version g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. phil@machine:~/python_module$ bash run.sh without sanitizers Throwing an exception Caught an exception Hello *** with sanitizers Throwing an exception ==11969==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0) #0 0x7faf2d20fc02 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe9c02) #1 0x7faf2d22e595 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x108595) #2 0x7faf2d15e26c in __interceptor___cxa_throw (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x3826c) #3 0x7faf28e631f5 in greet(_object*, _object*) (/home/phil/python_module/greet.so+0x11f5) #4 0x503090 (/usr/bin/python3.6+0x503090) #5 0x506858 in _PyEval_EvalFrameDefault (/usr/bin/python3.6+0x506858) #6 0x502208 (/usr/bin/python3.6+0x502208) #7 0x502f3c (/usr/bin/python3.6+0x502f3c) #8 0x506858 in _PyEval_EvalFrameDefault (/usr/bin/python3.6+0x506858) #9 0x504c27 (/usr/bin/python3.6+0x504c27) #10 0x506392 in PyEval_EvalCode (/usr/bin/python3.6+0x506392) #11 0x634d51 (/usr/bin/python3.6+0x634d51) #12 0x634e09 in PyRun_FileExFlags (/usr/bin/python3.6+0x634e09) #13 0x6385c7 in PyRun_SimpleFileExFlags (/usr/bin/python3.6+0x6385c7) #14 0x639159 in Py_Main (/usr/bin/python3.6+0x639159) #15 0x4a6f0f in main (/usr/bin/python3.6+0x4a6f0f) #16 0x7faf2cd56b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #17 0x5afa09 in _start (/usr/bin/python3.6+0x5afa09) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762683 Title: AddressSanitizer CHECK failed: ../../../sanitizer/asan/asan_interceptors.cc:384 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1762683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088448] Re: Unknown directive SystemGroup
The message for SystemGroup (and any other affected parameters) should be modified to refer explicitly to USN-1654-1 and to cups-files.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088448 Title: Unknown directive SystemGroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1088448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988008] Re: [precise] screen locks up with mouse cursor moving
** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988008 Title: [precise] screen locks up with mouse cursor moving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/988008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576648] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.)
Is there any technical barrier to uploading the patched version of nvidia-current in Lucid updates or backports? I could really benefit from having working Nvidia drivers on the 3.0 kernel, as I run a large lab full of workstations used by researchers, whose work is easier on the newer kernel. I'd be glad to help with any testing needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576648 Title: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/576648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576648] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.)
As another workaround that seems to suffice (no serious stability testing, yet), and allows use of the newer kernels, one can pull packages from the x-updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576648 Title: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/576648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192877] Re: pdftex for some reason scans the whole home directory
This is still biting me on Lucid, with texlive 2009-7, based on a long recursive dump of these stat calls from strace: stat($HOME/.texmf-config/web2c/pdftex, 0xdeadbeef) = -1 ENOENT (No such file or directory) Once I fixed the home directory entry in LDAP to not have a trailing /, it was fine, but that indicates that the upstream bug wasn't fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/192877 Title: pdftex for some reason scans the whole home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/192877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955371] [NEW] Build deps don't reflect failure of simple backport on Lucid's openssl
Public bug reported: When I try to build on Lucid, I get the following compiler errors: CC openconnect-dtls.o dtls.c: In function ‘dtls_try_handshake’: dtls.c:310: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ dtls.c:311: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ dtls.c:312: error: ‘struct dtls1_state_st’ has no member named ‘timeout_duration’ dtls.c:314: error: ‘BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT’ undeclared (first use in this function) dtls.c:314: error: (Each undeclared identifier is reported only once dtls.c:314: error: for each function it appears in.) dtls.c:315: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ The corresponding source is as follows: /* Debian restricts visibility of dtls1_stop_timer() so do it manually. Thankfully this *should* work, from 0.9.8m to 1.0.0d inclusive, and we don't have to worry about future changes because we don't do this for 1.0.0e and above anyway */ memset ((vpninfo-dtls_ssl-d1-next_timeout), 0, sizeof((vpninfo-dtls_ssl-d1-next_timeout))); vpninfo-dtls_ssl-d1-timeout_duration = 1; BIO_ctrl(SSL_get_rbio(vpninfo-dtls_ssl), BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT, 0, (vpninfo-dtls_ssl-d1-next_timeout)); This seems to indicate that building should require OpenSSL 0.9.8m or greater, while the build dependencies only ask for libssl-dev (= 0.9.8g-14). ** Affects: openconnect (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/955371 Title: Build deps don't reflect failure of simple backport on Lucid's openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/955371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl
** Description changed: When I try to build on Lucid, I get the following compiler errors: - CC openconnect-dtls.o + CC openconnect-dtls.o dtls.c: In function ‘dtls_try_handshake’: dtls.c:310: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ dtls.c:311: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ dtls.c:312: error: ‘struct dtls1_state_st’ has no member named ‘timeout_duration’ dtls.c:314: error: ‘BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT’ undeclared (first use in this function) dtls.c:314: error: (Each undeclared identifier is reported only once dtls.c:314: error: for each function it appears in.) dtls.c:315: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ The corresponding source is as follows: - /* Debian restricts visibility of dtls1_stop_timer() - so do it manually. Thankfully this *should* work, - from 0.9.8m to 1.0.0d inclusive, and we don't have - to worry about future changes because we don't do - this for 1.0.0e and above anyway */ - memset ((vpninfo-dtls_ssl-d1-next_timeout), 0, - sizeof((vpninfo-dtls_ssl-d1-next_timeout))); - vpninfo-dtls_ssl-d1-timeout_duration = 1; - BIO_ctrl(SSL_get_rbio(vpninfo-dtls_ssl), -BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT, 0, -(vpninfo-dtls_ssl-d1-next_timeout)); + /* Debian restricts visibility of dtls1_stop_timer() + so do it manually. Thankfully this *should* work, + from 0.9.8m to 1.0.0d inclusive, and we don't have + to worry about future changes because we don't do + this for 1.0.0e and above anyway */ + memset ((vpninfo-dtls_ssl-d1-next_timeout), 0, + sizeof((vpninfo-dtls_ssl-d1-next_timeout))); + vpninfo-dtls_ssl-d1-timeout_duration = 1; + BIO_ctrl(SSL_get_rbio(vpninfo-dtls_ssl), + BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT, 0, + (vpninfo-dtls_ssl-d1-next_timeout)); This seems to indicate that building should require OpenSSL 0.9.8m or greater, while the build dependencies only ask for libssl-dev (= 0.9.8g-14). + + The corresponding commit message in + 269a2e16a2686b0d416e4b78f6ecd4b44b6b3e1e says the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955371 Title: Build deps don't reflect failure of simple backport on Lucid's openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/955371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769866] Re: tab completion no longer escapes filenames and completes dirnames incorrectly (space instead of slash)
Here's a patch to move Adobe Reader's _filedir() function to a different name, so that it doesn't interfere with the one provided in /etc/bash_completion. ** Patch added: acroread_tab.patch https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/769866/+attachment/2660422/+files/acroread_tab.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769866 Title: tab completion no longer escapes filenames and completes dirnames incorrectly (space instead of slash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/769866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507089] Re: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch
I just reproduced the segfault at startup as an LDAP user with thunderbird version 3.1.7+build3+nobinonly-0ubuntu0.10.04.1 from lucid- update/lucid-security. I can confirm that installing and starting nscd lets Thunderbird start, and purging it restores the segfault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/507089 Title: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571308] Re: Thunderbird crashes with segmentation fault
*** This bug is a duplicate of bug 507089 *** https://bugs.launchpad.net/bugs/507089 Looks like a dupe of #507089 ** This bug has been marked a duplicate of bug 507089 thunderbird shredder always segfaults on startup with LDAP auth in nsswitch * You can subscribe to bug 507089 by following this link: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/507089/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571308 Title: Thunderbird crashes with segmentation fault -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689480] Re: package dependencies broken or missing
I'm seeing this exact issue on Lucid amd64. This is an LTS release, and a rather useful library. Any chance we'll see this corrected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689480 Title: package dependencies broken or missing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659205] Re: [fglrx] fails to detect correct resolution with non-multiple of 64 virtual desktop area
I'm seeing similar behavior on a desktop with a Radeon HD 4870. However, the 'multiples of 64' bit seems to be a red herring. I have a pair of 1920x1080 displays, and when I set Virtual 3840 1080, the maximum detected resolutions are 1440x900 and 1400x1050. If I set Virtual 3840 1088 (multiple of 64), I get the same result. If I set Virtual 3840 3840, both displays offer the intended 1920x1080 mode. In the failure case, I see these lines in /var/log/Xorg.0.log: (II) fglrx(0): Not using mode 1920x1080 (width too large for virtual size) (II) fglrx(0): Not using mode 1776x1000 (width too large for virtual size) (II) fglrx(0): Not using mode 1680x1050 (width too large for virtual size) Is it possible the driver wants a virtual area big enough to contain the modes in any orientation and arrangement? I'll go see what happens if I set Virtual 3840 1920. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659205 Title: [fglrx] fails to detect correct resolution with non-multiple of 64 virtual desktop area -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 39249] Re: (Dapper, Hardy) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied
I just noticed this on a Hardy server installation while investigating a network outage. It's apparently unrelated, since this bug has been appearing at least a week (according to syslog), while problems only cropped up today. I have dhcp3-client version 3.0.6.dfsg-1ubuntu9.1 installed. Syslog entries: Mar 14 13:12:13 style dhclient: DHCPREQUEST of null address on eth0 to 128.174.252.4 port 67 Mar 14 13:12:13 style dhclient: DHCPACK of 128.174.236.247 from 128.174.252.4 Mar 14 13:12:13 style dhclient: can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied Mar 14 13:12:13 style dhclient: bound to 128.174.236.247 -- renewal in 42886 seconds. $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp $ cat /etc/dhcp3/dhclient.conf request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, host-name, ntp-servers; $ ls -ld /var/lib/dhcp3/ drwxr-xr-x 2 root root 4096 2009-10-05 18:18 /var/lib/dhcp3/ $ ls -l /var/lib/dhcp3/ total 0 -rw-r--r-- 1 root root 0 2009-10-05 18:18 dhclient.leases I'm not going to try to reproduce this, because this is a production system and attempts might be disruptive to users. I'm happy to provide more information on request. -- (Dapper, Hardy) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied https://bugs.launchpad.net/bugs/39249 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 39249] Re: (Dapper, Hardy) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied
I just noticed this on a Hardy server installation while investigating a network outage. It's apparently unrelated, since this bug has been appearing at least a week (according to syslog), while problems only cropped up today. I have dhcp3-client version 3.0.6.dfsg-1ubuntu9.1 installed. Syslog entries: Mar 14 13:12:13 style dhclient: DHCPREQUEST of null address on eth0 to 128.174.252.4 port 67 Mar 14 13:12:13 style dhclient: DHCPACK of 128.174.236.247 from 128.174.252.4 Mar 14 13:12:13 style dhclient: can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied Mar 14 13:12:13 style dhclient: bound to 128.174.236.247 -- renewal in 42886 seconds. $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp $ cat /etc/dhcp3/dhclient.conf request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, host-name, ntp-servers; $ ls -ld /var/lib/dhcp3/ drwxr-xr-x 2 root root 4096 2009-10-05 18:18 /var/lib/dhcp3/ $ ls -l /var/lib/dhcp3/ total 0 -rw-r--r-- 1 root root 0 2009-10-05 18:18 dhclient.leases I'm not going to try to reproduce this, because this is a production system and attempts might be disruptive to users. I'm happy to provide more information on request. -- (Dapper, Hardy) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied https://bugs.launchpad.net/bugs/39249 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401126] Re: Realtek RTL8192SE WLAN Card Fails to work on Medion Akoya E1312 Netbook
@david woo: What is the license on the driver packages you've been linking? I couldn't find an over-arching one in the tarball itself. It would be nice if other people were able to package this and perhaps arrange it as a DKMS module, so that kernel upgrades don't break wireless. -- Realtek RTL8192SE WLAN Card Fails to work on Medion Akoya E1312 Netbook https://bugs.launchpad.net/bugs/401126 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 401126] Re: Realtek RTL8192SE WLAN Card Fails to work on Medion Akoya E1312 Netbook
Also, could you post the 64-bit version of the latest driver? Does it just need the skb-tail patch, or is there something more? -- Realtek RTL8192SE WLAN Card Fails to work on Medion Akoya E1312 Netbook https://bugs.launchpad.net/bugs/401126 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 477169] Re: Wubi/Karmic boot: kernel panic - not synching: VFS
Day by day Grubs is getting me more and more doubtful... I added: loopback loop1 = /ubuntu/disks/boot.disk and edited: root (loop0) - root (loop1) the last two lines where without /boot: linux /vmlinuz-2.6.31-14-generic root=/dev/sda5 loop=/ubuntu/disks/root.disk ro single initrd /initrd.img-2.6.31-14-generic And I get rid only of: insmod ntfs That gives me an 'error: not found' (or something similar). IT WORKS. But if I try to run kernel 2.6.31-15 with the same procedure: boots normally, but then I get stuck on tty1 console login with the text on the screen flashing!! Mah... -- Wubi/Karmic boot: kernel panic - not synching: VFS https://bugs.launchpad.net/bugs/477169 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 477169] Re: Wubi/Karmic boot: kernel panic - not synching: VFS
Hi Mark! Thanks for your help. I've done all you said in #84, but when doing grub-install hd0 I get: grub-probe: error: Cannot find a GRUB drive for /dev/loop1. Check your device.map. My device.map in /boot/grub contains only: (hd0) /dev/sda. What may be wrong? -- Wubi/Karmic boot: kernel panic - not synching: VFS https://bugs.launchpad.net/bugs/477169 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 477169] Re: Wubi/Karmic boot: kernel panic - not synching: VFS
UPDATES:
1) I succeeded in updating Grub with grub-install.
** Useful info for Mark **
I solved the error above substituting target=${host_mountpoint}/wubildr with
the full path to wubildr.
Consider that I installed wubi in a partition different from the first
partition, therefore my wubildr isn't in /host/. I don't know why the script
didnt' found it anyway.
2) I've the same error of #85.
Whatever kernel option I choose I get: Error: You need to load the kernel
first.
So I press 'e', get rid of all that bunch of lines except the last two:
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda5
loop=/ubuntu/disks/root.disk ro single
initrd /boot/initrd.img-2.6.31-14-generic
Try. Don't work, 'cause it seems /boot folder is empty.
So I've to substitute /boot with /boot_old (that was a copy of the old /boot
folder that I made before creating boot.disk, ecc...)
And all seems to work.
My question now is: how can I tell grub to load boot.disk into /boot
before loading kernel with these two commands?
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
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 40367] Re: ggcov: Incorrect library version dependency
And, 6 months later, it has still not been rebuilt and uploaded to intrepid-updates. To be clear, I just installed ggcov today and got the same error: ggcov: error while loading shared libraries: libbfd-2.18.50.20080610.so: cannot open shared object file: No such file or directory -- ggcov: Incorrect library version dependency https://bugs.launchpad.net/bugs/40367 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40367] Re: ggcov: Incorrect library version dependency
And I can confirm that a simple package rebuild on my Intrepid system eliminates this error. This should be a quick point for some MOTU to rack up. -- ggcov: Incorrect library version dependency https://bugs.launchpad.net/bugs/40367 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441802] [NEW] Hardy server network configuration should mention 'auto' twice
Public bug reported: Binary package hint: ubuntu-docs I'm running a server (alas, not installed as such) on 8.04.3. I just needed to change its network configuration from DHCP to a static address. I found this page, and tried to follow it: https://help.ubuntu.com/8.04/serverguide/C/network-configuration.html I should have known better after so many years, but I both forgot, and didn't read, that I needed to add the appropriate 'auto ethX' line to go with my static configuration. The box of configuration text auto eth0 iface eth0 inet dhcp looks, at first glance, like it only applied to DHCP configurations. The `auto eth0` line should be duplicated at the top of the next box, as well, to make it clear that it applies to static configurations as well. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New -- Hardy server network configuration should mention 'auto' twice https://bugs.launchpad.net/bugs/441802 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 441798] [NEW] Hardy server network configuration leads to resolvconf warnings
Public bug reported: I'm running a server (alas, not installed as such) on 8.04.3. I just needed to change its network configuration from DHCP to a static address. I found this page, and tried to follow it: https://help.ubuntu.com/8.04/serverguide/C/network-configuration.html Following the instructions on this page, and writing out /etc/resolv.conf explicitly, I found that I was getting ugly warnings on startup from resolvconf. The instructions should instead tell the user to edit /etc/resolvconf/resolv.conf.d/base, at least when it's present. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Description changed: - Binary package hint: ubuntu-docs + I'm running a server (alas, not installed as such) on 8.04.3. https://help.ubuntu.com/8.04/serverguide/C/network-configuration.html Following the instructions on this page, and writing out /etc/resolv.conf explicitly, I found that I was getting ugly warnings on startup from resolvconf. The instructions should instead tell the user to edit /etc/resolvconf/resolv.conf.d/base, at least when it's present. ** Description changed: - I'm running a server (alas, not installed as such) on 8.04.3. + I'm running a server (alas, not installed as such) on 8.04.3. I just + needed to change its network configuration from DHCP to a static + address. I found this page, and tried to follow it: https://help.ubuntu.com/8.04/serverguide/C/network-configuration.html Following the instructions on this page, and writing out /etc/resolv.conf explicitly, I found that I was getting ugly warnings on startup from resolvconf. The instructions should instead tell the user to edit /etc/resolvconf/resolv.conf.d/base, at least when it's present. -- Hardy server network configuration leads to resolvconf warnings https://bugs.launchpad.net/bugs/441798 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 209049] Re: Spelling Mistake in 50unattended-upgrades
This same typo is repeated in /usr/share/doc/unattended-upgrades/README That file also references gutsy, at least on my Hardy system. It should probably be updated to refer to the current release, or some measure taken to make this not problematic in the future. -- Spelling Mistake in 50unattended-upgrades https://bugs.launchpad.net/bugs/209049 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 86685] Re: trac BROKEN on AMD64: neo_cgi.so: undefined symbol: Py_InitModule4
I can confirm Chucky's statement that this bug is present in 8.04 x86_64, up to date as of today. My version of trac is 0.10.4-2. I was able to resolve it by installing python-clearsilver version 0.10.4-1.3 from Debian sid: http://http.us.debian.org/debian/pool/main/c/clearsilver/python-clearsilver_0.10.4-1.3_amd64.deb -- trac BROKEN on AMD64: neo_cgi.so: undefined symbol: Py_InitModule4 https://bugs.launchpad.net/bugs/86685 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 258466] Re: Unable to configure Administration menu
That's not a usable workaround - menus should be completely configurable on a per-user basis. It's particularly bad for users who legitimately don't have administrative privileges, and so want to make all that crap they can't use not appear in their menus. -- Unable to configure Administration menu https://bugs.launchpad.net/bugs/258466 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 258466] Re: Unable to configure Administration menu
I'm seeing this same problem in part in 8.10, and saw it in 8.04. I'm running on x86, with alacarte version 0.11.6-0ubuntu2. I have full sudo privs here (I'm the only user), but I'm not prompted at any point. Here's what doesn't work: - In the Applications menu, I cannot enable items (submenus) that are not already enabled. I've tried to enable both Debian and Programming, and they untick themselves after a few seconds or further interaction. They never go from the small-italic font to the larger upright font of active items. Everything else seems to operate just fine, though my memory is that it was worse before I upgraded from 8.04. If there's been no action on this front in another week or two, I'll have convenient access to an 8.04 machine on which to test further, to help track down what this comes from. -- Unable to configure Administration menu https://bugs.launchpad.net/bugs/258466 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
