This affects me too in exactly the same way.
Based on my digging, there are more than a few people experiencing this
particular combination of issues after the 13.10 upgrade (NM issues,
User Account management "unlock" is greyed out, drive
mounting/unmounting issues, shutdown/reboot issues).
I've
This issue isn't isolated to fglrx. See #16 and #18.
# ubuntu-drivers list
virtualbox-guest-dkms
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1222718/+attachment/3889849/+files/Xorg.0.log
--
You received this bug notification because you
Unfortunately, being able to relocate home directories is very typical
on *nix systems from my experience. The best possible case would be to
somehow search /etc/passwd for home directories and only allow it to run
out of those on a per-user basis. This isn't necessarily relevant to
Empathy or Te
I believe this is a problem with AppArmor in 12.04. I've been using
this same setup for a while now, so I don't think it affects previous
versions.
In /etc/apparmor.d/tunables/home, HOME is rigidly defined as "/home/".
I put home in /u01/home, it meant that the apparmor profile for
Telepathy was
Dump *will* now make dumps of an ext4 without complaining using dump
v0.4b41-6 (Jaunty)
Unfortunately, restoring the data shows that it's been corrupted
somewhere in the process (either dump or restore). The data doesn't
even remotely resemble the original.
100% reproducibility. Steps to reprod
This fixes the issue for me as well. I can switch between pointstick,
touchpad and Synergy without any obvious issues.
--
cursor with synergyc client is stuck in upper left corner
https://bugs.launchpad.net/bugs/321444
You received this bug notification because you are a member of Ubuntu
Bugs, w
This also affects me.
I have an HP Elitebook 8530w with both a touchpad and a joystick
(pointstick). I found that if I move the joystick Synergy will start
working as expected. If I use the touchpad, Synergy stops working and
reverts to being stuck in the upper left corner. If I kill/restart
syn
My earlier statement that Jaunty/Jaunty works correctly is incorrect.
On my laptop (HP Elitebook 8530w), I have a Synaptics touchpad as well
as a joystick.
If I touch the joystick *at all* Synergy will start working as expected.
I must have bumped the joystick during my last test.
This appears th
I had the same problem with:
Server: 1.3.1-4ubuntu2 (intrepid) (i386)
Client: 1.3.1-5ubuntu1 (jaunty) (x86_64)
I also tried it with 1.3.1-5ubuntu1 on both systems and 1.3.1-4ubuntu2
on both systems, with no change.
I upgraded the server to Jaunty, which means I'm currently running:
Server: 1.3
Bryce,
Interestingly, I just upgraded to intrepid last night to get around the
annoying intrepid->nx->hardy keyboard mapping bug (reported by someone
else already), so I was in a good place to test this tonight.
The updates installed fine, the fglrx-installer (via
System->Administration->Hardware
Alberto,
In this case EnvyNG yields a broken installation because when Compiz
loads (i.e., it uses 3D effects), you get a white screen instead of the
expected 3D effects.
After some digging, I found this to be because the fglrx kernel module
isn't loading. The reason the kernel module isn't load
I tried this back around 7/15.
Unfortunately, the EnvyNG installer results in a broken installation.
Based on my limited diagnosis, the kernel module won't load because
there's no device stanza in xorg.conf which contains "fglrx". Because
the kernel module isn't loaded, I wind up with a white sc
My original system was a 32-bit Hardy running on 64-bit capable
hardware, upgraded from Gutsy.
I did a fresh 32-bit install of Hardy, fully updated -- no change.
I did a fresh 64-bit install of Hardy, fully updated -- no change.
I read something somewhere recently about people running 32 bit OS o
It looks like that might not be a good comparison:
1) AGP vs PCIe
2) 32-bit vs 64-bit
Unless those two things matter less than they appear to.
--
[fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow
system
https://bugs.launchpad.net/bugs/206337
You received this bug n
It should also be noted that I found a new version of the netboot
installer had been released. All of the above tests were performed
booted from http://us.archive.ubuntu.com/ubuntu/dists/hardy/main
/installer-sparc/20070308ubuntu39/images/sparc64/netboot/2.6/boot.img
--
Installer/wget is unable
This test is with the apt-cacher server still running on port
~ # wget http://apt-proxy.company.com:/ubuntu//dists/hardy/Release -O -
wget: no response from server
~ # wget http://apt-proxy.company.com:8738/ubuntu//dists/hardy/Release -O -
wget: Unable to
There's no change. If anything, my system seems less responsive than
before. The excessive interrupts are still occurring. AIGLX was
disabled, as /var/log/Xorg.?.log went from:
$ fgrep AIGLX /var/log/Xorg.1.log
(==) AIGLX enabled
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGL
I should add that it appears that the system referenced above is
otherwise functional. Top reports the system is constantly 60% busy in
"%hi" when X is on the active console. The remainder of the system
feels like it's 60% or busier, like it's running a 500mhz Celeron
instead of the actual 2.8ghz
** Attachment added: "version_signature.log"
http://launchpadlibrarian.net/12850111/version_signature.log
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubun
** Attachment added: "uname.log"
http://launchpadlibrarian.net/12850105/uname.log
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "interrupts.log"
http://launchpadlibrarian.net/12850103/interrupts.log
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/12850100/dmesg.log
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/12850094/xorg.conf
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/12850088/lspci-vvnn.log
--
Using fglrx causes excessive hardware interrupts and an extremely slow system
https://bugs.launchpad.net/bugs/206337
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On an up-to-date Hardy install, when I enable the FGLRX driver using the
restricted drivers manager and reboot, either X or FGLRX cause an
excessive number of hardware interrupts on my system whenever it's the
active console:
[EMAIL PROTECTED]:~$ vmstat 1
procs ---mem
I noticed an omission in that last bit (should have waited to
cut-n-paste instead of manually making the changes):
partition=1
root=/dev/md0
timeout=20
image=/boot/vmlinuz
label=Linux
read-only
initrd=/boot/initrd.img
image=/boot/vmlinuz.old
label=LinuxOLD
Since my report (bug 203947) has been marked a duplicate of this one, I
thought I'd chime in:
I netbooted, chrooted into my mostly installed system and performed the
following:
apt-get --purge remove silo
then:
[EMAIL PROTECTED]:/# apt-get install silo
** Attachment removed: "syslog"
http://launchpadlibrarian.net/12739492/syslog
** Attachment added: "syslog"
http://launchpadlibrarian.net/12739551/syslog
--
Installer hangs trying to install SILO boot loader
https://bugs.launchpad.net/bugs/203947
You received this bug notification becaus
** Attachment added: "syslog"
http://launchpadlibrarian.net/12739492/syslog
--
Installer hangs trying to install SILO boot loader
https://bugs.launchpad.net/bugs/203947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: debian-installer
Steps to reproduce:
1) Do a network install using
http://us.archive.ubuntu.com/ubuntu/dists/hardy/main/installer-sparc/20070308ubuntu33/images/sparc64/netboot/2.6/boot.img
2) "Go Back" at an appropriate point and Switch to "low" priorit
This appears to resolve my issue. I was able to get past partitioning
and RAID configuration on a system with the original partition layout:
IDE1 master (hda) - 20.0 GB ST320413A
> #1 8.2 MB ("do not use")
> #2 641.6 MB K raid
> #4 4.1 GB K raid
> #5 510.0 MB K raid
> #6 3.1 GB K raid
> #7 5.1 G
By default, apt-cacher can also be accessed via Apache2 (if you have it
installed).
As a workaround, you can set the mirror to:
"apt-cacher.company.com" and "/apt-cacher/ubuntu"
Although I didn't used to have to do this with Gutsy and prior.
--
Installer/wget is unable to retrieve files via a
Performing:
chmod ugo+x /lib/partman/choose_method/70dont_use/choices
gets rid of the "Permission denied" problem, but doesn't seem to fix the
original problem. I've poked around a bit but am still unclear as to
why it's even attempting to mount the unconfigured RAID components.
--
Configure p
Somehow I over looked this in the syslog:
Mar 4 15:21:39 main-menu[5516]: (process:5580):
/lib/partman/choose_method/70dont_use/choices: Permission denied
Mar 4 15:21:39 main-menu[5516]: (process:5580):
Mar 4 15:21:39 main-menu[5516]: (process:5580):
/lib/partman/active_partition/15method/
Unfortunately, no improvement.
The only difference I can identify is that I can no longer mark
partition 1 as "Do Not Use". I'm using this partition layout, which is
similar to one I've tried above.
IDE1 master (hda) - 20.0 GB ST320413A
> #1 8.2 MB F ext3
> #2 641.6 MB K raid
>
Public bug reported:
Binary package hint: debian-installer
Installer is unable to retrieve files from apt-proxy/apt-cacher style
proxies using "hostname:port", despite the fact that the dialogs say
that it's valid.
1) Netbooted from
/ubuntu/hardy/main/installer-sparc/20070308ubuntu31/images/spa
And in case you're wondering, the reason I leave /dev/hda1 and /dev/hdc1
unconfigured is due to the fact that RAID volumes will overwrite the Sun
disklabel.
This configuration appears to work:
IDE1 master (hda) - 20.0 GB ST320413A
> #1 131.6 MB f ext3 /boot
> #2 510.0 MB f ext3
This (valid) partition layout also has problems:
IDE1 master (hda) - 20.0 GB ST320413A
> #1 8.2 MB
> #2 641.6 MB f ext3 /
> #4 4.1 GB f ext3 /usr
> #5 510.0 MB f ext3 /tmp
> #6 3.1 GB f swap swap
> #7 5.1 GB f ext3 /var
I did a "save debug logs" from the main menu. I found the following
interesting:
Mar 3 18:51:03 main-menu[27682]: (process:4769): mount:
Mar 3 18:51:03 main-menu[27682]: (process:4769): Mounting /dev/hda1 on
/mnt/tmpmount failed
Mar 3 18:51:03 main-menu[27682]: (process:4769): : Invalid ar
** Attachment added: "hardware-summary"
http://launchpadlibrarian.net/12370210/hardware-summary
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
Configure partitions for RAID1, received: The installer needs to remove
operating system files from the i
** Attachment added: "partman"
http://launchpadlibrarian.net/12370206/partman
--
Configure partitions for RAID1, received: The installer needs to remove
operating system files from the install target, but was unable to do so.
https://bugs.launchpad.net/bugs/198106
You received this bug noti
I think this may actually be a debian-installer problem, but I'll leave
it up to the experts to decide.
--
Configure partitions for RAID1, received: The installer needs to remove
operating system files from the install target, but was unable to do so.
https://bugs.launchpad.net/bugs/198106
You r
Public bug reported:
Binary package hint: ubiquity
1) Netbooted my Netra X1 from
/ubuntu/hardy/main/installer-sparc/20070308ubuntu31/images/sparc64/netboot/2.6/boot.img
2) configured my two internal drives as follows:
IDE1 master (hda) - 20.0 GB ST320413A
> #1 8.2 MB
> #2 641.6 MB
Hardy works for me running a netinstall with kernel 2.6.24-10-sparc64.
I'll report back if it doesn't work after the installation is complete.
--
Possible fake host protected area (hpa) detected in ide drive causing
SectorIdNotFound
https://bugs.launchpad.net/bugs/26119
You received this bug not
I was experiencing the same problem, so I installed Daniel Haler's PPA
version and about two weeks ago. It cured my immediate ills and had
been running ever since without problems.
Last night, I installed the version released into gutsy-proposed. My
initial impression is that it also seems to fi
This appears to have been resolved with kernel linux-
image-2.6.22-13-sparc64 (2.6.22-13.40) and boot image 20070308ubuntu17
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Fix Released
--
Sparc hangs on "Booting Linux" on Gutsy
https://bugs.launchpad.net/bugs/141526
You receiv
Public bug reported:
Binary package hint: linux-source-2.6.22
I have a Sun Netra X1 that I wanted to test Gutsy on. When booting, it
gets as far as "Booting Linux" and fails to continue to boot regardless
of how long I wait -- I left it sitting like this overnight last night.
Since this seems to
I had the exact same problem yesterday. Ultimately, I found that the
following workaround got my system to reboot correctly:
1) load the eata module from the busybox shell and wait 10s
2) exit from the shell and log in once the system has loaded
3) echo eata >> /etc/initramfs-tools/modules
4) ech
The problem is still occurring in Feisty.
--
Possible fake host protected area (hpa) detected in ide drive causing
SectorIdNotFound
https://bugs.launchpad.net/bugs/26119
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
Yes. The bug is present in Edgy.. I haven't tried upgrading to Feisty
yet.
I created a raid array:
mdadm --create -l5 -n 14 /dev/md10 /dev/sd[bcdfghijklqrst]1
Added it to /etc/mdadm/mdadm.conf:
[EMAIL PROTECTED]:/# cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-dev
This appears to have resolved my problem also.
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https:
I tried adding "/sbin/udevsettle --timeout=10" to the bottom of
/usr/share/initramfs-tools/scripts/init-premount/udev, rebuilt my
initrd, and it does seem to work on my system just as reliably as the
"sleep 10" method.
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/10
Clarification -- two comments up, in the "let it fail" scenario,
"nothing is ever discovered" should read:
/dev/sda*, /dev/sdb*, /dev/hda* /dev/hdc* are never discovered
regardless how long I wait. /dev/md1 does exist at this point.
--
boot-time race condition initializing md
https://bugs.launc
Correction -- after booting in the "break=mount" scenario my ATA (not
SATA) drives are still identified as /dev/sda and /dev/sdb according to
/proc/mdstat:
[EMAIL PROTECTED]:~# cat /proc/mdstat
Personalities : [raid1]
...
md1 : active raid1 sda5[0] sdb5[1]
497856 blocks [2/2] [UU]
The sam
My experience mirrors (pun intended) Jeff250's.
If I boot with break=mount, and remove "quiet splash", it drops to the
shell, and about a second later, it discovers everything properly. At
that point, I can exit the shell and the boot process will continue
normally.
If I don't boot with break=mo
Confirmed working for me -- my bug was marked as one of the dupes of
this one.
--
MASTER: Request for new-legacy nvidia drivers (9631)
https://bugs.launchpad.net/bugs/96430
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
I decided to include this, since it also seems to control how and which
arrays are started up at boot.
** Attachment added: "/etc/default/mdadm"
http://librarian.launchpad.net/7220924/mdadm
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bu
** Attachment added: "/etc/mdadm/mdadm.conf"
http://librarian.launchpad.net/7220921/mdadm.conf
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
ps.log
** Attachment added: "ps.log from initial busybox"
http://librarian.launchpad.net/7220912/ps.log
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
This photo is about two minutes after the first one, with "ls -al
/dev/hda* /dev/hdc* /dev/md*" and "cat /proc/mdstat"
** Attachment added: "Photo two minutes after it drops to shell, with
additional information."
http://librarian.launchpad.net/7220873/mvc-144x.jpg
--
boot-time race conditio
Sorry for the delay. We went away for the weekend. Attached is the
requested information.
The first one is a photo when it first drops to the busybox shell.
** Attachment added: "Photo right after it drops to the busybox shell"
http://librarian.launchpad.net/7220867/mvc-143x.jpg
--
boot-ti
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
All,
Please read this comment in another bug by Scott James Remnant.
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/83231/comments/25
This policy isn't clearly displayed anywhere obvious, they apparently
want us all to open separate bugs for them to investigate, and they will
de
Here are the versions of the related packages currently installed on my
system:
dmsetup 1.02.08-1ubuntu10
libdevmapper1.02 1.02.08-1ubuntu10
libvolume-id0108-0ubuntu3
lvm-common
lvm2
This isn't fixed for me. I opened a new report (Bug # 103177) as
requested by Scott James Remnant.
My problem still has the exact same symptoms that I described above.
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/75681
You received this bug notification because yo
Public bug reported:
Binary package hint: mdadm
I originally contributed some feedback to Bug #75681. It is currently
reported as being fixed, but my problem still persists. The person that
closed it recommended that we open new bugs if we're still having
problems. I've reproduced my feedback
I did a little research here:
http://www.nvidia.com/object/unix.html
And it turns out that the 1.0-9755 binary driver no longer supports the
"ti 4400", whereas the 1.0-9633 binary driver does.
So, it looks like X has a legitimate complaint there. However, that
still leaves all of my other point
Public bug reported:
Binary package hint: xorg
I had a working xorg/compiz/nvidia-glx configuration working properly
prior to updates this evening. Among other things, I updated the
following (and their related packages):
compiz 1:0.3.6-1ubuntu8(old) 1:0.3.6-1ubuntu10(new)
xserver-xorg 1:7.2-0ub
I confirm that my earlier report about the Sparcs I'm using have the
same problem in Edgy too. I reported it in slightly more detail in Bug
# 49265
--
Possible fake host protected area (hpa) detected in ide drive causing
SectorIdNotFound
https://launchpad.net/bugs/26119
--
ubuntu-bugs mailing
I probably should have included a bit more of the dmesg output. Here is
where it's the same. The above section immediately preceded this:
[ 38.303408] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 38.399361] hda: task_in_intr: error=0x10 { SectorIdNotFound }
Rouben:
I can't confirm whether this is actually a duplicate of 26119, but it
sounds virtually identical. The problem is only with particular drives.
The Seagate ST320413A referenced below causes it, but neither a Seagate
ST320420A nor a Western Digital "WDC WD400EB-00CPF0" do.
Paolo:
Assuming
FWIW, I have the problem, exactly as described, with a IDE-only system.
I attempted this with both an Edgy->Feisty upgrade (mid Februrary), and
a fresh install of Herd5.
I'm running straight RAID1 for all my volumes:
md0 -> hda1/hdc1 -> /boot
md1 -> hda5/hdc5 -> /
md2 -> hda6/hdc6 -> /usr
md3 ->
I can confirm the same with Herd3.
>From my diagnosis, it appears that /dev/md? are missing or not generated
properly in the initramfs.
In the busybox shell, I proceeded to do:
mknod /dev/md0 b 9 0
mknod /dev/md1 b 9 1
etc..
mdadm --run /dev/md0 /dev/hda1 /dev/hdc1
mdadm --run /dev/md1 /dev/hda5
Try this. Start Firefox from a command prompt:
LD_PRELOAD=/usr/lib/libXt.so.6 /usr/lib/firefox/firefox
That should temporarily fix the problem until you exit firefox. The
problem appears to be that nppdf.so expects that libXt.so to already be
loaded, which is bad practice.
A hack that will wor
Try this:
LD_PRELOAD=/usr/lib/libXt.so.6 /usr/lib/firefox/firefox
That will probably, but temporarily fix the problem. The problem
appears to be that nppdf.so expects that libXt.so to already be loaded.
A hack that will work around the problem (but load more, possibly
unnecessary libraries, dep
To work around this bug, I put the following in
/etc/default/mailscanner:
[ ! -d /var/run/MailScanner ] && mkdir /var/run/MailScanner && chown
postfix:postfix /var/run/MailScanner
[ ! -d /var/lock/subsys/MailScanner ] && mkdir -p /var/lock/subsys/MailScanner
&& chown postfix:postfix /var/lock/su
The dmfe module isn't available in the sparc64 port:
kite:~# find /lib/modules/2.6.15-25-sparc64 -iname "*dmfe*" -o -iname "*tulip*"
/lib/modules/2.6.15-25-sparc64/kernel/drivers/net/tulip
/lib/modules/2.6.15-25-sparc64/kernel/drivers/net/tulip/tulip.ko
kite:~#
** Changed in: linux-source-2.6.15
Public bug reported:
Support for the NICs in my system was removed between 2.6.15-23 and
2.6.15-25.
My Devices (via 'lspci -v'):
:00:05.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
Flags: bus master, medium devsel, latency 16
This may possibly be an madm/mdrun problem, but I haven't had a chance
to investigate whether it's the local-top/md script that's causing it,
or if it's mdrun.
--
initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
https://launchpad.net/bugs/49914
--
ubuntu-bugs mailing list
Public bug reported:
On a Sun e420 during the install, I created my volumes as follows:
/dev/sda1 /boot
/dev/md0 /home (/dev/sd[ab]8)
/dev/md1 / (/dev/sd[ab]2)
/dev/md2 /usr (/dev/sd[ab]4)
/dev/md3 swap (/dev/sd[ab]5)
/dev/md4 /tmp (/dev/sd[ab]6)
/dev/md5 /var (/dev/sd[ab]7)
and completed the i
It looks to me like you've been bitten by this bug:
https://launchpad.net/distros/ubuntu/+source/linux-
source-2.6.15/+bug/26119/+index
If you do a 'hdparm /dev/hda' you should also likely notice that
"using_dma = 0 (off)". That seems to be the other symptom of this
problem.
--
Intel 440BX: 'h
81 matches
Mail list logo
