On the same hardware, Fedora 17 does not have these problems.
I'll keep the ubuntu install to test proposed fixes or the next version, but I
guess I'll start using fedora for real...
Note that Ubuntu 12.04 works fine for me on other computers (intel
integrated graphics)
--
You received this bug
** Attachment added: "screenshot, taken with scrot"
https://bugs.launchpad.net/bugs/1000162/+attachment/3148812/+files/corrupt2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000162
Title:
g
Public bug reported:
I have many display corruption since I upgraded my system to 12.04 (11.10 was
working fine).
The computer is a dell precision T1500 with a radeon graphic card (firepro 2260
according to lspci).
I had some old settings in xorg.conf, removing the file completely did not
solve
two finger scrolling and other multitouch stuff requires some user-land
support, it does not work out of the box in natty either.
You will have to backport ginn [1] as well to support "legacy" applications
[1] https://launchpad.net/canonical-multitouch/ginn
--
You received this bug notification
it is now working in natty
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645530
Title:
magic trackpad not worki
*** This bug is a duplicate of bug 580430 ***
https://bugs.launchpad.net/bugs/580430
** This bug has been marked a duplicate of bug 580430
package enna-theme (not installed) failed to install/upgrade: tentative de
remplacement de « /usr/share/enna/theme/default.edj », qui appartient aussi
yes, I followed these instructions (and also installed the whole utouch
package).
I get the same behaviour (and log) with or without the xorg.conf section which
is the only text in my xorg.conf as the file didn't exist at all.
--
magic trackpad not working with evdev
https://bugs.launchpad.net/
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/645530/+attachment/1624196/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/645530/+attachment/1624197/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
I was eager to test the new support for multitouch devices so I got a magic
trackpad. Beside the association only working on command line it worked out of
the box but in basic mode: it moves the cursor and the physical click wor
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/52020510/Dependencies.txt
--
apparmor profile for dhcp3-client is too strict
https://bugs.launchpad.net/bugs/606163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
on a up to date maverick AMD64 install, dhclient stopped working: I
didn't touch apparmor or dhclient configuration and it worked well 2
days ago. The process get killed as shown by strace:
execve("/sbin/dhclient", ["dhclient", "eth0"], [/* 21 vars */]) = 0
brk(0)
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49130268/Dependencies.txt
--
pgfimage does not work
https://bugs.launchpad.net/bugs/585801
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: pgf
inserting an image using the pgf commands (pgfimage or pgfdeclareimage +
pgfuseimage) does not work (using pdflatex and a pdfimage): an empty box is
inserted instead.
Surprisingly, providing a non-existant path leads to the same result.
The same ima
Public bug reported:
Binary package hint: gnome-panel
disclaimer: it is a weird bug and I am not sure gnome-panel really is
the culprit here.
On one of my 3 computers running lucid, I have a weird behavior which I first
thought was due to compiz. It starts a while after login, usually as soon a
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49075724/Dependencies.txt
--
missing shebang in pdfcrop (and other texlive-related scripts)
https://bugs.launchpad.net/bugs/585394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
A while ago, I wrote a simple python script calling pdftk and pdfcrop to
prepare figures for inclusion in latex files.
If I recall properly, I used it at least on the last two ubuntu versions
(jaunty and karmic), but I just launched it again on lucid and it was broken,
comp
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/43329954/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43329955/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/43329956/Card0.Amixer.valu
Public bug reported:
Unexpected good news for me: the nouveau kernel module was enabled on PPC in
2.6.32-19.
Unfortunately, the display now turns off early in boot (before X launches) and
the screens complains about the lack of input then about input being out of
range.
I tried without success
it was renamed to -pae, not much of a problem once we know it...
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
[karmic] no more -server kernel for 32bit systems ?
https://bugs.launchpad.net/bugs/439667
You received this bug notification because you are a member of Ubuntu
Bugs, w
I also noticed this when usplash was removed. It is ugly and indeed a
regression from the usplah era but I didn't care... until fsck was
triggered.
With usplash we had progress status ans a "skip" option. Now we are back
to a cryptic text message without and a system which seems stuck as the
old t
** Attachment added: "exemple to reproduce it. newfile1 is the master document"
http://launchpadlibrarian.net/32762900/lyx_language_bug.tar.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32762901/Dependencies.txt
--
included document switches language of master d
Public bug reported:
Binary package hint: lyx
I'm currently writing my PhD thesis with lyx. We have to write it in french but
with an abstract in english.
After adding this abstract as a sub-document, the language of the rest of the
thesis switched to english.
It seems to be connected with the
Public bug reported:
I have a few systems with 4Go (or more) of RAM. For some of them, I use
the -server kernel on a 32bit install. This kernel is not available in
karmic (it is listed for amd64 but my amd64 system is not yet on
karmic).
The -generic kernel doesn't see more than 3Go of RAM, do we
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
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
** 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
** A
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
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
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 pr
*** 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-manag
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).
** 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.
--
ubu
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
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
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 inc
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~git
** 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.
--
ub
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 wh
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 \
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 a
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: Erro
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
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/b
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 Ubunt
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 bu
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 w
** 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
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.
The
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 mailin
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
** 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 c
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 becaus
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 mailin
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
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 "unloc
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 U
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
*** 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 presentatio
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 PROTECT
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
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
Bu
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)
S
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 aga
** 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.
--
ubunt
o 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
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
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 ver
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:
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 startab
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 hel
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
ubu
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
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 s
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
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
h
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)
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 prese
** 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
--
epipha
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, epiphan
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://lis
*** 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
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/83
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)
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
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
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 ?
>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
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
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 assembl
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 v
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
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 d
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 br
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
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 solve
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
It looks like a race condition is still here: the initramfs tryes to
assemble my RAID upon detection of /dev/sda. Obviously with 3 drives
missing out of 4, it fails... Then, /dev/md0 is not here but inactive
and not correctly created when the other drives are detected.
Is it possible to get and ud
In feisty, I can see some initrd-[...].bak files, which looks fine. Except it
is clearly not working properly :/
When updating the initramfs is regenerated _many_ times: once for the kernel,
once for udev, lvm, mdadm, initramfs-tools...
If the first one fails, it keeps the old working one as back
Public bug reported:
Binary package hint: lvm2
running an up to date feisty, I can not boot on my RAID/LVM root partition. I
previously had bug #75681 which seems fixed now (/dev/md0 is created
automatically again) but the LVM volumes are not activated by the initramfs
anymore.
In the initramf
after a few days of use, still no problem. I marke it as fixed as no one
else was complaining/commenting.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Fix Released
--
[feisty] SATA errors with 2.6.20, freezes
https://launchpad.net/bugs/77722
--
ubuntu-bugs mailing
1 - 100 of 133 matches
Mail list logo
