[Bug 305080] [NEW] [regression from tetex] missing fonts/packages in texlive
Public bug reported: Binary package hint: texlive-full I tried to compile latex documents using the templates used in bioinformatics (http://www.oxfordjournals.org/our_journals/bioinformatics/for_authors/submission_online.html) and failed to do so in hardy and intrepid. Even the test document provided with the template fails, due to missing .tfm files (for ly1 fonts) I have plenty of messages like this one: ! Font LY1/phv/bx/it/8=hvbo at 8.0pt not loadable: Metric (TFM) file not found. furthermore the mathtime.sty file is not distributed. All of this used to work out of the box in older version (before the texlive switch). I just checked in a fresh dapper install in virtualbox, adding kile and a few tetex packages was enough to get it working. In intrepid, removing the "LY1" options and mathtime package inclusion (lines 31 and 32 of bioinfo.cls) allows the test document to compile, but wouldn't it be much better to get it working out of the box again ? ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New -- [regression from tetex] missing fonts/packages in texlive https://bugs.launchpad.net/bugs/305080 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 290193] [NEW] unreliable WPA connection with network-manager 0.7
Public bug reported: Binary package hint: network-manager I have weird problems with network-manager 0.7. As I have the same problem on intrepid and hardy (using PPA packages for NM 0.7), I don't think it can be a kernel problem (it works fine on hardy with NM 0.6 and the same hardware/kernel). Upon connection, it sometimes connects nicely and sometimes fails, prompting several times (can be more than 10) for the password (observed on hardy with one WPA network). Once connected I have many connection loss (one every few minutes), some of them are resumes correctly and some trigger the password prompt again (observed mostly on intrepid on another WPA network but on the same hardware). Note that I have only acces to WPA networks, so I don't know if it is specific to WPA or not. This is on a dell laptop with an intel wireless card: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) I attached an extract on this morning log, I had several connection loss within 20 minutes. I rebooted to an install of hardy (using NM 0.6) on the same hardware and didn't see any loss since (more than one hour ago). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- unreliable WPA connection with network-manager 0.7 https://bugs.launchpad.net/bugs/290193 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 290193] Re: unreliable WPA connection with network-manager 0.7
** Attachment added: "log extract" http://launchpadlibrarian.net/18961135/daemon.log -- unreliable WPA connection with network-manager 0.7 https://bugs.launchpad.net/bugs/290193 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 290193] Re: unreliable WPA connection with network-manager 0.7
*** This bug is a duplicate of bug 263963 *** https://bugs.launchpad.net/bugs/263963 Indeed, it looks similar, but I'm not sure it is "only" a kernel bug: on hardy, using the SAME kernel, the problem is only present if I use network-manager 0.7 -- unreliable WPA connection with network-manager 0.7 https://bugs.launchpad.net/bugs/290193 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 198929] Re: Selection of screen section for recording turns screen black
I can confirm this.
When using compiz, the area selector works fine but the recording is messed up
(and compiz is not yet working/stable/glitch free for everyone).
as a (quick and dirty) workaround, I forced byzanz to set a root window
when selecting an area in src/byzanzselect.c by breaking the test on
line 195. It now looks like:
if (0 && rgba) {
gtk_widget_set_colormap (data->window, rgba);
} else {
GdkWindow *root = gdk_get_default_root_window ();
gint width, height;
gdk_drawable_get_size (root, &width, &height);
data->root = gdk_drawable_get_image (root, 0, 0, width, height);
}
It is not a proper solution but it allows to use it in the meantime.
--
Selection of screen section for recording turns screen black
https://bugs.launchpad.net/bugs/198929
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 409673] Re: latest poppler prevents pdftex/pdflatex from working correctly
I can confirm this as well (on a 32bit install). It affects pdfcrop as well, also included in texlive. I grabbed poppler 0.11.1 from http://poppler.freedesktop.org/ and compiled it using the debian directory of the 0.11.2 package. Beside a problem with a missing html documentation, the build went fine but the problem is still here. Doing the same with 0.11.0 fixed the problem for me as well. Just like pdftex, pdfcrop works again with 0.11.0 (but not with 0.11.1). -- latest poppler prevents pdftex/pdflatex from working correctly https://bugs.launchpad.net/bugs/409673 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 410305] [NEW] screen flickering on dell laptop
Public bug reported: Binary package hint: xserver-xorg-video-intel it seems similar to bug #399829 which appears at each frequency but 85Hz. In this case, none of the listed frequency fixes the problem. ProblemType: Bug Architecture: i386 Date: Fri Aug 7 16:17:37 2009 DistroRelease: Ubuntu 9.10 MachineType: Dell Inc. Latitude D520 Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic root=UUID=e6da9118-b864-4516-bef3-6da89fc48868 ro quiet splash ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.5-1ubuntu1 libdrm2 2.4.12-1ubuntu1 xserver-xorg-video-intel 2:2.8.0-0ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu5 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.31-5-generic i686 dmi.bios.date: 04/02/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0NF743 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/02/2007:svnDellInc.:pnLatitudeD520:pvr:rvnDellInc.:rn0NF743:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D520 dmi.sys.vendor: Dell Inc. fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.31-5-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- screen flickering on dell laptop https://bugs.launchpad.net/bugs/410305 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 410305] Re: screen flickering on dell laptop
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/30005808/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/30005809/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/30005810/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/30005811/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/30005812/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/30005813/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/30005814/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/30005815/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/30005816/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/30005817/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/30005818/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/30005819/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/30005820/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/30005821/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/30005822/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/30005823/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/30005824/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/30005825/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/30005826/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/30005827/xkbcomp.txt -- screen flickering on dell laptop https://bugs.launchpad.net/bugs/410305 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 410305] Re: screen flickering on dell laptop
It seems to have been a problem with the in-kernel part of the driver and KMS, fixed in the latest kernel update (2.6.31-6): * I spotted some flicker in usplash and text console as well * booting without KMS removed it * it is gone, even with KMS enabled in 2.6.31-6 (and back if booting again on 2.6.31-5, it was not fixed by one of the other updates) For the record, here is a short answer to your question: The symptoms are similar to that of bug #399829: many redraw trigger screen flickering, for exemple moving windows of the gdm animations, even text scrolling in a terminal the only difference is that changing the resolution did not work arround it for me, otherwise, the flickering looked like the one in the video linked in bug #399829. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Fix Released -- screen flickering on dell laptop https://bugs.launchpad.net/bugs/410305 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 409673] Re: latest poppler prevents pdftex/pdflatex from working correctly
short version: fixed for me long version: my system was working with self-made packages of poppler 0.11.0 and the same behaviour appeared (I guess) after the latest texlive update. It is now working fine again with the poppler version available in the archive but not with the older version! The mandriva bugzilla is not available right now si I can't check in it, but what is the reason for this strict version dependancy ? Did poppler break the ABI ? will the next versions be OK should we to expect such breakage again ? -- latest poppler prevents pdftex/pdflatex from working correctly https://bugs.launchpad.net/bugs/409673 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 54002] Re: No need to convert LVM volumes to UUIDs
I have mixed feelings about this. I was about to report a similar bug for grub as the move to UUID everywhere currently prevents my edgy system from booting (I can boot if I put back the old "root=/dev/mapper/" argument in grub). I am marking this as also affecting grub, for the record. On the other hand, I find UUID better than labels or lvm volume names as they are more likely to be uniq. A while ago I put a friend's hard drive in my computer to get its data back, we where both using LVM with identical volume names, which was a bit problematic (I don't remember the details though). UUIDS might help in this area, but pushing the user to choose non-clashing LVM names might be enough. ** Also affects: grub (Ubuntu) Importance: Untriaged Status: Unconfirmed -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
I guess that the original reporter really did mean "not needed", but it my case, it causes a bug :) I have just checked, it is still present after recreating my initramfs. The problem is that it can not find my LVM volume by UUID. The strange thing is that /etc/fstab has also been modified to use UUID (making it much less nice to edit manually) and it did not cause any problem, though my /home partition is also a LVM one and it does _NOT_ appear in /dev/disk/by-uuid/ !! My exact setup is LVM on software RAID 5. I am not very fluent with the initramfs process so I can not tell in which state it is when it drops me the busybox shell, but I could give you output of commands run from it if needed. LVM "partitions" are under /dev/mapper/ and the user can choose their name. Mine are called: vg_$VG-lv_$HOST$PART where $VG designs the volume group to which it belongs, $HOST is my hostname (to avoid clashes when adding disks from a similar installation from another host) and $PART is the role of this volume (home, root32 and root64 in my case). -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54205] Re: font rendering broken in edgy
-- font rendering broken in edgy https://launchpad.net/bugs/54205 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54205] font rendering broken in edgy
Public bug reported: after the recent upgrade of gtk-engines, the font rendering is broken in edgy, as chown in the attached picture ** Affects: gtk-engines (Ubuntu) Importance: Untriaged Status: Unconfirmed -- font rendering broken in edgy https://launchpad.net/bugs/54205 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54205] Re: font rendering broken in edgy
No, I am using the default ubuntu theme on an up to date edgy system. ii xserver-xorg-core1.1.1-0ubuntu1 X.Org X server -- core server ii xserver-xorg 7.0.22ubuntu6the X.Org X server ii ubuntu-artwork 31 Ubuntu themes and artwork ii human-gtk-theme 0.1-0ubuntu1 Edgy GDM themes (typo in the title ?) it was working fine before the update of ubuntu-artwork and renaming of its dependancies. Why are you saying "(minus xserver-xorg-core)" ? Is there a known problem with it ? -- font rendering broken in edgy https://launchpad.net/bugs/54205 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54205] Re: font rendering broken in edgy
update: I have just launched a Qt app to check and it has the same problem, it is not a gtk/pango thing. I might be related with the last xft update: xft (2.1.10-1ubuntu1) edgy; urgency=low . * Merged with Debian experimental * Fixed libfreetype6-dev Build-Depends I have this version, I updated it without noticing at the same time as gtk engines. I just tried reverting to version 2.1.8.2 (from dapper) but this did not solve my problem. Any other idea ? -- font rendering broken in edgy https://launchpad.net/bugs/54205 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54205] Re: font rendering broken in edgy
Indeed, I was using the nvidia binary driver. I thought it would not work at all without explicitely telling it to ignore ABI changes... Great to have xorg 7.1 then, and sorry for the noise! I am marking the bug as rejected as they is nothing we can do with it, until a free drivers exists :/ ** Changed in: gtk-engines (Ubuntu) Status: Needs Info => Rejected -- font rendering broken in edgy https://launchpad.net/bugs/54205 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59211] Re: Blam doesn't start since Mono update (Edgy)
I can also confirm this problem. The same happened with f-spot which is now fixed, I tried to rebuild the package (using apt-get source...) but this failed with: Printing.cs(17,10): error CS0104: `PrintJob' is an ambiguous reference between `Gnome.PrintJob' and `Gtk.PrintJob' after adding the "Gnome." prefix in two places I was able to build it but the original problem did not vanish. Changing the signature did not solve it either: this function is associated with both the "delete_event" (close button) and the "quit_action" (menu item) which require different signatures. Oddly, this argument is not used and making it an object also triggers this error :/ I had to create a second function (simple delegate) to associate with the delete event. I am attaching a patch including all these changes but I'm not sure it is well formatted. ** Attachment added: "patch solving compilation errors and method signature" http://librarian.launchpad.net/4165121/fixblam.patch -- Blam doesn't start since Mono update (Edgy) https://launchpad.net/bugs/59211 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59733] Re: Openoffice Writer Crashes when Saving
*** This bug is a duplicate of bug 58492 *** ** This bug has been marked a duplicate of bug 58492 Openoffice.org crashes on "Save" -- Openoffice Writer Crashes when Saving https://launchpad.net/bugs/59733 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58492] Re: Openoffice.org crashes on "Save"
An less hideous workaround if you are the only user of the system is to use openoffice's dialog for open/save (in the "general" section of the options). Anyway I am happy to learn that a rebuild is sufficient to get back gnome's save dialog! ** Bug 59733 has been marked a duplicate of this bug -- Openoffice.org crashes on "Save" https://launchpad.net/bugs/58492 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59946] Re: run action as root without prompting for a password
indeed, when launched by a normal user, users-admin crashes and the terminal output says that this user was not allowed to send a dbus message. Sorry for the extra fear it gave me. I am still pretty sure to have launched it as a normal user a while ago, but this was either a separate (fixed) bug or some mis-remember on my part. I still dislike being able to launch it without sudo controlling (it is especially bad for people with custom sudo configuration, but they can work around it manually I guess). Anyway, if a member of the admin group is compromised, something bad can be done, it only makes things a bit easier. Nice to have the UI running fully as non-priv user anyway! -- run action as root without prompting for a password https://launchpad.net/bugs/59946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58940] Re: evolution-data-server crashed on startup
It did also happen at each login for me. I get ride of it by removing all references to external calendars, I think I had something weird with my config. I tried once to add a google-calendar source but entered it in the bad section and then I was unable to delete it. After some gconf cleanup the old not-really-existing-calendar is gone and the crash with it. Sorry, I do not have any gdb backtrace, I just remember that this backtrace was harder to get than others as evolution ran another instance and did not use the one I attached. The crash at login time is probably triggered by the clock-applet. When running evo itself, the mail part was working fine and everything went wrong when switching to he calendar part. -- evolution-data-server crashed on startup https://launchpad.net/bugs/58940 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52373] Re: latest firefox update breaks gmail
** Bug 59428 has been marked a duplicate of this bug -- latest firefox update breaks gmail https://launchpad.net/bugs/52373 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59428] Re: Firefox compatibility issues with gmail in Edgy!!!
*** This bug is a duplicate of bug 52373 *** ** This bug has been marked a duplicate of bug 52373 latest firefox update breaks gmail -- Firefox compatibility issues with gmail in Edgy!!! https://launchpad.net/bugs/59428 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61922] [edgy] javascript weirdness in epiphany
Public bug reported: Binary package hint: epiphany-browser I have some strange behaviour for javascript-using webpages in epiphany. As an example, gmail works properly except that I can not actually view any email (the mail is marked as read but I stay in the list). In the same vein, neither google-calendar nor google-maps do anything usefull. I had this problem with both epiphany and firefox, now it works fine with firefox but not with epiphany. It also does not work for a new user without any configuration files. The strangest thing is that the very same(s) google account works just fine on another edgy system, still with epiphany! (and it did work fine on the same system under dapper) I really do thing something weird is wrong with firefox/gecko/epiphany on my system, as somme other website using javascript do not work on _this_ system (like authenticating into ldlc.com, a french hardware vendor). All these sites works fine with firefox or mozilla. I do not have xulrunner installed and already tryied "apt-get install --reinstall" epiphany and firefox without success. Any hint about a possible culprit ? ** Affects: epiphany-browser (Ubuntu) Importance: Untriaged Status: Unconfirmed -- [edgy] javascript weirdness in epiphany https://launchpad.net/bugs/61922 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38745] Re: Clicking gmail messages doesn't always display email
This _might_ be related to a problem I am currently experiencing on edgy, see bug 61922 -- Clicking gmail messages doesn't always display email https://launchpad.net/bugs/38745 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147609] Re: jetdirect printer prints only the first page
The recent updates (not sure which one of which package...) fixed the problem for me :) Does it still happen to you ? -- jetdirect printer prints only the first page https://bugs.launchpad.net/bugs/147609 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 147609] Re: jetdirect printer prints only the first page
As it seems to be gone for both of us, I think it is better to close it... ** Changed in: cupsys (Ubuntu) Status: New => Fix Released -- jetdirect printer prints only the first page https://bugs.launchpad.net/bugs/147609 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 136469] Re: toshiba p100 series dsdt acpi error no sound, works with acpi turned off.
I can confirm this with the latest kernel in gutsy, not sure if it worked on feisty (I only installed gutsy on this one). Does anyone know if a fix may enter gutsy before the final release ? -- toshiba p100 series dsdt acpi error no sound, works with acpi turned off. https://bugs.launchpad.net/bugs/136469 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 33027] Re: [dapper] tooltip should disappear
yes, the tooltip are still not going away in gutsy for me (or with a way too large timeout). -- [dapper] tooltip should disappear https://bugs.launchpad.net/bugs/33027 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 147609] Re: jetdirect printer prints only the first page
I think I have the very same problem, whatever I print using gutsy I get only one page (which can be two-sided), printing to the same network printer from feisty works. -- jetdirect printer prints only the first page https://bugs.launchpad.net/bugs/147609 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 147651] openoffice crash on ppt export
Public bug reported: Binary package hint: openoffice.org one particular slides of one of my odt presentations crashes reliably the ppt export of openoffice. The fun thing is that this slide does not have anything fancy, it is juste a slightly modified version of another slide (some text, colors and arrow direction changed) attached are the two faulty slides (the "bad" one is the second one). ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New -- openoffice crash on ppt export https://bugs.launchpad.net/bugs/147651 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 147651] Re: openoffice crash on ppt export
** Attachment added: "a 2-slides odt file which triggers the crash" http://launchpadlibrarian.net/9619226/crash_pptExport.odp -- openoffice crash on ppt export https://bugs.launchpad.net/bugs/147651 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 147609] Re: jetdirect printer prints only the first page
I think so, the cups URI is: hp:/net/HP_LaserJet_P2015_Series?ip= -- jetdirect printer prints only the first page https://bugs.launchpad.net/bugs/147609 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 147670] bad thumnaild and printed version for some pdf
Public bug reported: Binary package hint: evince The thumbnails generated by evince for some pdf are incomplete (see the first file in the attached screenshot). When opening this file, I can "force" evince to display the text by selecting it. This is painfull but the content seems to be OK. Then, if I print this file I get a fun bug (also available in the "print preview" dialog): on _some_ (2) lines, the spaces are replaced by 't'. This happens on an up to date gutsy (beta1), on feisty, evince can open and print this file correctly. PS: I can provide the file on demand but not attach it to the bug report (nature papers are not freely available :/) ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- bad thumnaild and printed version for some pdf https://bugs.launchpad.net/bugs/147670 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 147670] Re: bad thumnaild and printed version for some pdf
** Attachment added: "screenshot of the bad thumbnail (the first file, all others, also from nature are OK)" http://launchpadlibrarian.net/9620586/bad_thumb.png -- bad thumnaild and printed version for some pdf https://bugs.launchpad.net/bugs/147670 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 147670] Re: bad thumnaild and printed version for some pdf
I had already the post-beta updates, I am using libcairo2 1.4.10-1ubuntu4 (which is stated _not_ to solve #116236). It is probably not the same problem anyway: the pdf file given in #116236 (the first one, not the firefox ad) opens fine in my gutsy system and badly in feisty, while the pdf about which I reported this bug opens fine in feisty and badly in gutsy. I also want to say again that this is _not_ only a display problem: some weird artefact appeared in the printed version (which are not present when printing from feisty) -- bad thumnaild and printed version for some pdf https://bugs.launchpad.net/bugs/147670 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 205923] Re: openoffice in hardy doesn't build on powerpc
It failed again. It looks to be caused by the mozilla plugin this time (and it failed for the same reason on i386, I bet the plugin is disabled on the arch that succedeed) mkdir -p -m755 debian/mozilla-openoffice.org/usr/lib/openoffice/program for f in libnpsoplugin.so nsplugin; do \ mv debian/openoffice.org-core/usr/lib/openoffice/program/$f debian/mozilla-openoffice.org/usr/lib/openoffice/program; \ done mv: cannot stat `debian/openoffice.org-core/usr/lib/openoffice/program/libnpsoplugin.so': No such file or directory mv: cannot stat `debian/openoffice.org-core/usr/lib/openoffice/program/nsplugin': No such file or directory make: *** [debian/stampdir/install-arch] Error 1 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2 ** Build finished at 20080415-2122 FAILED [dpkg-buildpackage died] -- openoffice in hardy doesn't build on powerpc https://bugs.launchpad.net/bugs/205923 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 205923] Re: openoffice in hardy doesn't build on powerpc
Once again the build failed. At least the cause looks different this time! ** Changed in: openoffice.org (Ubuntu Hardy) Status: Fix Released => Confirmed -- openoffice in hardy doesn't build on powerpc https://bugs.launchpad.net/bugs/205923 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 225794] Re: Xorg freeze after a while with intel driver
oups, submitted too quickly... ii xorg 1:7.3+10ubuntu10 X.Org X Window System ii xserver-xorg 1:7.3+10ubuntu10 the X.Org X server ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9 Xorg X server - core server ii xserver-xorg-input-all 1:7.3+10ubuntu10 the X.Org X server -- input driver metapacka [...] ii xserver-xorg-video-i8102:1.7.4-0ubuntu7 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-intel 2:2.2.1-1ubuntu12 X.Org X server -- Intel i8xx, i9xx display d attached is also the Xorg.log, not sure it really helps as I had too reboot the hard way. syslog doesn't show anything interresting either. At least it didn't the other times I checked but as I'm writing this I found some lines that were not present after the previous crashes: The OOM killer did its job and broke evrything. After enabling again my swap (installing FC9 changed its id which is whi it was missing) I can play a bit longer without freezing: $ free -m total used free sharedbuffers cached Mem: 995986 9 0 0 32 -/+ buffers/cache:953 42 Swap: 2863301 2561 I have only the epiphany running (on this page plus gmail), a terminal and evince. After closing evince, I get much nicer numbers: $ free -m total used free sharedbuffers cached Mem: 995427567 0 0 43 -/+ buffers/cache:384611 Swap: 2863146 2717 looks like a memory leak ** Attachment added: "Xorg log (also with XAA, ends like when using EXA)" http://launchpadlibrarian.net/14091445/Xorg.0.log.old ** Changed in: evince (Ubuntu) Sourcepackagename: xorg => evince -- Xorg freeze after a while with intel driver https://bugs.launchpad.net/bugs/225794 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 225794] Re: Xorg freeze after a while with intel driver
** Attachment added: "xorg.conf (with XAA)" http://launchpadlibrarian.net/14091228/xorg.conf -- Xorg freeze after a while with intel driver https://bugs.launchpad.net/bugs/225794 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 225794] [NEW] Xorg freeze after a while with intel driver
Public bug reported: Binary package hint: xorg Hardware: laptop dell latitude, integrated intel graphic card Software: up to date hardy AMD64 (updated from gutsy and followed half of hardy devel cycle, I'll check with a fresh install when I have time to do so). compiz is disabled, it happens when using EXA and XAA. Since when: I'm pretty sure the bug was not present in gutsy but I didn't use much this laptop during hardy cycle so I can't tell for sure the system works fine but freezez from time to time (i.e. the mouse doesn't move, keybord is not responsive, even sysreq are most of the time useless - I couldn't try an ssh connection yet. After disabling compiz it still happens and seems to be related to my use of evince or openoffice. It look like I can reproduce it quite reliably by launching evince and playing with the scrollbar to force it to redraw tons of things. It take a variable amount of time but always freezes if I insist (it also freezes when I'm reading normally but this is a bit random). I also tried using XAA without any luck output of lspci: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 02:01.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 21) 02:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Xorg freeze after a while with intel driver https://bugs.launchpad.net/bugs/225794 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 225794] Re: Xorg freeze after a while with intel driver (i945gm)
All freezes happened while doing something (reading pdf, using openoffice). Il all cases I had not-so-big pdf(s) opened in evince. As I said in my previous comment (after which I reassigned the bug to evince which was then changed), it indeed looks like a memory leak: the memory used by evince increases when going back and forth in the document with the scrollbar (in continuous mode). running "watch free -m" in a terminal while using evince I can confirm that: * open a pdf * scroll down and back up (slowly to make sure it rendered everything) * check memory usage * scroll down and up a couple more times * memory usage increased by 300Mo if I keep doing so it becomes very slow and unresponsive as it swaps (already better than the freezes I add). It doesn't seem to happen (at least not at the same speed) on all pdf, and I can't attach here the ones that triggerd it for me (most journals are picky about what we do with their pdfs :/ ). I can't test now if this happens when using an other graphic card but I will next week. -- Xorg freeze after a while with intel driver (i945gm) https://bugs.launchpad.net/bugs/225794 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 225794] Re: Xorg freeze after a while with intel driver (i945gm)
On Thu, May 8, 2008 at 9:18 AM, unggnu <[EMAIL PROTECTED]> wrote: > It is true that Evince consumes much memory but not more than 130 MB on > my pc and it often reduces consumption after some time. Since I have > enough memory I can't confirm it. Could you recheck this issue with a > Live CD? Is compiz always enabled? > This is without compiz (as I have problems with it and java applications). I will do more tests with live-cd and a different computer next week. -- Aurélien Naldi -- Xorg freeze after a while with intel driver (i945gm) https://bugs.launchpad.net/bugs/225794 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 136251] Re: trackerd crashed with SIGSEGV
it may be related to bug #138399 and/or #136523 -- trackerd crashed with SIGSEGV https://bugs.launchpad.net/bugs/136251 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 20704] Re: can't cancel stalled remote transfer
The upstream bug is very unlikely to get fixed at all now that the backend of nautilus is switching from gnome-vfs to gio/gvfs: whatever the current status, isn't it better to close this bug as wontfix ? I have juste tested on hardy with the new nautilus and sftp: * I can cancel a "live" network copy * A copy continues when the network comes back * If I unplug the network and then try to cancel the transfer, it does nothing but grey out the cancel button. It will finish to cancel it a while after I plug back the network. * I have tried to wait 5 minutes for the transfer to timeout in absence of network, it doesn't, and doesn't allow me to cancel it either So the new situation is a bit better than the previous one, but the problem is still present IMHO. -- can't cancel stalled remote transfer https://bugs.launchpad.net/bugs/20704 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 107122] Re: openoffice impress does not display slide show under compiz
*** This bug is a duplicate of bug 104956 *** https://bugs.launchpad.net/bugs/104956 ** This bug has been marked a duplicate of bug 97630 A Openoffice Impress presentation is not correctly exported to PDF ** This bug is no longer a duplicate of bug 97630 A Openoffice Impress presentation is not correctly exported to PDF ** This bug has been marked a duplicate of bug 104956 Ubuntu 7.04 beta openoffice 2.2 can't display presentations with "Desktop Effects" enabled, when using dual-monitor -- openoffice impress does not display slide show under compiz https://bugs.launchpad.net/bugs/107122 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 120525] transparency rendering problem in presentations
Public bug reported: Binary package hint: openoffice.org I have an OOo impress presentation using some transparency (to have a gradient as background in the master pages). In edit mode it renders fine but does not work in presentation mode: every partially transparent item is completely hidden (i.e. white background). The pdf export is OK. Changing the rendering options (use of openGL and hardware accel) does not help. The templates provided with the ubuntu package have the same problem. It happens on an up to date feisty, both on a G5 (ATI graphic card) and a P4 (intel chip) so it is probably not related to the video drivers. ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: Unconfirmed -- transparency rendering problem in presentations https://bugs.launchpad.net/bugs/120525 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 103608] Re: [feisty] boot stuck in the initramfs
This has been fixed a while ago, with other MD/LVM related bugs. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Unconfirmed => Fix Released -- [feisty] boot stuck in the initramfs https://bugs.launchpad.net/bugs/103608 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 205923] Re: openoffice in hardy doesn't build on powerpc
It seems that the new OOo upload still didn't build on PPC (binaries for x86 and AMD64 are available). According to http://launchpadlibrarian.net/13083788/buildlog_ubuntu-hardy- powerpc.openoffice.org_1%3A2.4.0-3ubuntu1_FAILEDTOBUILD.txt.gz the problem is still the same: pkgmaintainermangler: Error: Unable to locate DEBIAN/control dpkg-deb: failed to open package info file `debian/openoffice.org-report-builder/DEBIAN/control' for reading: No such file or directory dh_builddeb: command returned error code 512 make: *** [debian/stampdir/binary-arch] Error 1 -- openoffice in hardy doesn't build on powerpc https://bugs.launchpad.net/bugs/205923 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 122549] [gutsy] compiz fusion breaking gnome-screensaver behaviour
Public bug reported: Binary package hint: compiz I have some weird misbehaviour of gnome-screensaver in combination with compiz fusion in gutsy. It is not 100% reproductible but happens most of the time. It looks like compiz does not let the screensaver lock the screen properly: when the "unlock screen" dialog appears, it does not have the focus: One can not enter a password to unlock the screen. What is much worse is that an OTHER window has the focus: with the screen locked, I was able to enter commands in an opened terminal. I was even able to see their output thanks to compiz: it lets me cycle through window, showing me its usual composited alt-tab... Changing desktop was also possible, but I could not trigger the scale plugin by going to a screen edge. The focus seems to come back to the screensaver after a while (but one can still cycle through other windows and change desktop). Disabling desktop effects and using plain metacity, everything works as expected. It happens at least with the last 3 git snapshots of compiz in gutsy, AFAIR it did not happen with feisty. Note: I am tempted to consider this as a security vulnerability as it allows to circumvent the "protection" offered by a screensaver. Should it be considered as such ? output of dpkg -l | grep compiz: ii compiz1:0.5.1+git20070626-0ubuntu1 OpenGL window and compositing manager ii compiz-bcop 0.0.0+git20070612-0ubuntu1 Compiz option code generator ii compiz-core 1:0.5.1+git20070626-0ubuntu1 OpenGL window and compositing manager ii compiz-dev1:0.5.1+git20070626-0ubuntu1 OpenGL window and compositing manager - deve ii compiz-fusion-plugins-extra 0.0.0+git20070622-0ubuntu1 Collection of extra plugins from OpenComposi ii compiz-fusion-plugins-main0.0.0+git20070626-0ubuntu1 Collection of plugins from OpenCompositing f ii compiz-gnome 1:0.5.1+git20070626-0ubuntu1 OpenGL window and compositing manager - GNOM ii compiz-plugins1:0.5.1+git20070626-0ubuntu1 OpenGL window and compositing manager - plug ii compizconfig-settings-manager 0.0+git20070625-0ubuntu1 Compiz configuration settings manager ii libcompizconfig-backend-gconf 0.0+git20070620-0ubuntu1 Settings library for plugins - OpenCompositi ii libcompizconfig0 0.0+git20070626-0ubuntu1 Settings library for plugins - OpenCompositi ii python-compizconfig 0.0.0+git20070622-0ubuntu1 Compiz configuration system bindings ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- [gutsy] compiz fusion breaking gnome-screensaver behaviour https://bugs.launchpad.net/bugs/122549 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 103608] Re: [feisty] boot stuck in the initramfs
I just ran update-initramfs for my two kernels and I the problem happens only with the latest one: "2.6.20-14", so I am reassigning the package. just in case, my initramfs is available here: http://crfb.univ-mrs.fr/~naldi/initrd.img-2.6.20-14-generic ** Changed in: linux-source-2.6.20 (Ubuntu) Sourcepackagename: lvm2 => linux-source-2.6.20 -- [feisty] boot stuck in the initramfs https://bugs.launchpad.net/bugs/103608 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 103696] Re: System fails to boot with 2.6.20-14
might be related to #103679, and to #103608 ? (I am the original reporter of the second, and I have seen the same error messages as in the first) -- System fails to boot with 2.6.20-14 https://bugs.launchpad.net/bugs/103696 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 103608] Re: [feisty] boot stuck in the initramfs
This looks similar to some other reported bugs: #103679 (I have seen the same "failed to set xfermode" in the busybox shell) and #103696 -- [feisty] boot stuck in the initramfs https://bugs.launchpad.net/bugs/103608 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
Re: [Bug 103696] Re: System fails to boot with 2.6.20-14
Le samedi 07 avril 2007 à 01:19 +, Cafuego a écrit : > Aurelien: > > I don't see any messages like the ones described in #103679 - the > devices are detected properly. I don't use lvm or md on this machine, so > I don't know if #103608 is relevant. I never get dumped to a busybox > shell, bootup just halts. I have seen these messages only while collecting udevd's logs in the busybox shell. When not specifying "break=(pre)mount", o,e get dumped into the busybox shell after 3 minutes if I recall properly, most of the time I can not wait so long... If bootup is stopped and you do not get the shell after a while, this is another bug... The effect of these 3 bugs sure look different, but at least the hang introduced with the newer kernel is a common point, other symptoms might be unrelated though. -- Aurelien Naldi <[EMAIL PROTECTED]> -- System fails to boot with 2.6.20-14 https://bugs.launchpad.net/bugs/103696 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 75681] Re: boot-time race condition initializing md
I would surely test a newer udev packages if it fixes this problem. Using apt-get source to rebuild the debian package should be fairly easy, but I guess ubuntu maintains a set of additionnal patches, and merging them might be non-trivial. Is any of the ubuntu dev willing to upload a test package somewhere ? Reading the debian bug, I am not convinced it is the same problem, on my system I have SOME devices created and other lagging behind, the debian bug seems to be about devices not created at all. If the newer udev does not fix this problem, is it doable to detect "stalled" RAID array and to stop them ? -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1] Re: Microsoft has a majority market share
> * Third party Software vendors have no easy way to figure out, which version > of Ubuntu is installed on a particular computer in order to deal with > backward > compatibility issues: There is no ``/etc/Ubuntu_version`` and the file > ``/etc/debian_version`` still tells ``testing/unstable``. /etc/lsb-release exists, and should be used instead. -- aurelien naldi -- Microsoft has a majority market share https://launchpad.net/bugs/1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
Here is my output for udevd. I needed several boots to get it, so I hope it helps ;) ** Attachment added: "output of udevd --verbose" http://librarian.launchpad.net/7031494/udevd.out -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75681] Re: boot-time race condition initializing md
I am not on this system right now so I can't upload my initramfs yet,
I will probably do it later tonight.
I have four SATA drives and two installations (i386 and AMD64, both
feisty, this is in the i386 one, the AMD64 one is not up to date and I
use it as a rescue system).
Every hard drive has a very similar partitionning scheme:
* boot partition (two installs, each has a backup of its main
"/boot", not exactly up to date as I have been too lazy to write a
small script)
* swap partition or small temporary data partition
* the main RAID partition
I have a single RAID5 system, md0 using sda3, sdb3, sdc3 and sdd3
md0 is a LVM group, (vg_raid if I recall correctly) and contains three volumes:
the "root" partition for my two install and a big shared "/home"
is it any other think that may help you, beside my initramfs ?
I guess you do not need the mdadm config file as it is included...
On 3/28/07, Ian Jackson <[EMAIL PROTECTED]> wrote:
> Aurelien Naldi writes ("[Bug 75681] Re: boot-time race condition initializing
> md"):
> > Here is my output for udevd. I needed several boots to get it, so I hope
> > it helps ;)
>
> Thanks, that's going to help a lot I think. Can you please put up a
> copy of your initramfs (/initrd.img) too ? It'll probably be too
> large to mail and I'm not sure LP will take it, so you probably want
> to put it on a webserver somewhere.
>
> Ideally it would be the initramfs from the same test run as the log
> but another will do.
>
> Also, to help me understand this log, can you describe your raid and
> LVM setup ?
>
> Ian.
>
> --
> boot-time race condition initializing md
> https://launchpad.net/bugs/75681
>
--
aurelien naldi
--
boot-time race condition initializing md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75681] Re: boot-time race condition initializing md
On 3/28/07, Ian Jackson <[EMAIL PROTECTED]> wrote:
> Aurelien Naldi writes ("Re: [Bug 75681] Re: boot-time race condition
> initializing md"):
> > With older versions (of mdadm I think) the RAID was assembled, but
> > degraded or kind of assembled but not startable (when only 1 or 2 disk
> > were present at first). a "--no-degraded" option was added in the
> > mdadm script to avoid this. Now the RAID does not try to start when
> > drive(s) are missing (i.e. is never assembled in degraded mode) but
> > weird things are still hapening.
>
> OK, so the main symptom in the log that I'm looking at was that you
> got an initramfs prompt ?
a normal boot would have given me a busybox yes, but I added
"break=premount here", so the shell is not exactly a bug ;)
The bug is that my array was not _correctly_ assembled after running udevtrigger
> > I do not recall which devices were in the "assembled" array when I
> > launched this one, but the RAID was _not_ degraded. But I guess you
> > have it right: I had sometime enough time to see in /proc/partition
> > only a few of my drives, and the array was assembled with these. Once
> > all the devices are there, runing /scripts/local-top/mdadm again fixes
> > it all.
>
> Right. Did you have to rerun vgscan ?
Not this time, but the array was present and exiting the shell
resulted in a working boot, LVM has no problem anymore for me.
> > after running udevd and udevtrigger, I checked that things were well
> > broken (it works too fine in my two first attempts) and then all I had
> > to do is running "/scripts/local-top/mdadm" once more and the array
> > was correctly assembled.
>
> Right.
>
> > I have not started LVM by hand, I copied the udevd.out to one of my
> > normal partition, then exited the shell and it finished to boot fine.
>
> You mounted your root fs by hand, though ?
No, I copied the output to one of my boot partition, one that is _not_
in the RAID/LVM. I did it to avoir running vgscan and friends by hand
to see if the next part of the boot goes fine or not.
--
boot-time race condition initializing md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
my initramfs can be found here: http://gin.univ-mrs.fr/GINsim/download/initrd.img-2.6.20-13-generic NOTE: it is note the one on which I booted this morning but I think I reverted all changes and built it again, so it should be pretty similar ;) -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75681] Re: boot-time race condition initializing md
Le mercredi 28 mars 2007 à 22:55 +, Ian Jackson a écrit : > I see. Err, actually, I don't see. In what way was the assembly of > the raid incorrect ? You say it wasn't degraded. Was it assembled at > all ? Was it half-assembled ? My memory does not deserve me right, sorry! In previous versions, the array was listed in /proc/mdstat with a set of drives, but not really assembled. before running the mdadm script I had to stop it... This bug is now gone, the array was _not_ assembled and I could run the mdadm script directly ;) -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
OK, I really appreciate that you want to fix this and I really want to help, but this has been driving me nuts. I can reproduce it *way too* reliably with a "normal" boot (i.e. it happens 8 times out of 10) but when trying to get a log it suddenly refused to happen :/ I started to think that the echo line added to the mdadm script caused a sufficient lag to avoid the trap and rebooted without this line, I could reproduce it and get a log at the first boot! Unfortunatly I messed somethings up and thus tryed to make a new one without much success. Then I put the "echo running" line back and I have tried again and again for half an hour to finally get one, but I forgot to put a ">>" instead of a ">" when redirecting udevd's output. I give up for now as I have been unable to reproduce it since (except twice with "normal" boot, but not willing to wait 3minutes...) so, here it is, I attach a tar.gz of the log I made, and I put my initramfs here: http://crfb.univ- mrs.fr/~naldi/initrd.img-2.6.20-13-generic What I did: boot with break=premount launch udevd & udevtrigger, check that the bug happened, collect some info to fix it: /scripts/local-top/mdadm lvm vgscan lvm vgchange -a y collect some more info mount /dev/sda1 on /mnt # an ext2 partition for /boot copy my log files here umount /mnt pkill udevd (sorry, I might have get nicer logs if I stopped it before, right ?) exit watch it finish booting ** Attachment added: "some log files" http://librarian.launchpad.net/7045516/aurelien_mdadmrace_logs.tgz -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75681] Re: boot-time race condition initializing md
On 3/28/07, Ian Jackson <[EMAIL PROTECTED]> wrote: > > Every hard drive has a very similar partitionning scheme: > > * boot partition (two installs, each has a backup of its main > > "/boot", not exactly up to date as I have been too lazy to write a > > small script) > > * swap partition or small temporary data partition > > sd?1 and sd?2 respectively, I take it ? yes sd?1 are boot partitions and sd?2 swap/other > Do you recall in what state the md0 raid came up ? The symptom as I > understand it is that it came up degraded ? Looking at the log, the > disks were found in the order sda3 sdd3 sdb3 sdc3 so if it came up > degraded was sdc3 missing ? With older versions (of mdadm I think) the RAID was assembled, but degraded or kind of assembled but not startable (when only 1 or 2 disk were present at first). a "--no-degraded" option was added in the mdadm script to avoid this. Now the RAID does not try to start when drive(s) are missing (i.e. is never assembled in degraded mode) but weird things are still hapening. I do not recall which devices were in the "assembled" array when I launched this one, but the RAID was _not_ degraded. But I guess you have it right: I had sometime enough time to see in /proc/partition only a few of my drives, and the array was assembled with these. Once all the devices are there, runing /scripts/local-top/mdadm again fixes it all. > > And the LVM works properly now ? after running udevd and udevtrigger, I checked that things were well broken (it works too fine in my two first attempts) and then all I had to do is running "/scripts/local-top/mdadm" once more and the array was correctly assembled. I have not started LVM by hand, I copied the udevd.out to one of my normal partition, then exited the shell and it finished to boot fine. One more comment: I have tested some other suggested workarround: - removing the mdrun script did not help (the first thing done by this script is to check the presence of the mdadm one and then to exit) - adding a timeout in "/usr/share/initramfs-tools/init" works fine for me: 5 seconds are not enough but 8 are OK ;) -- aurelien naldi -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103608] [feisty] boot stuck in the initramfs
Public bug reported: Binary package hint: lvm2 recent updates in feisty fixed a race condition at boot time between mdadm and sata hard drives. This fix seems to have been working for me. more recently, the kernel was updated to 2.6.20-14. This updates and the one coming along broke my boot again. Unfortunatly I do not have much time yet to rebuild the initramfs for the 2.6.20-13 kernel, to test if the problem comes from the kernel or from the userland tools, but I plan to do so later today. Here is a first report with logs collected in the busybox shell: * boot with break=premount * run udevd --verbose and store the output * run udevtrigger * at this point, NONE of my devices has been detected, they used to appear immediatly with previous versions. * near to one minute later, the console show a bunch of new lines and my hard drives have been properly detected, and my /dev/md0 mdadm array is also here. The only missing stuff if the lvm volumes. * running lvm vgscan/vgchange -a y by hand creates the corresponding devices without a problem udev 108-0ubuntu3 lvm-common 1.5.20ubuntu12 lvm2 2.02.06-2ubuntu9 busybox-initramfs 1.1.3-3ubuntu3 initramfs-tools0.85eubuntu8 linux-image-2.6.20-14-generic 2.6.20-14.22 I will post my initramfs in a web page and comment back later tonight PS: PLEASE do something quickly, as I will move on next monday until after the feisty release and will not be able to help tracking it :/ ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [feisty] boot stuck in the initramfs https://bugs.launchpad.net/bugs/103608 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 103608] Re: [feisty] boot stuck in the initramfs
** Attachment added: "collected logs" http://librarian.launchpad.net/7177647/log_udevd.tgz -- [feisty] boot stuck in the initramfs https://bugs.launchpad.net/bugs/103608 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 75681] Re: boot-time race condition initializing md
I have just tested upgrading to the debian udev package and (beside being painfull) it completly broked my system. I think that people here are experiencing two different bugs, as _for_me_ /dev/sd* files are created normally, just with a few seconds of delay, making mdadm blocked after trying to assemble an array for which some devices are still missing. * I could not use prevu to upgrade to the debian udev package as its version number (0.105) is lower than this of the ubuntu package (103), thus lvm2 complains that it will break this old version of udev. * after upgrading the version number, building the packages by hand and rebooting I got stucked and _NO_ devices was created at all. Maybe some ubuntu patches should be applied to make it work ?? * after reinstalling the older version (thanks to an other working feisty install), I could boot again. But booting does still require several attempts or adding "break=mount" option and running the mdadm script once my devices are created. One thing changed since my last comment: if I wait for the busybox shell, I do not see a half-created /dev/md0 anymore, so something improved at least ;) -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83013] Re: (Feisty) NetworkManager makes system unusable, seems to have problem with dbus
It looks more like a crash of the kernel driver for your wifi card... I have just experienced a similar problem, I will test tomorow if removing network-manager solves it. Uneducated guess: if it is "just" a driver problem, blacklisting r8187 should also solve the problem (I planned to do it but ran out of time). I will try blacklisting it and removing network-manager and comment back later. -- (Feisty) NetworkManager makes system unusable, seems to have problem with dbus https://launchpad.net/bugs/83013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83013] Re: (Feisty) NetworkManager makes system unusable, seems to have problem with dbus
Indeed, the log you posted looks like a driver problem: Jan 31 13:39:05 leon-desktop kernel: [ 46.901348] rtl8187: Card successfully reset Jan 31 13:39:10 leon-desktop kernel: [ 51.597988] BUG: unable to handle kernel NULL pointer dereference at virtual address If blacklisting it solves the error, it will also allow you to keep the network-manager installed. AFAIR this is necessary to keep ubuntu-desktop installed, which makes administration/upgrades much easier :) Anyway, I will test both here on friday (removing the network-manager then blacklisting and reinstalling it). -- (Feisty) NetworkManager makes system unusable, seems to have problem with dbus https://launchpad.net/bugs/83013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83832] Re: [feisty] mounting LVM root broken
ii lvm-common 1.5.20ubuntu11 The Logical Volume Manager for Linux (common ii lvm2 2.02.06-2ubuntu8 The Linux Logical Volume Manager ii udev 103-0ubuntu11 rule-based device node and kernel event mana ii libdevmapper1.02 1.02.08-1ubuntu4 The Linux Kernel Device Mapper userspace lib ii mdadm 2.5.6-7ubuntu3 tool to administer Linux MD arrays (software No newer version are available yet I do not have devmapper installed, and none is available (my other, working, feisty install does not have any devmapper either) It looks like I have another problem: after running udevtrigger, /dev/md0 was _not_correctly_ assembled (it was last time). It had been assembled while only two disks (out of four) had been detected. After stopping md0 and running /scripts/local-top/mdadm, it as back and working. running lvm by hand seemed to work, but I could still not mount my root partition, this time mount complained: "failed: Invalid argument" as I could not find /dev/static, I can not compare the majors/minors of /dev/mapper/* :/ I had my 3 LVM volumes as (254,[0-2]). After booting on my working install I see here 253[0-2] so this might be the problem, right ?? I tried to mount my /boot partition to copy the output files but this failed as well, and I can only attach the faulty initramfs. rebuilding the initramfs did not help (it was rebuild due to an update of usplash, done in a chroot) I see two problems now: * /dev/md0 is assembled too early (in 3 boots one worked, one had a single device in the RAID volume and one had two devices), see my comment in bug #75681. * I am unable to mount ANYTHING in the initramfs, maybe due to a wrong major number ? I guess I can mknode my devices in the initramfs, but I am a little worried that the boot will not go well if udev mangles major codes :/ ** Attachment added: "the initramfs does not work" http://librarian.launchpad.net/6351764/initrd.img-2.6.20-6-generic -- [feisty] mounting LVM root broken https://launchpad.net/bugs/83832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83832] Re: [feisty] mounting LVM root broken
creating the block devices by hand did not help. And the major/minor numbers for /dev/sda* are the same in the initramfs as in my working system. This looks pretty annoying :/ This initramfs was created in a chroot, the problem may land here ?? My working system is a 64 bit install, while the broken one is 32bit. I have mounted my root partition, its /boot, then chrooted into it and mounted /proc -- [feisty] mounting LVM root broken https://launchpad.net/bugs/83832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83832] Re: [feisty] mounting LVM root broken
OK, now I have a problem :/ I wanted to recreate the initramfs outside of a 64bit install, so I fired an edgy desktop CD: it does not support RAID/lvm anymore. The dapper CD worked fine, I recreated the initramfs. upon reboot, it is still broken. The actual problem is that I tryed to add other devices to the broken RAID array. They was added as spare drives and their superblock data got updated. Now I can not assemble the array anymore. /dev/sdb3 is correctly detected but the three other devices are seen as spare drives. It should be possible to restore the superblocks, as the one in /dev/sdb3 is still valid and contains the order of all devices in the array, but I am not sure how to do this, any pointer ? Except for the RAID superblocks, all data in the array should still be in sync, so It should be fixable, hopefully :) -- [feisty] mounting LVM root broken https://launchpad.net/bugs/83832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83832] Re: [feisty] mounting LVM root broken
Just to let you know, recreating the RAID array in the same order with the same options scared me but did work. Everything seems to be "fine", I am just done playing with it for now, waiting for your analyse of the initramfs to do more tests. Sorry for tonight's flood :) -- [feisty] mounting LVM root broken https://launchpad.net/bugs/83832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83832] Re: [feisty] mounting LVM root broken
Today I managed to boot this system again, so here are some updates: * the mount error (invalid argument) was caused by a missing "-t reiserfs" (or "-t ext2" for my /boot partition) * with "break=premount", the raid array has been correctly assembled twice (out of 4 tries), in which cas the LVM volumes have been correctly detected as well. * None of my "normal boot" (i.e. without break=[pre]mount) could assemble the array I attach the output of udevd, corresponding to a boot where the RAID array has been assembled in degraded mode (resync is ongoing right now) ** Attachment added: "udevd --verbose output" http://librarian.launchpad.net/6387250/udevd-output -- [feisty] mounting LVM root broken https://launchpad.net/bugs/83832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
There is still a race condition here. I does not attempt to start the array before detecting devices but it often starts it too early. My 4 devices RAID5 is, most of the time, either not assembled (i.e. 1 or 2 devices out of 4 is not enough) or assembled in degraded mode. An array should be assembled in degraded mode ONLY when no more devices are expected (or at least after a timeout)! -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
The first boot went fine. The next one hanged. And the next one went also fine. For all of them, I get the message "no devices listed in cinf file were found" but it looks harmless. I do not know were the second one hanged so it may be unrelated, but it was before mounting / -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
>From the changelog of mdadm 2.5.6-7ubuntu4: Specify --no-degraded argument to mdadm in initramfs; this can be overridden by setting MD_DEGRADED_ARGS to some nonempty value (eg, a single space). This ought to fix race problems where RAIDs are assembled in degraded mode far too much. (LP #75681 and many dupes.) This looks much more like a work arround than a real fix! I may misunderstand it, please ignore me if this is the case :) Does it mean that I have to enter commands in the initramfs or to do some kind of black magic to boot a system with a broken hard drive ? And it only avoids to desynchronise a working RAID, it does not fix the race at boot time as mdadm does still try to assemble the array with too few drives and thus refuses to assemble it properly later. The array should _not_ be started _at_all_ unless all needed devices have been detected (including spare ones) OR when all device detection is done. So I ask it again, is it any way to make udev send a special signal when devices detection is finished ? Is it any way to make mdadm scan for arrays and assemble them ONLY if all of their devices are present, doing _nothing_ otherwise ? It may be tricky but I think that these problems can only be fixed this way. Anyway, it did work before. -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73345] Re: X crashes when using Xv or fullscreen-SDL with binary nvidia driver
This pretty old bug has only been fixed in the latest version of the nvidia binary drivers: 1.0-9746, released December 21, 2006. Installing this version manually solved it for me, both in edgy and in feisty. Is it any hope to include this version, at least for feisty or is it any other blocker ? -- X crashes when using Xv or fullscreen-SDL with binary nvidia driver https://launchpad.net/bugs/73345 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84437] Re: apt-get: missing/wrong package in repository
How is it a bug ? Installing this package requires some manual intervention, which will be asked again and again until completed. To get rid of this message you can: * follow the instructions, it worked fine for me * remove the sun-java[56]-doc package If these actions fail, then a bug is present. Then please provide a more detailled description. The zip file could perhaps be downloaded directly without asking (like it is done for the flash plugin), but I guess that this would break sun's license or something. Maybe, launching a browser at the right page would make things much easier for the average user, but saving the file at the right place and giving it to the root user would still require some work. -- apt-get: missing/wrong package in repository https://launchpad.net/bugs/84437 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84859] sun-java[56] on PPC
Public bug reported: I know that sun does not support linux-ppc. But some of the "sun- java[56]-*" packages are available (but not installable) on PPC, which may give some false hope to the users. Would it be possible to distribute packages of the IBM java for the PPC architecture ? I have been installing it manually for a while, but having a version ready inside ubuntu repository would make things so much easier... This might be too much to ask while support for PPC may get dropped soon, in this case, please at least do not include broken packages of sun's java. Maybe the ongoing opensourcing of sun's jdk will improve this quite a bit, does anyone have some extra informations on this ? Will it mean having the same JDK on every platform in the medium term ? ** Affects: sun-java6 (Ubuntu) Importance: Undecided Status: Unconfirmed -- sun-java[56] on PPC https://launchpad.net/bugs/84859 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
OK, here are the result of some more tests with mdadm_2.5.6-7ubuntu4: * my first boot went fine, allowing me to get your advice. * the second boot hanged, so I waited for a while. All my devices were here, both in /dev and in /proc/partitions The RAID array was assemble with 3 devices (out of 4) but not started (i.e. not degraded) running "/scripts/local-top/mdadm from udev" did not work, the screen was filled with error message: "mdadm: SET_ARRAY_INFO failed for /dev/md0: Device or ressource busy" I could stop it only using the sysreq, which took me back to the initramfs shell, with the raid array completely stopped. There running the same command again assembled the array correctly. [off topic] I could not leave the shell and continue booting, It took me back to this shell every time, saying: "can't access tty; job control turned off" [/off topic] * The third boot hanged also. The array was assembled with one drive only (thus it could not even have started in degraded mode). I tried running "mdadm -S /dev/md0" before doing anything else. After this, running "/scripts/local-top/mdadm from-udev" assembled the array properly [off topic] But I still could not continue the boot. The next 4 boot did also hang (but I did not wait). Then it accepted to boot again [/off topic] -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83642] Re: fancy isolinux screen on install isos hang xen/kvm HVM guests
I can confirm this bug. Running the desktop-cd with qemu (or without loading kvm-intel module) seems to work but is damn slow. X seems to run inside kvm without a problem, only the early "bling" fails. -- fancy isolinux screen on install isos hang xen/kvm HVM guests https://launchpad.net/bugs/83642 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83013] Re: (Feisty) NetworkManager makes system unusable, seems to have problem with dbus
*** This bug is a duplicate of bug 78255 *** ** This bug has been marked a duplicate of bug 78255 [feisty] rtl8180 oops -- (Feisty) NetworkManager makes system unusable, seems to have problem with dbus https://launchpad.net/bugs/83013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82956] Re: gnome-main-menu only retains 6 favorite applications
A new package in feisty uses a new SVN checkout and fixes the problem. Shoult I mark it as "fix released" or not ? (it also affects edgy) -- gnome-main-menu only retains 6 favorite applications https://launchpad.net/bugs/82956 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85118] epiphany launch error: Unable to connect to session bus
Public bug reported: Binary package hint: epiphany-browser [using epiphany 2.17.91 in feisty. It happened with older versions in feisty, but not in edgy and older versions] When I boot the system and log in, I can launch epiphany without a problem, but if I logoff, and then log back in, epiphany refuses to start: ** (epiphany:9785): WARNING **: Unable to connect to session bus: Failed to connect to socket /tmp/dbus-9sJiuXWgBI: Connection refused I can log off, remove all my files in /tmp using the console to fix the problem. dbus-launch epiphany also works. ProblemType: Bug Date: Wed Feb 14 15:30:10 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/epiphany Package: epiphany-browser 2.17.91-0ubuntu1 ProcCmdline: epiphany ProcCwd: /tmp ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=fr_FR.UTF-8 LANGUAGE=fr_FR.UTF-8 SourcePackage: epiphany-browser Uname: Linux gin-g5 2.6.20-6-powerpc64-smp #3 SMP Wed Jan 31 19:43:02 UTC 2007 ppc64 GNU/Linux ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: Unconfirmed -- epiphany launch error: Unable to connect to session bus https://launchpad.net/bugs/85118 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85118] Re: epiphany launch error: Unable to connect to session bus
** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6438130/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6438131/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6438132/ProcStatus.txt -- epiphany launch error: Unable to connect to session bus https://launchpad.net/bugs/85118 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
With the --no-degraded option that has been added, it IS harmless for the array itself, but it can still block the boot. If an array has been assembled too early, it should be stopped (running "mdadm -S /dev/md0" by hand worked for me) BEFORE trying to assemble it again, an other race may be present here ? mdadm can tell if a device is part of an array, this could be used to check that all devices are present before assembling it, but would slow things down or require some memory. If a device is really missing (shit happens...), the array should then be assembled in degraded mode. This should probably happen automatically (or with a confirmation) after the timeout, or by adding a boot option. -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: initramfs script: race condition between sata and md
Perhaps is it another bug on my particular system... I have written about it in previous comments, when trying to assemble /dev/md0 I have three different results: * all devices of the array are available: /dev/md0 is created and working * a device is missing (and --no-degraded is _not_ specified): /dev/md0 is created and working in degraded mode * several devices are missing (or only one with --no-degraded): /dev/md0 is still created but _not_ working. I get a message like "too many missing devices, not starting the array", but it still appears in /proc/mdstat (not running but present, it may not be completely assembled but it is here!). I can not assemble it until it has been fully stopped using "mdadm -S /dev/md0" This looks weird, and I had not seen this before, but I had not tryed to launch the array with 2 missing drives... -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73345] Re: X crashes when using Xv or fullscreen-SDL with binary nvidia driver
Indeed, the newer version in feisty works fine. Sorry for not testing earlier: I was using a hand-installed drivers in the meantime. -- X crashes when using Xv or fullscreen-SDL with binary nvidia driver https://launchpad.net/bugs/73345 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74050] Re: tomboy in kubuntu (kde): the applet not visible in the main panel
I have the same behaviour running gnome on edgy, both on PPC and i386. Using the panel applet works fine. Maybe an icon is missing somewhere ? I straced it and have not found anything in the trace, all references to "png" correspond to the lookup for libpng. It does not seems to try to load its icon at all ! -- tomboy in kubuntu (kde): the applet not visible in the main panel https://launchpad.net/bugs/74050 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75052] [feisty] non-working initramfs: failed to activate RAID
Public bug reported: Binary package hint: initramfs-tools I have just upgraded my system to feisty and it can not boot on the new kernel. My old kernels are still fine. After some checking, it looks like the mdadm script into the initramfs are not functionnal. By adding the "break=mount" kernel option I got a shell in the initramfs, where I get the error: "mdadm: ' not identified in config file" the config file looks fine, even the one in the initramfs, only /dev/md0 is defined. running the RAID by hand works fine. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- [feisty] non-working initramfs: failed to activate RAID https://launchpad.net/bugs/75052 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75052] Re: [feisty] non-working initramfs: failed to activate RAID
The above error is fixed: I had edited my /etc/mdadm/mdadm.conf and put a space at the end of the HOMEHOST line. I replaced my config file by the one generated by mkconf, it solves this problem but still does not boot. The new error message is: "mdadm: no devices listed in conf fil were found" The weird thing is that simply running /script/local-top/mdadm by hand works! -- [feisty] non-working initramfs: failed to activate RAID https://launchpad.net/bugs/75052 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77737] Re: 2.6.20-* fails to boot in Feisty
*** This bug is a duplicate of bug 75681 *** ** This bug has been marked a duplicate of bug 75681 initramfs script: race condition between sata and md -- 2.6.20-* fails to boot in Feisty https://launchpad.net/bugs/77737 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77722] [feisty] SATA errors with 2.6.20, freezes
Public bug reported: Binary package hint: linux-image-2.6-amd64-generic Upgrading to kernel 2.6.20 in feisty introduced many errors and freezes on my AMD64 install (I also have a x86 install but I'm not yet ready to upgrade it to feisty so I can not tell if it is AMD64 specific yet). These errors are not present with 2.6.19 and appears with both 2.6.20-2-generic and 2.6.20-3-generic. I have a nforce4 motherboard, on which are plugged 4 sata hard drives, in RAID5 (and an IDE CD-writer). The errors (visible at the end of the attached dmesg output) seems to hit only the last hard drives which get reseted now and then, leading to system freezes during a few (up to 30) seconds. I used to have the nvidia driver loaded but I am now running a clean kernel and the errors are still here. I can test on a 32bit install on the same system once Bug #75052 is fixed, until then I prefer keeping a booting system out of two :) ---dmesg output [0.00] Linux version 2.6.20-3-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 20061212 (prerelease) (Ubuntu 4.1.1-21ubuntu3)) #2 SMP Tue Dec 26 02:36:13 UTC 2006 (Ubuntu 2.6.20-3.4-generic) [0.00] Command line: root=/dev/mapper/vg_raid-lv_memroot64 ro quiet break=mount [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f800 (usable) [0.00] BIOS-e820: 0009f800 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3fff (usable) [0.00] BIOS-e820: 3fff - 3fff3000 (ACPI NVS) [0.00] BIOS-e820: 3fff3000 - 4000 (ACPI data) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fee0 - fef0 (reserved) [0.00] BIOS-e820: fefffc00 - ff00 (reserved) [0.00] BIOS-e820: - 0001 (reserved) [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] Entering add_active_range(0, 256, 262128) 1 entries of 3200 used [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP (v000 Nvidia) @ 0x000f8fc0 [0.00] ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff3040 [0.00] ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff30c0 [0.00] ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff95c0 [0.00] ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff9500 [0.00] ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x [0.00] Scanning NUMA topology in Northbridge 24 [0.00] Number of nodes 1 [0.00] Node 0 MemBase Limit 3fff [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] Entering add_active_range(0, 256, 262128) 1 entries of 3200 used [0.00] NUMA: Using 63 for the hash shift. [0.00] Using node hash shift of 63 [0.00] Bootmem setup node 0 -3fff [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 262128 [0.00] On node 0 totalpages: 262031 [0.00] DMA zone: 56 pages used for memmap [0.00] DMA zone: 1071 pages reserved [0.00] DMA zone: 2872 pages, LIFO batch:0 [0.00] DMA32 zone: 3527 pages used for memmap [0.00] DMA32 zone: 254505 pages, LIFO batch:31 [0.00] Normal zone: 0 pages used for memmap [0.00] Nvidia board detected. Ignoring ACPI timer override. [0.00] If you got timer trouble try acpi_use_timer_override [0.00] ACPI: PM-Timer IO Port: 0x4008 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: BIOS IRQ0 pin2 override ignored. [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) [
[Bug 75052] Re: [feisty] non-working initramfs: failed to activate RAID
*** This bug is a duplicate of bug 75681 *** ** This bug has been marked a duplicate of bug 75681 initramfs script: race condition between sata and md -- [feisty] non-working initramfs: failed to activate RAID https://launchpad.net/bugs/75052 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74050] Re: tomboy in kubuntu (kde): the applet not visible in the main panel
This is fixed in feisty and the feisty package works fine on edgy (and the latest tomboy rocks even more) -- tomboy in kubuntu (kde): the applet not visible in the main panel https://launchpad.net/bugs/74050 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40537] Re: Openoffice.org2 cannot write to NFS files
I can confirm this on ubuntu edgy (on both the nfs server and client). Launching openoffice on a NFS-mounted home directory took forever. Installing nfs-common solved this problem (and many other performance- related problems). BUT even with nfs-common, openoffice has some remaining problems, like crash on exit and random errors while saving. I am running it through "ssh -X" for now but other might not have/want openoffice on their nfs- server! -- Openoffice.org2 cannot write to NFS files https://launchpad.net/bugs/40537 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77009] Re: failed deps on iceweasel | iceape-browser | icedove
Would it not be much easier to add a proper "provides ice---" to firefox/thunderbird ? -- failed deps on iceweasel | iceape-browser | icedove https://launchpad.net/bugs/77009 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81578] Re: 0.3.2 crashes
It is not a driver issue: the exception is a "System.DllNotFoundException" probably a missing lib, but I could not found any kind of "libgl-cil" or "libgtkglext1-cil" :/ Note: happens to me on PPC with the ati Xorg driver. f-spot 0.31 or 0.32 introduces a new OpenGL view, the ubuntu package have probably not been updated for it. Either a depend is missing or some files have not been added to the package. -- 0.3.2 crashes https://launchpad.net/bugs/81578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81578] Re: 0.3.2 crashes
Oups, I should have read the upstream bug first. adding to /usr/lib/f-spot/f-spot.exe.config solved it for me. -- 0.3.2 crashes https://launchpad.net/bugs/81578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
