[Bug 529714] Re: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
I get the same issue without wins in nsswitch.conf at all - but stranger results yet depending on whether or not an iPhone is currently connected to the computer. With an iPhone connected, I get an invalid pointer crash with backtrace ending in libusb, then libc shortly thereafter. (log attached) Without the iPhone, it just says Segmentation fault. Boom! ** Attachment added: rhythmbox_invalid_free http://launchpadlibrarian.net/48849680/rhythmbox_invalid_free -- rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r() https://bugs.launchpad.net/bugs/529714 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 529714] Re: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
As always, if any more information is helpful, let me know; it's been ages since I followed up on a bug report ... -- rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r() https://bugs.launchpad.net/bugs/529714 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 529714] Re: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
I get the same issue without wins in nsswitch.conf at all - but stranger results yet depending on whether or not an iPhone is currently connected to the computer. With an iPhone connected, I get an invalid pointer crash with backtrace ending in libusb, then libc shortly thereafter. (log attached) Without the iPhone, it just says Segmentation fault. Boom! ** Attachment added: rhythmbox_invalid_free http://launchpadlibrarian.net/48849680/rhythmbox_invalid_free -- rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r() https://bugs.launchpad.net/bugs/529714 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 529714] Re: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
As always, if any more information is helpful, let me know; it's been ages since I followed up on a bug report ... -- rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r() https://bugs.launchpad.net/bugs/529714 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 62244] Re: Debugging mode not enabled in Bochs.
I'm going to go ahead and take away the opinion I had of this some three and a half years ago now - honestly, the GDB stub is in all likelihood much more useful than whatever Bochs come up with themselves. chilicuil; is there some overriding reason you can't use gdb to debug it instead? As William says (said), they're mutually incompatible, so I guess Debian made the decision to let bochs users use gdb to debug instead. -- Debugging mode not enabled in Bochs. https://bugs.launchpad.net/bugs/62244 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 216696] Re: failing to detect available resolutions, cannot use proper ones (regressed)
I think your problem (translaterx_german) is quite different to mine. Please file a new bug. I'm closing this one. Somehow it went away. get-edid now works. xrandr returns the list of resolutions successfully, on the correct device: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1200 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 59.9 1440x900 75.0 59.9 1280x960 59.9 1360x765 59.8 1152x864 74.8 1280x720 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48075.0 72.8 66.7 60.0 720x40070.1 S-video disconnected (normal left inverted right x axis y axis) -- failing to detect available resolutions, cannot use proper ones (regressed) https://bugs.launchpad.net/bugs/216696 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 216696] Re: failing to detect available resolutions, cannot use proper ones (regressed)
Symptom of bug mysteriously disappeared - the machine had been rebooted 10~20 times without change, but after the power went off while it was on, on the next boot things were fine. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New = Invalid -- failing to detect available resolutions, cannot use proper ones (regressed) https://bugs.launchpad.net/bugs/216696 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
No problems with 1:2.22.1-0ubuntu3. Thanks a lot, guys! -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Perfect! Well, almost. No screens appear - I believe this is because I also *happen* to be suffering from (proposed) bug 216696 - i.e. X detects no monitors as being available. I'm hoping it's not a complicating factor. Either way, given these packages gnome-display-properties no longer crashes, and appears to work fine (given the situation). Thank you! :) -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Of course, my apologies. Arlen ** Attachment added: valgrind.log http://launchpadlibrarian.net/13421489/valgrind.log -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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
Re: [Bug 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Hi, On Mon, Apr 14, 2008 at 10:29 PM, James Westby [EMAIL PROTECTED][EMAIL PROTECTED] wrote: If you could test the packages, and then confirm here that they work that would be fantastic. If the problem re-appears could you please re-open the bug (set the status back to New) so that it is clear to everyone that it needs work. No problems! I'll look out for it then. Cheers, Arlen ** Attachment added: unnamed http://launchpadlibrarian.net/13421674/unnamed -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 204872] Re: gnome-display-properties crashed with SIGSEGV in rw_screen_list_outputs()
Hi. Where/how can we get this latest version, 1:2.22.1-0ubuntu5? The pool appears to have only 2.22.1-0ubuntu2 as far as I can see, but it may be that I don't know where to look. This problem's just run into me as I recently upgraded my hardy install. I'm using ATI, however! Any ideas? Arlen -- gnome-display-properties crashed with SIGSEGV in rw_screen_list_outputs() https://bugs.launchpad.net/bugs/204872 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 216676] [NEW] gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Public bug reported: Binary package hint: gnome-control-center I recently upgraded to the latest hardy - beforehand all was working well; using `radeon' kernel module for my ATI card. Post-upgrade, the screen resolution changed to 1280x768 (from 1680x1024 or thereabouts - widescreen monitor). So, I went to gnome-display-properties.. but it segfaulted. At first, I imagined this to be quite similar to https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/204872, but I am using the latest as was suggested to be the fix (1:2.22.1-0ubuntu5 is the version I'm running). Also, I'm using an ATI card as opposed to NVidia. compiz was enabled when I started out; disabling does not fix. gnome-control-center 1:2.22.1-0ubuntu2 libgnome-desktop-2 1:2.22.1-0ubuntu5 Anything else? This seems to be quite a problem. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sun Apr 13 07:58:37 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gnome-display-properties Package: gnome-control-center 1:2.22.1-0ubuntu2 PackageArchitecture: i386 ProcCmdline: gnome-display-properties ProcCwd: /home/celtic ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 Signal: 11 SourcePackage: gnome-control-center Stacktrace: #0 0xb7f06229 in rw_mode_get_width () from /usr/lib/libgnome-desktop-2.so.2 #1 0x0804d62b in _start () StacktraceTop: rw_mode_get_width () from /usr/lib/libgnome-desktop-2.so.2 _start () ThreadStacktrace: . Thread 1 (process 6771): #0 0xb7f06229 in rw_mode_get_width () from /usr/lib/libgnome-desktop-2.so.2 #1 0x0804d62b in _start () Title: gnome-display-properties crashed with SIGSEGV in rw_mode_get_width() Uname: Linux 2.6.24-16-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/13405162/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/13405163/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/13405164/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/13405165/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/13405166/Registers.txt -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216696] [NEW] failing to detect available resolutions, cannot use proper ones (regressed)
Public bug reported: Binary package hint: xserver-xorg-video-ati Hi there, This appears to be a regression in the latest hardy. All was working well, I upgraded (~400 packages). My monitor's maximal resolution is 1680x1050, which I used. Post-upgrade, it's now at 1280x768. Due to an unrelated[?] problem, I can't even open gnome-display-properties to change it, but querying xrandr gives this: Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1280 x 1200 VGA-0 disconnected 1280x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm DVI-0 disconnected (normal left inverted right x axis y axis) S-video disconnected (normal left inverted right x axis y axis) 1280x768 (0x50) 80.1MHz h: width 1280 start 1344 end 1480 total 1680 skew0 clock 47.7KHz v: height 768 start 769 end 772 total 795 clock 60.0Hz The monitor is attached by DVI. xrandr says otherwise, which is curious. 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) Attaching X logs. It appears confused about the (non-)presence of the output devices. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- failing to detect available resolutions, cannot use proper ones (regressed) https://bugs.launchpad.net/bugs/216696 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 216696] Re: failing to detect available resolutions, cannot use proper ones (regressed)
** Attachment added: X logs http://launchpadlibrarian.net/13405791/Xorg.0.log -- failing to detect available resolutions, cannot use proper ones (regressed) https://bugs.launchpad.net/bugs/216696 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 216696] Re: failing to detect available resolutions, cannot use proper ones (regressed)
Attaching `sudo get-edid`. It fails, in the end. ** Attachment added: output from `sudo get-edid` http://launchpadlibrarian.net/13405799/edid-output -- failing to detect available resolutions, cannot use proper ones (regressed) https://bugs.launchpad.net/bugs/216696 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Here's X's log. ** Attachment added: X logs http://launchpadlibrarian.net/13406441/Xorg.0.log -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
X config. I will look into getting a proper stacktrace for you. ** Attachment added: xorg.conf http://launchpadlibrarian.net/13406450/xorg.conf -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
(gdb) run Starting program: /usr/bin/gnome-display-properties [Thread debugging using libthread_db enabled] [New Thread 0xb6ca2720 (LWP 10742)] CRTC 4a Timestamp: 7278908 CRTC 4b Timestamp: 7278908 Output 4c Timestamp: 7278908 Output 4d Timestamp: 7278908 Output 4e Timestamp: 7278908 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6ca2720 (LWP 10742)] rw_mode_get_width (mode=0x3) at randrwrap.c:1104 1104randrwrap.c: No such file or directory. in randrwrap.c (gdb) bt #0 rw_mode_get_width (mode=0x3) at randrwrap.c:1104 #1 0x0804d62b in rebuild_gui (app=0x807a0f0) at xrandr-capplet.c:525 #2 0x0804f1ae in run_application (app=0x807a0f0) at xrandr-capplet.c:1755 #3 0x0804f83c in main (argc=1, argv=0xbfbd3184) at xrandr-capplet.c:1799 (gdb) -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
No problems. Here's the extra back trace info. I'll run it with valgrind next. (gdb) thread apply all bt full Thread 1 (Thread 0xb6d5f720 (LWP 11066)): #0 rw_mode_get_width (mode=0x3) at randrwrap.c:1104 __PRETTY_FUNCTION__ = rw_mode_get_width #1 0x0804d62b in rebuild_gui (app=0x807a0f0) at xrandr-capplet.c:525 sensitive = 0 __PRETTY_FUNCTION__ = rebuild_gui #2 0x0804f1ae in run_application (app=0x807a0f0) at xrandr-capplet.c:1755 xml = value optimized out align = (GtkWidget *) 0x8077078 major = 1 minor = 2 event_base = 115 error_base = 186 display = value optimized out xdisplay = value optimized out __PRETTY_FUNCTION__ = run_application #3 0x0804f83c in main (argc=1, argv=0xbfc68a14) at xrandr-capplet.c:1799 No locals. (gdb) -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 216676] Re: gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width()
Valgrind log attached! Looks painful. ** Attachment added: valgrind.log http://launchpadlibrarian.net/13406992/valgrind.log -- gnome-display-properties crashed on opening with SIGSEGV in rw_mode_get_width() https://bugs.launchpad.net/bugs/216676 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 125302] Re: kvm-ifup fails to bring up tap0 in feisty
I had a similar problem (Gutsy/AMD64, 2.6.22-14-generic, kvm 1:16-1ubuntu2), in that tap0 wasn't visible (ifconfig -a) on my host, and kvm reported can't add tap0 to bridge eth1: Operation not supported when starting. However, after my host finished booting and everything network related had finished initializing, tap0 had appeared, and I can configure them both to communicate without issue. -- kvm-ifup fails to bring up tap0 in feisty https://bugs.launchpad.net/bugs/125302 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
