[Bug 343220] Re: cc1plus crashed with SIGSEGV
** Visibility changed to: Public -- cc1plus crashed with SIGSEGV https://bugs.launchpad.net/bugs/343220 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 343220] Re: cc1plus crashed with SIGSEGV
Another valuable thing I should mention is that this system has a dmraid-based (i.e. software) RAID0 on two disks and it uses ext4 as filesystem. In fact, the corruption maybe due to something failing in these layers (dmraid/ext4); but as I said GCC shouldn't crash, no matter what garbage you throw at it. -- cc1plus crashed with SIGSEGV https://bugs.launchpad.net/bugs/343220 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 195308] Re: unable to resolve host
I've found the same problem in the Feisty-Hardy upgrade. I fixed it logging as root (using 'su' and not 'sudo'!) in a terminal and then adding the line: 127.0.0.1 ubuntu to /etc/hosts file (in my case the machine name is ubuntu). -- unable to resolve host https://bugs.launchpad.net/bugs/195308 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 130299] Re: please update package coreutils
I'd love to use the new ls --group-directories-first feature! So I vote for the update; please update coreutils to the latest version, thanks. -- please update package coreutils https://bugs.launchpad.net/bugs/130299 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
[Bug 104790] Re: feisty opens a busybox on boot with RAID0+reiserfs
Hi, as I wrote in my comment dated 2007-07-09, since the kernel: Linux ubuntu 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux the problem is gone for me. Now I'm using Linux ubuntu 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux and I still don't have any problem. Should this bug report be closed? Or the fix in the newer kernels was actually a side-effect of unrelated changes? In this case I fear the bug could reappear in future! Putting some comments in the initialization scripts about the danger of a race condition between md-building and root-mounting could be useful to avoid such possibility in future... -- feisty opens a busybox on boot with RAID0+reiserfs https://bugs.launchpad.net/bugs/104790 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
[Bug 133765] Re: gutsy md module not present in ramdisk
Hi, sorry for the delay - I forgot to say that since one month or so, I managed to boot my Gutsy without using the Feisty kernel ramdisk, just updgrading to linux kernel 2.6.22-13-386. I think the problem of the md module is gone in that release as I now boot without problems... please let me know if I can be of any help, e.g. providing debug-related info. -- gutsy md module not present in ramdisk https://bugs.launchpad.net/bugs/133765 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
[Bug 109262] Re: [fixed in 4.2] linker error with -fvisibility-inlines-hidden
I confirm this too (just hit this bug). It has been reported however that the same GCC version (4.1.2) compiled from vanilla sources does work correctly with that snippet of code. -- [fixed in 4.2] linker error with -fvisibility-inlines-hidden https://bugs.launchpad.net/bugs/109262 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
[Bug 104790] Re: feisty opens a busybox on boot with RAID0+reiserfs
I forgot to say that using the latest kernel: Linux ubuntu 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux the problem is gone! I had however to uninstall also the uswsusp package because it seems it was giving problems to the boot, too. -- feisty opens a busybox on boot with RAID0+reiserfs https://bugs.launchpad.net/bugs/104790 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
[Bug 104790] feisty opens a busybox on boot with RAID0+reiserfs
Public bug reported: My layout of hard disks is: hda6 = BOOT partition of my (K)Ubuntu sda1 = partition of the RAID0 device /dev/md0 which uses REISERFS (v 3.6) sdb1 = partition of the RAID0 device /dev/md0 which uses REISERFS (v 3.6) I've done Edgy-Feisty upgrade (using update-manager) but at the restart, after GRUB, I'm being dropped in a BusyBox. Very nice thing is the fact that it does not see the keyboad and thus I cannot type anything (I press keys but nothing happens on the screen). I think this is somehow related to the fact my keyboard (and mouse) are USB... maybe the busybox is launched _before_ loading the USB driver? I suspect that's the source of the problem because e.g. the numpad LED does not turn on when I press Block-num, which typically happens when keyboard is not turned on by the kernel. Things get much better if I put a break=mount in the GRUB options for kernel command as the busybox which comes up then is interactive (i.e. when a press a keyboard key it's responsive and show it on the screen). I've found that from the busybox I'm dropped after GRUB, my MD device is already assembled and working. In fact, I've discovered that I don't need to do _anything_ from that busybox. I.e. if I just press Ctrl+D, busybox exits and the boot proceed correctly. However if I remove the break=mount option from the GRUB kernel command, I still get an unresponsive busybox (and I'm forced to turn off the computer unplugging the cable: the turn-off button nor the reset button do anything!). ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- feisty opens a busybox on boot with RAID0+reiserfs https://bugs.launchpad.net/bugs/104790 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
[Bug 104790] Re: feisty opens a busybox on boot with RAID0+reiserfs
** Attachment added: dmesg dmesg.log http://librarian.launchpad.net/7222814/dmseg.log -- feisty opens a busybox on boot with RAID0+reiserfs https://bugs.launchpad.net/bugs/104790 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
[Bug 37030] Re: compatibility beetween dri and radeon
Since the time of Dapper I always had a similar problem like those reported by Michele Campeotto: name of display: :0.0 libGL: XF86DRIGetClientDriverName: 4.0.3 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_get_dispatch) libGL error: unable to find driver: r300_dri.so libGL: XF86DRIGetClientDriverName: 4.0.3 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_get_dispatch) libGL error: unable to find driver: r300_dri.so display: :0 screen: 0 Today I've upgraded to Feisty and found DRI was still not working, so I decided to investigate this and finally found this bug entry. I've now fixed it removing the xorg-driver-fglrx package. That's great!! However I think it would be _very_ important to at mark xorg-driver- fglrx as conflicting with xserver-xorg-video-ati and/or to update the descriptions of these two packages mentioning that having installed both means DRI won't work. Thanks! -- compatibility beetween dri and radeon https://bugs.launchpad.net/bugs/37030 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 57923] Re: Opening firefox by clicking on links in thunderbird breaks https
I have this same problem but mine seems to be even worse: I can't manage to open *any* https link in FF even if it's already started and if I copypaste the URL from another app. (and I get that screen with the Check to make sure your system has the Personal Security Manager installed etc etc). I can workaround this only using Mozilla Web Browser. I'm using FF package 1.99+2.0b2+dfsg-1ubuntu2 -- Opening firefox by clicking on links in thunderbird breaks https https://launchpad.net/bugs/57923 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48029] Re: Can't load r200_dri in libGL (ATI Radeon R250 Lf [FireGL 9000])
Same problem here. _glapi_get_dispatch is undefined symbol in /usr/lib/dri/r200_dri.so and thus DRI is disabled with my ATI Radeon 9100. On Dapper I fixed this problem compiling and installing my own libGL: quoting from http://dri.freedesktop.org/wiki/DriTroubleshooting : If the driver complains about unresolved symbols then your libGL is out of sync with your DRI drivers. Because APIs change, you typically need a libGL from the latest X.Org release to run DRI drivers, and sometimes you need a libGL from X.Org CVS for the latest drivers. Reinstall both your drivers and your libGL from sources from the same date. since I remember it was a pain, I'd really like to have DRI work out of the box on Edgy - please fix this ASAP !! Thanks! -- Can't load r200_dri in libGL (ATI Radeon R250 Lf [FireGL 9000]) https://launchpad.net/bugs/48029 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57923] Re: Opening firefox by clicking on links in thunderbird breaks https
If I open the browser from the panel or menu then all https links work. if I try to do the same and open Firefox from the menu or panel and then type e.g. https://sourceforge.net; I get that same error screen. -- Opening firefox by clicking on links in thunderbird breaks https https://launchpad.net/bugs/57923 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61040] chrome://browser/content/browser.xul entity error
Public bug reported: Binary package hint: firefox I'm using latest EDGY EFT packages. Since I have updated to the 1.99+2.0b2+dfsg-1ubuntu1 version of firefox package, I can't start firefox as it tells me: Errore interpretazione XML: entità non definita Indirizzo: chrome://browser/content/browser.xul Linea numero 1140, colonna 9: toolbarbutton id=go-button ^ menuitem id=menu_HelpPopup_reportPhishingtoolmenu ^ I tried to reinstall the package but that didn't help. ** Affects: firefox (Ubuntu) Importance: Untriaged Status: Unconfirmed -- chrome://browser/content/browser.xul entity error https://launchpad.net/bugs/61040 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
