[Bug 238259] Re: Building amd64 module for virtualbox-ose fails.

[José M . López-Cepero]

I can also confirm this.

I'm using kernel 2.6.24-21-generic, for which the virtualbox-ose modules
have not yet been compiled. When trying to use module-assistant I get
the same errors as the first poster (assembly-related messages). This
makes Virtualbox unusable in the 2.6.24-21 kernel.

As a temporary workaround, I was able to manually insert the module for
2.4.6-20-generic, which was still installed (since it is the latest
dependency of the virtualbox-ose-modules-generic package) and it seems
to work, by using the following command:

sudo insmod /lib/modules/2.6.24-20-generic/misc/vboxdrv.ko

dmesg reports success and the vbox machine seems to boot up and work OK.

-- 
Building amd64 module for virtualbox-ose fails.
https://bugs.launchpad.net/bugs/238259
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

@Lucas Gadani: Interesting. It seems that the special workaround you
removed, which, I presume, was made for a specific keyboard model,
breaks some others. Are you (or anybody else) aware of any way to
disable the 'quirks' mode without recompiling the kernel?

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

Seems to be a kernel problem as per Lucas Gadani report. I am reporting
it in the i386 package as it seems to be the closest available match
(the Launchpad interface is rather confusing), although I am seeing the
same problem here with amd64.

** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

Ignore the i386 bit above, I got the wrong text for the update. Sorry
for the bugspam

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 177856] Re: Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115

[José M . López-Cepero]

The Flash 64-bit is rather unstable on my system. Has anybody had any
success with Christopher's .deb file? It does not seem to contain the
binary...

-- 
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
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 177856] Re: Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115

[José M . López-Cepero]

Yes, I did uninstall everything, the only thing I did not do was copying
it to the global plugins dir (I left it at ~/.mozilla/plugins). I
checked that it was detected OK. Unfortunately, it would bring the
browser down every so often. With the stock nspluginwrapper, at least
the browser did not crash (just the Grey Box of Death). It might be a
case of a bad interaction with FlashBlock, but I did not get around to
try it.

I already built my own .deb file; it's a pity I redid the work :) It
seems to work for now with the 32-bit Flash plugin. When I have some
more time I'll keep experimenting.

Thanks for your reply!

-- 
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Hi there. @Tormod: What logs do you want, exactly? I did not see
anything helpful in any of them, but I'd be glad to upload any of them
you might need.

I am able to reliably reproduce the Xorg (alleged?) memory leak with
your desktop-changing line. I am also running compiz; interestingly,
however, I can't say the same as DoDoENT - if I kill compiz and change
the background, Xorg memory usage keeps on growing merrily.

I'm also using Xorg 1.5.2 on amd64.

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Ooops. I'm sorry. I did not notice Bryce's message. My fault.

I'm attaching all the requested files to this post. I think there is
nothing customized in my xorg.conf, but I'm attaching it just in case.
Also, there seems to be no specific output in the Xorg.0.log file after
the desktop is changed.

Thanks!

** Attachment added: "Xorg.0.log, xorg.conf and contents of lspci -vvnn"
   http://launchpadlibrarian.net/20083785/logfiles.zip

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 216939] Re: totem causes alt key press in openoffice every 30 seconds

[José M . López-Cepero]

Ubuntu Jaunty, AMD64, same issue. Please reopen.

Incidentally, to me this happens with me-tv, which uses the xine engine.
So I do not think that this is strictly a totem problem, but a libxine1
one.

** Package changed: totem (Ubuntu) => xine-lib (Ubuntu)

** Changed in: xine-lib (Ubuntu)
   Status: Invalid => Incomplete

-- 
totem causes alt key press in openoffice every 30 seconds
https://bugs.launchpad.net/bugs/216939
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 281993] [NEW] [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

Public bug reported:

I have a Microsoft Wireless Keyboard 3000, part of a wireless RF
keyboard/mouse bundle, which comes with several media keys (Back,
Forward, Play/Pause, Vol. Down, Vol. Up, Mute, Home, Search, Mail and
Calculator). They worked perfectly in Hardy once I got all the keysyms
straight in gnome-keybinding-properties.

Since updating to Intrepid beta (via update-manager), none of these
multimedia keys work anymore. Apparently, no KeyPress/KeyRelease event
is generated when they are pressed (checked with gnome-keybinding-
properties and with xev). Further, I have gone as far as to go to a
(tty) console and use 'kbd_mode -s' to see the raw input from the
keyboard (thankfully I remembered about SysRq+R before rebooting ;)),
and the multimedia keys do not generate any.

I am using the Generic 105 keys international distribution, which used
to work perfectly under Hardy. I have also tried many other
possibilities, including every Microsoft-branded keyboard in the
database, several unrelated models and some of the generic keyboards
(including the "Evdev-managed"), to no avail.

I have seen several other similar bugs, but none of them related to
exactly the same behavior. I am using Intrepid beta, up to date.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

I have found that the same behavior is triggered by hugin when
compositing large panoramas. The error seems related to generic
manipulation of very big images, not specifically by changing the
desktop wallpaper.

Any ideas on this topic?

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 232197] Re: firefox 3.0 very slow on some sites, blocking computer

[José M . López-Cepero]

I'm seeing the same behavior on some sites. The scrolling becomes so
slow that the browser freezes for 1-2 seconds whenever you do. If you
hit the clickwheel a few times, it's enough to trigger the "unresponsive
application" warning, while the browser uses 100% CPU to redraw the
window.

I'm using Ubuntu 8.04 in AMD64, up to date as of now (June 5th). Kernel
2.6.24-18-generic, Firefox 3.0~rc1+nobinonly-0ubuntu0.8.04.1, Xorg
1:7.3+10ubuntu10.1. I have Compiz enabled with nVidia proprietary driver
(169.12).

I'm attaching a test case which is pretty painful for me with Firefox 3,
but which renders fine on Ubuntu 7.10 with Firefox 2.

I suppose this bug is related to the Gecko engine, since epiphany-
browser also exhibits it. I also suspect Bug #207454 is related to this
one, but this seemed more general, so I'm posting here.

** Attachment added: "Example of site triggering the slow rendering."
   http://launchpadlibrarian.net/15027037/SlownessExample.zip

-- 
firefox 3.0 very slow on some sites, blocking computer
https://bugs.launchpad.net/bugs/232197
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 273604] Re: audacious crashed with SIGSEGV in __libc_start_main()

[José M . López-Cepero]

I was also getting a segfault on audacious start. By renaming
/usr/lib/audacious/Output/libcrossfade.so to something else (with a
different extension), I am now able to start the program just fine.

Example backtrace with debugging symbols enabled:

$ gdb `which audacious`
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /usr/bin/audacious 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fd8d385b770 (LWP 10156)]
[New Thread 0x40e22950 (LWP 10159)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fd8d385b770 (LWP 10156)]
set_pvt_data (plugin=0x1, data=0x0) at pluginenum.c:425
425 pluginenum.c: No such file or directory.
in pluginenum.c
(gdb) bt
#0  set_pvt_data (plugin=0x1, data=0x0) at pluginenum.c:425
#1  0x7fd8c527169f in ?? () from /usr/lib/audacious/Output/libcrossfade.so
#2  0x00423895 in plugin_system_init () at pluginenum.c:909
#3  0x00419a72 in main (argc=1, argv=0x7fffdb88edd8) at main.c:735

-- 
audacious crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/273604
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 254107] [NEW] xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Public bug reported:

Binary package hint: xorg

Executive summary: Changing the desktop wallpaper under Gnome makes Xorg
resident memory usage increase non-reversibly. Given enough changes of
wallpaper, xorg ends up using up every bit of the available memory,
bringing the system down with it.

Detailed description:

I have built a program which changes the desktop wallpaper by writing a
gconf key. Nautilus monitors the key and sets the desktop wallpaper
accordingly.

I am using the program with a lot of decent-sized images (about
2000-3000 pixels wide) and setting it to change every 5 minutes.

Whenever a wallpaper change occurs, Xorg's memory usage goes up. This
does not seem to be related with apps storing resources in the server,
since xrestop remains largely unchanged. Also, nautilus (the app which
changes the desktop) does not increase its memory usage, nor does
killing it help with anything Xorg-related.

Take this status, which is normal after about 25-30 desktop changes. The
memory usage (measured with htop) is:

xorg: 1328M  422M 13580
nautilus: 499M 80712 17576

(resp. VIRT, RES, SHR).

xrestop usage:
Pixmaps:   33739K total, Other: 277K total, All:   34017K total

I now change the desktop wallpaper by writing to the gconf key:

xorg: 1341M  435M 13580 (+~14M VIRT and RES)
nautilus:  499M 80712 17576 (unchanged)
Pixmaps:   33767K total, Other: 276K total, All:   34044K total (largely 
unchanged, slight differences maybe due to the different size of the underlying 
wallpaper)

After another change:
xorg: 1355M  449M 13612 (+~14 M, again)
nautilus: 499M 80712 17576 (unchanged)
Pixmaps:   33741K total, Other: 274K total, All:   34016K total 
(essentially unchanged, again)

Just to be sure that it's not something related to my own tool, I tried
changing the background by using Gnome's own tools a few times, with
similar results.

I am rather confused as to what the origin of this leak might be. I can
imagine nautilus being the culprit, since it is the application that
sets the background; however, since the only application increasing its
memory usage in this process is xorg, and there is no indication of
xrestop leakage, I am reporting the bug here.

I am using Hardy 8.04.1, fully updated, nVidia GeForce 8500 GT with
proprietary drivers (nvidia-glx-new).

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Thanks for reassigning to the correct package (I suppose :))

Is there any particular test you want me to carry out to further
investigate this bug?

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Ok, so I have investigated some more and found several interesting
links.

A very similar Debian bugreport, which seemed to right itself
misteriously:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326956

In Ubuntu forums:
http://ubuntuforums.org/showthread.php?t=440038&page=6

Interestingly, the last post (as of now, by Tsu Dho Nimh 1 week ago)
mentions that using very large images seems to trigger the error, which
is consistent with what I am seeing.

I would guess that something is preventing old images from being freed,
and/or having their space effectively used/returned to the stack.

Interestingly, as per one of the Gentoo user's post, I used pmap on the
Xorg process. Here are the first lines of a typical pmap:

8<---8<---8<---8<---8<---8<---

6148:   /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
Address   Kbytes RSSAnon  Locked Mode   Mapping
00401764   -   -   - r-x--  Xorg
007b9000  68   -   -   - rw---  Xorg
007ca000  310936   -   -   - rw---[ anon ]
41543000   8   -   -   - rwx--  zero
7f2360c2e000  96   -   -   - rw-s-[ shmid=0x13a807f ]
7f2360c460007592   -   -   - r  kochi-gothic-subst.ttf
7f23613b 284   -   -   - rw-s-[ shmid=0x13a007e ]

8<---8<---8<---8<---8<---8<---

By looking at base addresses, there is a different between the first
four values and the rest of the file, so they probably are some kind of
special buffer. Specifically, the [ anon ] block at 0x7ca000 is highly
suspicious, since it does not have execute permissions, and (more
importantly) is huge, at over 300 Mb.

If I change the background now, hey presto, the [ anon ] block grows by
about 20 Mb, which is roughly the same amount that the Xorg memory usage
does (according to htop and to pmap). This is repeatable, so that seems
to be the problem. Now, if somebody knows what that [ anon ] block is
used for...

I think the rest of the pmap is fairly uninteresting; there are some
changes, but the ballooning of the used memory is due to the first [
anon ] block (if there is any other contribution, it is negligible). I
can attach them if you are interested, though.

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 254107] Re: xorg memory leak when changing desktop wallpapers (Gnome)

[José M . López-Cepero]

Well, if the error is indeed related to caching, the bug is that the X
server is unable (or unwilling) to free some of the buffers when running
out of memory. I would suppose that a cache has some kind of limit, but,
as it is now, there seems to be none (nor there is any mechanism to free
the cache that I am aware of). The memory usage keeps growing and
growing without control.

-- 
xorg memory leak when changing desktop wallpapers (Gnome)
https://bugs.launchpad.net/bugs/254107
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

** Description changed:

+ I have a Microsoft Wireless Keyboard 3000, part of a wireless RF
+ keyboard/mouse bundle, which comes with several media keys (Back,
+ Forward, Play/Pause, Vol. Down, Vol. Up, Mute, Home, Search, Mail and
+ Calculator). They worked perfectly in Hardy once I got all the keysyms
+ straight in gnome-keybinding-properties.
+ 
+ Since updating to Intrepid beta (via update-manager), none of these
+ multimedia keys work anymore. Apparently, no KeyPress/KeyRelease event
+ is generated when they are pressed (checked with gnome-keybinding-
+ properties and with xev). Further, I have gone as far as to go to a
+ (tty) console and use 'kbd_mode -s' to see the raw input from the
+ keyboard (thankfully I remembered about SysRq+R before rebooting ;)),
+ and the multimedia keys do not generate any.
+ 
+ I am using the Generic 105 keys international distribution, which used
+ to work perfectly under Hardy. I have also tried many other
+ possibilities, including every Microsoft-branded keyboard in the
+ database, several unrelated models and some of the generic keyboards
+ (including the "Evdev-managed"), to no avail.
+ 
+ I have seen several other similar bugs, but none of them related to
+ exactly the same behavior. I am using Intrepid beta, up to date.
+ 
+ -
+ 
+ (This was written by somebody else, erasing the original description in
+ the process:)
+ 
  Microsoft Wireless Keyboard 3000 user here.  Confirming this is indeed a
  regression.  I didn't realize how much I relied on the special keys
  until they disappeared!  Would appreciate any insight into why this
  regression occurred, in addition to what might be done to fix it.

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

I'm attaching the relevant section of the lsusb - output. The
receiver is both for the mouse and the keyboard (MS Wireless Keyboard
3000).

Also, I reverted the description back to my original text; it had been
erased at some point.

Thanks for your help!

** Attachment added: "lsusb - for the MS Wireless Keyboard 3000 
transmitter."
   http://launchpadlibrarian.net/20991740/lsusb-mskey

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

I can confirm that the new kernel fixes the issue. Thanks for your work,
Andy!

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 281993] Re: [intrepid] REGRESSION: multimedia keys no longer working

[José M . López-Cepero]

(and Lucas, of course...)

-- 
[intrepid] REGRESSION: multimedia keys no longer working
https://bugs.launchpad.net/bugs/281993
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 264551] [NEW] Firefox reloads pages when automatically changing encodings

[José M . López-Cepero]

Public bug reported:

Binary package hint: firefox

Firefox detects the appropriate encoding of a webpage which does not
explicitly state it and reloads it to re-render the page with the
correct encoding if necessary.

Unfortunately, this completely disregards the fact that reloading a
dynamic page may have unintended consequences. Specifically, Firefox
will happily reload a page which has a GET parameter, which means that
some operations (eg. a database insert) may end up being done twice.

I have built a case which reliably reproduces the bug in my machine. I
have hosted it at:

http://andvaranaut.es/example.php

The file is a PHP script which does the following:

1) Writes a very basic html header, with no encoding info (the reload event 
happens even if the output is plain text, by the way)
2) Writes "Hi, I'm gonna output some weird characters in about 2 secs"
3) Sleeps for 2 secs
4) Writes a bunch of accented letters to stdout (in UTF-8, although the exact 
encoding seems to be irrelevant).
5) Sleeps for another 2 secs
6) Writes "Got that?", closes the remaining HTML tags, and ends

Each of the writings in steps 2, 4 and 6 is done within a paragraph tag,
although that does not seem relevant to triggering the reload.

The very first time you visit the page, you'll get to stage 2) (see the
"Hi, I'm gonna output..." message). Then, the browser will pause for 2
seconds (stage 3)). And then, the page will immediately reload. The
reason is that, having received the accented letters in stage 4),
Firefox decides that it has to rerender the page, and does so by
reloading and internally setting what it considers to be a suitable
encoding this time. Once the reload begins, you will proceed through
steps 1)-6) as expected. This means that you will wait for 6 seconds
instead of 4, that the "Hi, I'm gonna output..." message will flash
twice, and that all PHP code in steps 1) through 3) will be executed
twice at the end of the day.

If you hit F5 and/or press Enter in the address bar, Firefox will
remember the encoding it used and only load the page once, working as
expected. But, if you open a new session, hit Shift+F5 or add some
random GET parameters to the URL, the page will again load twice. (If
you repeat GET parameters in the same session, it also remembers the
encoding. But you have to repeat the full URL).

I have not tested what happens with POST requests, where the results may
be even more disastrous (either a form will be submitted twice, or the
user will be shown a confusing dialog about "refreshing" a page he is
just visiting, or, worse yet, the page will reload without sending the
form contents a second time).

I'm using Firefox 3.0.1 in amd64 Hardy, fully updated.

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Firefox reloads pages when automatically changing encodings
https://bugs.launchpad.net/bugs/264551
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 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Just wanted to let you know that this bug has a _really_ nasty
interaction with the wireless chip on the laptop (a fairly common
ipw3945). When one of these hanges occurs, the module may crash with a
PREEMPT, which essentially means that wireless is lost unless the
computer is rebooted. The probabilities of this occurring are seemingly
related with the network activity at the time of the hang. For instance,
if I run aMule and have some downloads going on (nothing too speedy,
maybe 30 kb/s between upload and download) the wireless connection will
rarely be up for more than 1 hour. (No exaggeration - it actually just
went out as I was writing this report - total uptime is 12 _minutes_).

I'm a little frustrated at not being able to use my favourite distro
effectively on my computer. I understand that maybe this is not the
correct place to report the bug, or that I should provide more
information, or that you are just very busy at the moment, and that's
why there are no advances on the issue. In that case, I'd  really like a
pointer to what to do next to help you, or to the correct libata
mantainer. As I said before, I like to think that I'm a rather savvy
Linux user, but if it comes to low-level kernel debugging, I'm totally
at a loss.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Hi Ben,

Thanks for your reply. I'm rather confident I'm current with all
updates. The kernel package I'm using is

linux-image-2.6.15-26-386
Version 2.6.15-26.46

It is indeed from dapper-security; I can't seem to find a way for
synaptic or apt-cache to show me the date, though.

I have seen that Edgy has a slightly more advanced kernel version, and
that building custom kernels in Dapper and below is rather discouraged.
Do you think updating to Edgy would help? (I have quickly glanced
through 2.6.17 changelogs, but found nothing libata related). I have run
Breezy and Dapper already before release, but not this early in the
release cycle.

Thanks again for your reply. If there is any other test I can carry out
for you, please let me know.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Edgy Eft LiveCD Knot 1 won't boot. The process hangs rather early in the
bootup sequence: in the initrd, while trying to mount the root
filesystem. After a few seconds, it bails out to a BusyBox prompt
complaining that it does not have access to the tty because job control
is turned off (or something similar). The MD5sum of the CD is correct,
so it is not a recording problem on my side.

Any other ideas? :(

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

A small update. Today I have struck a lucky chord: it's already almost
5h uptime and not a single hang (and, therefore, my wireless connection
is working happily). If I do a dmesg, the following suspicious lines
appear:

[17179641.092000] cdrom: sr0: mrw address space DMA selected
[17179641.116000] Assertion failed! qc->n_elem > 
0,drivers/scsi/libata-core.c,ata_fill_sg,line=2531
[17179641.376000] cdrom: sr0: mrw address space DMA selected
[17179641.38] Assertion failed! qc->n_elem > 
0,drivers/scsi/libata-core.c,ata_fill_sg,line=2531

Whatever that means, I have not seen them before (and I don't remember
updating the kernel from yesterday to today). The system seems to work
perfectly fine, with no evident negative consequences of the failed
assertion, and with no hangs. The CD works seemingly OK, and copying
large files out of it doesn't clog the CPU, but the maximum transfer
speed seems to be around 2 MB/s. I'd rather endure that than the hangs.
If any of you know of any way to force the "mrw address space DMA", that
might be a good enough workaround for the moment...

I'll leave the computer running overnight to be sure, and then reboot
and see if it magically works again...

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Public bug reported:

Binary package hint: linux-386

I have an Acer Aspire 9410 Centrino Duo laptop and there seems to be a
problem with the SATA controller. Although I have found no major flaws
yet (ie. no data corruption), every few minutes (maybe 2, maybe 30) the
system seems to hang for a while (about 10-30 sec).

Apparently, the problem is that the ata driver is not fully compatible
with the chipset. Examining dmesg's output, every time a hang happens
the following lines appear:

[17186864.708000] ata1 is slow to respond, please be patient
[17186889.664000] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x60
[17186889.664000] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 
0xb/47/00
[17186889.664000] ATA: abnormal status 0xD0 on port 0x1F7
[17186891.016000] ata1: status=0x50 { DriveReady SeekComplete }
[17186891.016000] sda: Current: sense key: No Sense
[17186891.016000] Additional sense: No additional sense information
[17186891.02] sr0: CDROM (ioctl) error, command: <6>Read TOC/PMA/ATIP 43 00 
00 00 00 00 00 00 0c 40
[17186891.02] sr: Current [descriptor]: sense key: Aborted Command
[17186891.02] Additional sense: Scsi parity error
[17186891.02] ATA: abnormal status 0xD0 on port 0x1F7
[17186891.02] ATA: abnormal status 0xD0 on port 0x1F7

The main scheme is always the same: there is an 'ata1 is slow to
respond, please be patient', followed by a timeout and a few errors. The
CD error message may appear or not; I remember having seen a few
different variations (examining /var/log/messages, the "sense key" may
be "No sense", "Scsi parity error" or "Aborted command", and there are
another slight variations, and the error may come from sda or sr0). The
"abnormal status" messages are always there; I have looked around for a
reference to what status 0xD0 means, but to no avail. I think what
causes the hangs is that the system blocks until a 30 second timeout
passes from the "slow to respond" message.

I'm using 2.6.15-26-386 (the 686 version caused the laptop to hang at
seemingly random times); as revealed by lspci, the controler is:

:00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family)
Serial ATA Storage Controllers cc=IDE (rev 02)

(numeric code 8086:27c4), which apparently should be well supported by
ata_piix. I have not yet tried with another Linux distro, but Windows XP
does not exhibit that problem. Also, I exchanged the laptop for another
because of an unrelated problem and the hangs kept happening.

I assume this is due to some kind of bug on the sata controllers and
that's why I'm reporting the bug here. Feel free to direct me to any
other source and I'll repost. Alternatively, if there was some way to
set the 'slow to respond' timeout to a shorter time (5 seconds or so),
that would probably be a good enough workaround.

I will immediately attach the output of dmesg, lspci and lsmod.

Thanks in advance for your help.

** Affects: linux-meta (Ubuntu)
 Importance: Untriaged
 Status: Unconfirmed

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

lspci -

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

dmesg

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

/var/log/messages. Search for "ata1 is slow to respond" to locate hangs.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

lsmod

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Sorry - I forgot to mention. I'm using Ubuntu Dapper, freshly installed
and with all the updates applied.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

And sorry (again). When the CD error occurs, it is always (or at least
the times I have noticed) a "read TOC" error such as the one above. But
there is no disc in the drive to read the TOC from. I don't know if it
is usual to issue read TOC commands in empty drives...

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Changing to Confirmed, since it has happened to me in two different
laptops (thus nearly excluding hardware problems) and on a stock Ubuntu
6.06 installation.

** Changed in: linux-meta (Ubuntu)
   Status: Unconfirmed => Confirmed

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Sorry for not answering earlier - I have been without internet
connection.

I have found what seems to be a workaround. Don't ask me how it is
supposed to work, though :D

Apparently, when I boot up using the Edgy CD I downloaded and choosing
"Boot from first hard disk" from the menu, the CD gets put in the "mrw
address space DMA" (whatever that is) and the system may go on happily
for days (very rarely I get a hangup, but it would be like one in a week
or so. I don't know why that happens (note that the only thing from the
CD that gets executed is the bootloader), but it seems to be reliable...

Cheers

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

ubuntu-bugs@lists.ubuntu.com

[José M . López-Cepero]

Public bug reported:

Binary package hint: metacity

I suggest having windows raised not on mouse-button-down (as they are
now), but in mouse-button-up; making that the default behavior and/or
adding an option to turn it on.

Furthermore, I suggest raising windows if the cursor stays over them for
a few seconds when in a drag&drop operation.

Rationale:

 - There are two main "click" operations which can be done in a window:
click (button down, button up) and drag (button down, move mouse holding
button), as in drag&drop operations.

 - If the user clicks in a window, the new behavior would be almost the
same as it is now, with no noticeable differences other than the (very
small) delay between mouse-down and mouse-up.

 - If the user wants to do a drag&drop operation, the new behavior would
allow him to do the drag&drop between _all visible items_ the moment the
operation begins, whereas the old behavior does not.

Say you have two partially overlapping Nautilus windows open. In the one
in the foreground there is a folder, and in the one in the background
there is a file which is not obscured by the foreground window. You want
to drag that file to the folder. With the current behavior, clicking and
dragging on the file immediately raises the background window, changing
the screen distribution (counter-intuitive) and obscuring a significant
part of the foreground window (likely including the intended drag&drop
target). With the new behavior, you just drag the (visible) file to the
(visible) folder and that's it.

Let's say now that the situation is reversed. You want to drag a file
from a foreground window to a folder in a background window. The
background window is obscured by the foreground window, so the target
folder is not visible. With the current behavior the best way to
drag&drop is either moving the windows (so the drag&drop is not direct)
or using the task bar (rather inconvenient). With the proposed behavior
it's just drag the file to the visible part of the background screen -
linger for 2 seconds with the button down - the background screens is
raised - drag to the (now visible) folder and release the button.

The suggested behavior would make dragging & dropping more convenient
and more intuitive, and I have seen it implemented to good use in
several other file managers. I have filed the bug against Metacity
because I suppose that it's possible to control this policy in the
window manager.

Thanks for your time and keep up the good work.

** Affects: metacity (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
Wish: Improve drag&drop: raise window on mouseup & drag&drop
https://launchpad.net/bugs/70419

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 146290] Re: gimp "open from url" doesn't work

[José M . López-Cepero]

My 2 cents: The correct package to install is called "gimp-gnomevfs".
Installing libcurl or gnomevfs alone won't do (at least it didn't work
for me).

-- 
gimp "open from url" doesn't work
https://bugs.launchpad.net/bugs/146290
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 188101] Re: gnome-terminal doesn't show any items in menubar

[José M . López-Cepero]

I can confirm this problem. I'm using the Spanish (Spain) locale. Hardy,
just updated.

Maybe some i18n files are missing?

-- 
gnome-terminal doesn't show any items in menubar
https://bugs.launchpad.net/bugs/188101
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 89723] Re: LifeDrive's hard disk doesn't mount automatically

[José M . López-Cepero]

*** This bug is a duplicate of bug 81219 ***
https://bugs.launchpad.net/bugs/81219

** This bug has been marked a duplicate of bug 81219
   [Feisty] Second volume in a USB drive not mounted

-- 
LifeDrive's hard disk doesn't mount automatically
https://bugs.launchpad.net/bugs/89723
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 81219] Re: [Feisty] Second volume in a USB drive not mounted

[José M . López-Cepero]

Sadly, this bug does not seem to have made it on time for the final
release of Feisty, which makes it a regression as compared to Edgy (and
Dapper). Too bad.

I have marked #89723 (where some similar information is posted) as a
duplicate as reported by Matt. Both bugs are now marked as "needs info".
Since more information has been reported in both cases, it would be nice
to have a developer quickly review it and state whether more information
is still needed or, if not, update the status to something more
appropriate.

Some word from the developers on the matter would be welcome. Of course,
I (and I suppose everybody) understand that the reason this bug has not
been dealt with yet is probably just lack of time, so I don't want to
sound like I'm rushing anybody. Just asking nicely.

Best regards.

-- 
[Feisty] Second volume in a USB drive not mounted
https://bugs.launchpad.net/bugs/81219
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 82486] Re: [feisty] very nasty bug with libata

[José M . López-Cepero]

I don't really remember doing that, but it could be. Sorry for being
annoying :)

However, I still think it would be a good idea to not make libata choke
on unknown parameters.

Thanks

-- 
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

I have recently begun using the same laptop I had the problem as my main
computer (for the past 3 months I didn't use it much), and apparently
updating to Feisty solves the problem. If the involved computers are not
mission critical I'd reccommend you to update to Feisty (there's the
ocassional  breakage, but overall it is rather stable).

I do have a CD in the drive. I haven't yet researched what happens if I
remove it.

Best regards, Jose

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81219] Re: [Feisty] Second volume in a USB drive not mounted

[José M . López-Cepero]

Hi Martin,

Sorry for the delay. I have just begun a short research stay abroad and
it's always a little difficult to completely settle down fast. :)

I have confirmed the problem in a different computer (also with feisty,
up to the last updates). I have generated a hal.log file by following
the Dapper instructions in the wiki page you posted. The device is
plugged in at timestamp 22:59:06.551. Confusingly enough, hal does seem
to find the partition. The only eye-catching difference I can spot
between the processes followed for the HD and the SD card reader is that
after the "Doing addon-storage for /dev/sdX" message, only the second
time around does osspec.c report having added the device name:


[29032]: 22:59:12.541 [D] addon-storage.c:312: 
**
[29032]: 22:59:12.541 [D] addon-storage.c:313: Doing addon-storage for /dev/sdd 
(bus usb) (drive_type disk) (udi 
/org/freedesktop/Hal/devices/storage_serial_Unknown_SDC_PVG0M635V2EV)
[29032]: 22:59:12.541 [D] addon-storage.c:314: 
**
22:59:12.568 [I] osspec.c:226: SEQNUM=3028, ACTION=add, SUBSYSTEM=block, EVPATH
=/sys/block/sdd/sdd1, DEVNAME=/dev/sdd1, IFINDEX=0

The previous "doing addon-storage" for /dev/sdc (the 4Gb HD) does not
have a similar osspec.c line.

I hope this helps. Thanks for your attention!

** Attachment added: "hal debug output"
   http://librarian.launchpad.net/6608997/hal.log

-- 
[Feisty] Second volume in a USB drive not mounted
https://launchpad.net/bugs/81219

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Using 2.6.20-9-generic SMP on Feisty.

Without a CD in the drive, there are hangs and the dmesg messages are
almost exactly the same chantra has reported:

[ 9575.732000] ata1.01: cmd a0/01:00:00:00:00/00:00:00:00:00/b0 tag 0 cdb 0x25 
data 8 in
[ 9575.732000]  res 50/00:00:00:00:00/00:00:00:00:00/b0 Emask 0x2 (HSM 
violation)
[ 9575.732000] ata1: soft resetting port
[ 9576.084000] ata1.00: configured for UDMA/100
[ 9576.264000] ata1.01: configured for UDMA/33
[ 9576.264000] ata1: EH complete
[ 9576.28] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[ 9576.296000] sda: Write Protect is off
[ 9576.296000] sda: Mode Sense: 00 3a 00 00
[ 9576.304000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[ 9576.336000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[ 9576.34] sda: Write Protect is off
[ 9576.34] sda: Mode Sense: 00 3a 00 00
[ 9576.34] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[10195.476000] ipw3945: association process canceled
[10531.292000] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[10531.292000] ata1.01: cmd a0/01:00:00:00:00/00:00:00:00:00/b0 tag 0 cdb 0x43 
data 12 in
[10531.292000]  res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 
(timeout)
[10538.292000] ata1: port is slow to respond, please be patient (Status 0xd0)
[10561.308000] ata1: port failed to respond (30 secs, Status 0xd0)
[10561.308000] ata1: soft resetting port
[10561.66] ata1.00: configured for UDMA/100
[10561.848000] ata1.01: configured for UDMA/33
[10561.848000] ata1: EH complete
[10561.864000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[10561.872000] sda: Write Protect is off
[10561.872000] sda: Mode Sense: 00 3a 00 00
[10561.888000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[10561.912000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[10561.912000] sda: Write Protect is off
[10561.912000] sda: Mode Sense: 00 3a 00 00
[10562.288000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA

I had a few more errors of the "timeout" kind after this one, and they
all corresponded to hangs. They seemed to happen very frequently, like
every 20 minutes or less. I did not get any other "HSM violation"
errors.

The good part: With a CD in the drive, the computer works perfectly. No
hangs, no dmesg messages, all good and well.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 53754] Re: ata_piix problem with Intel ICH7 chipset

[José M . López-Cepero]

Using 2.6.20-9-generic SMP on Feisty.

Without a CD in the drive, there are hangs and the dmesg messages are
almost exactly the same chantra has reported:

[ 9575.732000] ata1.01: cmd a0/01:00:00:00:00/00:00:00:00:00/b0 tag 0 cdb 0x25 
data 8 in
[ 9575.732000]  res 50/00:00:00:00:00/00:00:00:00:00/b0 Emask 0x2 (HSM 
violation)
[ 9575.732000] ata1: soft resetting port
[ 9576.084000] ata1.00: configured for UDMA/100
[ 9576.264000] ata1.01: configured for UDMA/33
[ 9576.264000] ata1: EH complete
[ 9576.28] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[ 9576.296000] sda: Write Protect is off
[ 9576.296000] sda: Mode Sense: 00 3a 00 00
[ 9576.304000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[ 9576.336000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[ 9576.34] sda: Write Protect is off
[ 9576.34] sda: Mode Sense: 00 3a 00 00
[ 9576.34] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[10195.476000] ipw3945: association process canceled
[10531.292000] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[10531.292000] ata1.01: cmd a0/01:00:00:00:00/00:00:00:00:00/b0 tag 0 cdb 0x43 
data 12 in
[10531.292000]  res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 
(timeout)
[10538.292000] ata1: port is slow to respond, please be patient (Status 0xd0)
[10561.308000] ata1: port failed to respond (30 secs, Status 0xd0)
[10561.308000] ata1: soft resetting port
[10561.66] ata1.00: configured for UDMA/100
[10561.848000] ata1.01: configured for UDMA/33
[10561.848000] ata1: EH complete
[10561.864000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[10561.872000] sda: Write Protect is off
[10561.872000] sda: Mode Sense: 00 3a 00 00
[10561.888000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[10561.912000] SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
[10561.912000] sda: Write Protect is off
[10561.912000] sda: Mode Sense: 00 3a 00 00
[10562.288000] SCSI device sda: write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA

I had a few more errors of the "timeout" kind after this one, and they
all corresponded to hangs. They seemed to happen very frequently, like
every 20 minutes or less. I did not get any other "HSM violation"
errors.

The good part: With a CD in the drive, the computer works perfectly. No
hangs, no dmesg messages, all good and well.

-- 
ata_piix problem with Intel ICH7 chipset
https://launchpad.net/bugs/53754

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81621] Re: problems when "cd" to Directories with german umlauts and "_"

[José M . López-Cepero]

Fix tested and working. Thanks!

-- 
problems when "cd" to Directories with german umlauts and "_" 
https://launchpad.net/bugs/81621

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81219] Re: [Feisty] Second volume in a USB drive not mounted

[José M . López-Cepero]

Thanks for the comment, Cristian. I attach all the files as directed (I
followed the Dapper instructions). I have cut the dmesg file to only
include the messages produced from the moment the device was plugged in.

Be warned that the device is not exactly a USB key in its behavior. When
it is first plugged in, it gets recognized as a Palm PDA (that's what
the "Handspring Visor" messages are for). Then, you run an utility on
the device and it starts to behave like a USB drive, so the kernel
"sees" a disconnect from the Visor and a connect from the USB drives.
The device used to work perfectly that way under Edgy and, just to try,
I have done it the other way around (first enable "USB key mode", then
plug it in) and the behavior is identical.

The result is always the same: the drives get recognized (as in, the
scsi /dev/ entries are created and I can manually mount/unmount/use
them) but only the SD card (first of the created drives) gets mounted
(if a card is present, that is; in fact, the "photos found" dialog box
pops up in that case). The "palmOne file storage" device does not get
mounted automatically (no matter whether there is a SD card in the slot
or not) but, as I just mentioned, I can access it just fine by mounting
it manually.

Output of id: uid=1000(cepe) gid=1000(cepe)
grupos=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),44(video),103(plugdev),107(lpadmin),108(scanner),1000(cepe)

Output of id hal: complains that the user hal does not exist

Output of id haldaemon: uid=118(haldaemon) gid=118(haldaemon)
grupos=118(haldaemon),24(cdrom),25(floppy),103(plugdev),122(powerdev)

Output of uname -a: Linux ubuntu 2.6.20-8-generic #2 SMP Tue Feb 13
05:18:42 UTC 2007 i686 GNU/Linux

I hope that sheds some light on the problem. Thanks for your help and
don't hesitate to ask for any further information you might need.

Best regards.

** Attachment added: "log files when plugging the device in"
   http://librarian.launchpad.net/6467391/report.zip

-- 
[Feisty] Second volume in a USB drive not mounted
https://launchpad.net/bugs/81219

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82486] Re: [feisty] very nasty bug with libata

[José M . López-Cepero]

Hi Cristian,

Right now, I don't have access to the computer where I originally had
the problem in. I will do as you suggest when I can, although I'm afraid
that the kernel version has been updated since, so I'm not sure that it
will be of much use.

However, I could reproduce the problem this way:

 - Create a file called /etc/modprobe.d/libata
 - Write "options libata printk=255" in the file 
 - Recreate the initrd (either manually or by updating the kernel) - that will 
get the /etc/modprobe.d/libata file on the initrd
 - Reboot. When loading the initrd, libata will refuse to load because it will 
not recognize the 'printk' parameter. Then, the root partition will not be 
accessible, and booting will fail at the early stages.

I don't know where the /etc/modprobe.d/libata file first came from. I
have another computer which I usually upgrade more or less at the same
time and it did not show the problem. So maybe it was some strange bug
in modutils or something like that. I searched extensively and, although
there were a few reports of similar problems, they are very rare, so
whatever happened is probably not an issue now. If you consider that to
be enough, feel free to close the bug.

However, I'd personally vote for making the libata module handle
erroneous parameters more gracefully (printing a warning and ignoring
them instead of failing to load), since I think that making a critical
module not load because of a misspelled argument is not exactly the best
way to handle the error.

Best regards.

-- 
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] failures in update to feisty

[José M . López-Cepero]

Public bug reported:

I updated yesterday from Edgy to Feisty by running "update-manager -c
-d". The upgrade got through without errors until the "configuring
packages" phase. Then, the update of five packages failed:

vim
vim-tiny
ubuntu-minimal
nano
ubuntu-standard
mc

Following the update-manager prompts, I'm reporting this bug and
attaching the contents of /var/log/dist-upgrade after this message.

I tried mc after the update and it worked; it seemed not to have updated
to the last version, though. Strangely enough, apt-get dist-upgrade did
not work the first time I ran it, but did work the second or third. I
don't think I did anything package related between one run and the next,
but maybe the error was related to still open files or something
similar.

I also experienced a problem with gnome-panel during the upgrade; it
froze in an unresponsive state. Killing it with "killall gnome-panel"
made it return to normal.

** Affects: update-manager (upstream)
 Importance: Undecided
 Status: Unconfirmed
** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: failures in update to feisty

[José M . López-Cepero]

** Attachment added: "contents of /var/log/dist-upgrade"
   http://librarian.launchpad.net/5745335/update.zip

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: Unconfirmed

-- 
failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

** Summary changed:

- failures in update to feisty
+ [Feisty] failures in update to feisty

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 76341] Re: [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages

[José M . López-Cepero]

I can confirm the error. 2.6.20-4-generic kernel, AMD Sempron 2800+, VIA
chipset (I don't remember the exact model right now, but I think it's a
KT266 or KT333). Turning off pcmcia also worked for me. With the bug
active, almost half of the processor time was wasted because of it (more
specifically, because of dd copying the klogd output to
/var/log/messages), so I'd bump up its priority.

-- 
[Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over 
/var/log/messages
https://launchpad.net/bugs/76341

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79326] [Feisty] drivemount applet shows non-unmountable volumes

[José M . López-Cepero]

Public bug reported:

Binary package hint: gnome-applets

Just upgraded from Edgy to Feisty.

My computer has a floppy disk, two DVD units and a single hard drive.
The HD has two FAT-formatted partitions (one for Windows XP, other for
storing and exchanging data) and a extended partition containing three
Linux partitions (root, /home and another one I mount on /mnt/stuff).

The drive mount applet in Edgy correctly showed only the floppy disk, as
well as any USB drive or card reader I had plugged in. Whenever I
inserted a DVD in any of the drives, it also showed up.

The Feisty version also shows three other volumes, corresponding to the
"stuff" partition and the two FAT partitions. Not only can't they be
unmounted by users (they do not have the 'user' flag in fstab), but even
if they could that would be of dubious utility, since they are
partitions in a fixed hard drive.

I suggest excluding all partitions explicitly appearing in /etc/fstab
which do not have the 'user' flag from the applet listing.

** Affects: gnome-applets (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
[Feisty] drivemount applet shows non-unmountable volumes
https://launchpad.net/bugs/79326

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79327] [Feisty] edgy->feisty upgrade not updating fstab correctly

[José M . López-Cepero]

Public bug reported:

Binary package hint: update-manager

Recently updated from Edgy to Feisty.

My /etc/fstab file had two kinds of entries. One of them was for
partitions in my hard drive. They all were formerly referenced as
/dev/hdaX, but they all were converted to the UUID form during the Edgy
update. The transition from Edgy to Feisty has worked flawlessly for
them, even keeping the swap partition working, which was troublesome in
the Dapper->Edgy update.

However, there also were two entries pointing to my DVD drives (/dev/hdc
and /dev/hdd). Since all drives are now seen as SCSI devices, these
entries are worthless. During the upgrade, they should have been changed
to /dev/scd0 and /dev/scd1 to reflect the new naming, or just have been
commented out so that the automounting could handle them automatically.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
[Feisty] edgy->feisty upgrade not updating fstab correctly
https://launchpad.net/bugs/79327

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79331] [Feisty] nvidia driver not working for 2.6.19 kernel

[José M . López-Cepero]

Public bug reported:

Binary package hint: linux

The nvidia kernel module is unusable with the 2.6.19 Feisty kernel. The
message in /var/log/messages says it all:

Jan 14 16:49:22 localhost kernel: [   95.730395] NVRM: API mismatch: the client 
has the version 1.0-9631, but
Jan 14 16:49:22 localhost kernel: [   95.730398] NVRM: this kernel module has 
the version 1.0-9629.  Please
Jan 14 16:49:22 localhost kernel: [   95.730400] NVRM: make sure that this 
kernel module and all NVIDIA driver
Jan 14 16:49:22 localhost kernel: [   95.730402] NVRM: components have the same 
version.

I'm rather confident that the problem is that the nvidia kernel provided
in the current package (linux-restricted-modules-2.6.19-7-generic) are
1.0.9629, whereas the ones in the corresponding 2.6.20-4-generic
package, as well as in nvidia-glx, are 1.0.9631.

The straightforward solution is providing 1.0.9631 in the 2.6.19
package. If there is some misterious reason why that can't be, I suggest
at least providing the corresponding nvidia-glx version as an
alternative (right now it's only 1.0.9631).

I don't think this bug is related to bug #79228, since the mismatch I'm
reporting prevents X from loading completely.

By the way, the module works perfectly with the default 2.6.20 kernel,
but I have to stick with 2.6.19 because of an incompatibility with my
wireless adapter (I use a rt73 USB key, and the rt73 driver from the
rt2x00 project does not yet support 2.6.20).

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
[Feisty] nvidia driver not working for 2.6.19 kernel
https://launchpad.net/bugs/79331

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79332] [Feisty] useless kernel retained in grub bootlist

[José M . López-Cepero]

Public bug reported:

Binary package hint: update-manager

Just updated from Edgy to Feisty. My Edgy kernel (2.6.17-10-generic)
still appears on the grub bootlist, even though it is obsolete and (more
importantly) panics just as it boots. I suggest removing old kernels
from the system on upgrade, or at least placing some kind of warning
("*deprecated*" or something similar) in the list so that the user is
not fooled into thinking they will work correctly across the upgrade.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
[Feisty] useless kernel retained in grub bootlist
https://launchpad.net/bugs/79332

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

Sorry for the delay. I have not been able to put my dirty paws on the
updated computer again until now.

This is the output of "locale", which I pressume is a rather standard
Spanish one:

[EMAIL PROTECTED]
[EMAIL PROTECTED]
LC_CTYPE="[EMAIL PROTECTED]"
LC_NUMERIC="[EMAIL PROTECTED]"
LC_TIME="[EMAIL PROTECTED]"
LC_COLLATE="[EMAIL PROTECTED]"
LC_MONETARY="[EMAIL PROTECTED]"
LC_MESSAGES="[EMAIL PROTECTED]"
LC_PAPER="[EMAIL PROTECTED]"
LC_NAME="[EMAIL PROTECTED]"
LC_ADDRESS="[EMAIL PROTECTED]"
LC_TELEPHONE="[EMAIL PROTECTED]"
LC_MEASUREMENT="[EMAIL PROTECTED]"
LC_IDENTIFICATION="[EMAIL PROTECTED]"
LC_ALL=

By the way, I don't think an archive failure had anything to do with my
particular error, since a lot of other packages had been downloaded
flawlessly, and I'm rather sure that no new packages were downloaded
before the successful installation.

And maybe it was some temporary glitch which has already been corrected.
Updating some 900 packages in an upgrade to an _alpha_ version and
getting 6 small failures doesn't really seem that unreasonable :)

Thanks to you all, CP

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

Sure!

'el subproceso post-installation script devolvió el código de salida de
error 2' == "the post-installation script subprocess returned error exit
code 2"

'problemas de dependencias - se deja sin configurar' == "dependency
problems - leaving unconfigured".

I think all the Spanish messages in the output are either of the first
or the second kind.

Best regards, CP

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81219] [Feisty] Second volume in a USB drive not mounted

[José M . López-Cepero]

Public bug reported:

I have a PalmOne LifeDrive PDA. It has a 4GB hard drive and a SD card
slot. It also has an application which allows it to appear just like a
USB drive to the operating system when connected via USB. The
application provides two different drives: one

Up to Dapper, plugging the PDA and enabling drive mode correctly mounted
and showed the two drives. However, now in Feisty the 4GB volume is no
longer mounted. This is independent of whether there is a SD card in the
PDA card reader or not. If there is, it's correctly detected and
mounted.

I can mount the drive just fine manually, but that kind of defeats the
purpose of having automounting :)

I was inclined to assign the error to hal, but the hardware browser and
lshal do show the missing drive. From hal's point of view, the LifeDrive
has an internal "SCSI Host Adapter" with two "SCSI Devices", one as
"file storage" (the 4GB drive) and a "SDC" (the SD card).

dmesg section when plugging the PDA:

---

[  166.195639] usb 5-6.6: new high speed USB device using ehci_hcd and address 
11
[  166.288417] usb 5-6.6: configuration #1 chosen from 1 choice
[  166.288769] scsi6 : SCSI emulation for USB Mass Storage devices
[  166.288833] usb-storage: device found at 11
[  166.288836] usb-storage: waiting for device to settle before scanning
[  171.289969] scsi 6:0:0:0: Direct-Access palmOne, File storage 1.0  
PQ: 0 ANSI: 0
[  171.292073] SCSI device sdg: 7818112 512-byte hdwr sectors (4003 MB)
[  171.293985] sdg: Write Protect is off
[  171.293991] sdg: Mode Sense: 0f 00 00 00
[  171.293994] sdg: assuming drive cache: write through
[  171.295945] SCSI device sdg: 7818112 512-byte hdwr sectors (4003 MB)
[  171.296923] sdg: Write Protect is off
[  171.296927] sdg: Mode Sense: 0f 00 00 00
[  171.296930] sdg: assuming drive cache: write through
[  171.296935]  sdg: sdg1
[  171.582358] sd 6:0:0:0: Attached scsi removable disk sdg
[  171.582415] sd 6:0:0:0: Attached scsi generic sg8 type 0
[  171.583371] scsi 6:0:0:1: Direct-Access Unknown  SDC  1.0  
PQ: 0 ANSI: 0
[  171.585156] SCSI device sdh: 1999872 512-byte hdwr sectors (1024 MB)
[  171.585930] sdh: Write Protect is on
[  171.585934] sdh: Mode Sense: 0f 00 80 00
[  171.585936] sdh: assuming drive cache: write through
[  171.588180] SCSI device sdh: 1999872 512-byte hdwr sectors (1024 MB)
[  171.588927] sdh: Write Protect is on
[  171.588930] sdh: Mode Sense: 0f 00 80 00
[  171.588932] sdh: assuming drive cache: write through
[  171.588937]  sdh: sdh1
[  171.592219] sd 6:0:0:1: Attached scsi removable disk sdh
[  171.592278] sd 6:0:0:1: Attached scsi generic sg9 type 0
[  171.593629] usb-storage: device scan complete

---

Thanks for any help!

** Affects: Ubuntu
 Importance: Undecided
 Status: Unconfirmed

-- 
[Feisty] Second volume in a USB drive not mounted
https://launchpad.net/bugs/81219

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

Just tested:

 - Ubuntu-desktop was not installed. I have installed it via apt-get (it
also pulled gimp-python) and got no errors.

 - dpkg --reconfigure -a did not produce any output.

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81219] Re: [Feisty] Second volume in a USB drive not mounted

[José M . López-Cepero]

** Description changed:

  I have a PalmOne LifeDrive PDA. It has a 4GB hard drive and a SD card
  slot. It also has an application which allows it to appear just like a
  USB drive to the operating system when connected via USB. The
- application provides two different drives: one
+ application provides two different mass storage drives: one is the 4GB
+ hard drive and the second is the SD card reader slot. (Edited - forgot
+ to finish the paragraph the first time, stupid me...)
  
  Up to Dapper, plugging the PDA and enabling drive mode correctly mounted
  and showed the two drives. However, now in Feisty the 4GB volume is no
  longer mounted. This is independent of whether there is a SD card in the
  PDA card reader or not. If there is, it's correctly detected and
  mounted.
  
  I can mount the drive just fine manually, but that kind of defeats the
  purpose of having automounting :)
  
  I was inclined to assign the error to hal, but the hardware browser and
  lshal do show the missing drive. From hal's point of view, the LifeDrive
  has an internal "SCSI Host Adapter" with two "SCSI Devices", one as
  "file storage" (the 4GB drive) and a "SDC" (the SD card).
  
  dmesg section when plugging the PDA:
  
  ---
  
  [  166.195639] usb 5-6.6: new high speed USB device using ehci_hcd and 
address 11
  [  166.288417] usb 5-6.6: configuration #1 chosen from 1 choice
  [  166.288769] scsi6 : SCSI emulation for USB Mass Storage devices
  [  166.288833] usb-storage: device found at 11
  [  166.288836] usb-storage: waiting for device to settle before scanning
  [  171.289969] scsi 6:0:0:0: Direct-Access palmOne, File storage 1.0  
PQ: 0 ANSI: 0
  [  171.292073] SCSI device sdg: 7818112 512-byte hdwr sectors (4003 MB)
  [  171.293985] sdg: Write Protect is off
  [  171.293991] sdg: Mode Sense: 0f 00 00 00
  [  171.293994] sdg: assuming drive cache: write through
  [  171.295945] SCSI device sdg: 7818112 512-byte hdwr sectors (4003 MB)
  [  171.296923] sdg: Write Protect is off
  [  171.296927] sdg: Mode Sense: 0f 00 00 00
  [  171.296930] sdg: assuming drive cache: write through
  [  171.296935]  sdg: sdg1
  [  171.582358] sd 6:0:0:0: Attached scsi removable disk sdg
  [  171.582415] sd 6:0:0:0: Attached scsi generic sg8 type 0
  [  171.583371] scsi 6:0:0:1: Direct-Access Unknown  SDC  1.0  
PQ: 0 ANSI: 0
  [  171.585156] SCSI device sdh: 1999872 512-byte hdwr sectors (1024 MB)
  [  171.585930] sdh: Write Protect is on
  [  171.585934] sdh: Mode Sense: 0f 00 80 00
  [  171.585936] sdh: assuming drive cache: write through
  [  171.588180] SCSI device sdh: 1999872 512-byte hdwr sectors (1024 MB)
  [  171.588927] sdh: Write Protect is on
  [  171.588930] sdh: Mode Sense: 0f 00 80 00
  [  171.588932] sdh: assuming drive cache: write through
  [  171.588937]  sdh: sdh1
  [  171.592219] sd 6:0:0:1: Attached scsi removable disk sdh
  [  171.592278] sd 6:0:0:1: Attached scsi generic sg9 type 0
  [  171.593629] usb-storage: device scan complete
  
  ---
  
  Thanks for any help!

-- 
[Feisty] Second volume in a USB drive not mounted
https://launchpad.net/bugs/81219

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

I'm afraid I do. I had a laptop with Ubuntu 6.06 LTS lying around.
Yesterday I updated to Edgy, all was apparently working OK. Today I am
upgrading it to Feisty with the update manager, and after quite a few
hours (the lack of ata_piix support makes the update glacially slow) now
I'm at the end, and the same packages are failing. vim, vim-tiny and mc
have already failed.

Locales are all es.ES_UTF8 except LC_ALL (blank) and LANGUAGE (which
contains es_ES:es:en_GB:en).

I will report the complete results later.

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

As expected, the installation failed before the cleanup phase. The error
message that appeared in the box was "installPackages() failed".

I ran sudo dpkg --reconfigure -a and vim, nano, mc, vim-tiny, ubuntu-
standard and ubuntu-minimal were configured with no error. It seems that
the system is now in a clean state. ubuntu-* were left unconfigured
because they depended on vim and/or nano.

Following with sudo apt-get dist-upgrade removed the 2.6.17 kernel docs
and replaced them with the 2.6.20 ones. Doesn't seem related.

ubuntu-desktop was installed in the Edgy phase and was updated correctly
by the update manager, so no problem there.

sudo update-manager -d -c did not report any new distribution available.

Now for an interesting fact. All four failing packages do so because of
the postinst script returning exit code 2. So it's probably some problem
with the scripts. There are two possibilities:

 - A common syntax error in them. bash returns 2 if it finds a syntax error in 
a shell script file. I don't think this is a good explanation, because if there 
was a "hard" syntax error on the postinst files, it should happen always, not 
only when upgrading.
 - All four postinst scripts have in common the use of the alternatives 
mechanism. Specifically, all four invoke update-alternatives, which is the only 
common command among them other than the shell constructs. Is there any 
possible event which would make the alternatives mechanism not work during part 
of the update? It might pay to investigate a bit further.

Thanks, Jose

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82486] [feisty] very nasty bug with libata

[José M . López-Cepero]

Public bug reported:

Binary package hint: linux

I had a laptop with Ubuntu 6.06 LTS. I updated it to Edgy and then to
Feisty and everything seemed to go okay. However, the system would not
boot after that. It would stay almost dead with only a little bit of the
boot process bar active, then drop to a shell after a few minutes.

After _lots_ of pulling my hair, I found that the cause was a file
called "libata.modprobe" in /etc/modprobe.d. The file contained the line
"options libata printk=255", and, upon booting, libata would complain of
the "printk" option being unknown... and refuse to load. Since all my
hard drives are SATA, that meant the initrd system didn't see the root
drive and thus hanged. Commenting out the option line and regenerating
the initrd solved the problem.

Two thoughts.

First: What package is responsible for the libata.modprobe file? I'd
guess this is modutils. Maybe I was caught in a bad update, or something
like that. In that case, it would be nice for subsequent updates to
correct the problem. I did chroot to my Feisty installation and apt-get
update/dist-upgrade, to no avail.

Second: Why does a critical module, such as libata, not load because of
an "unknown option"? It does not seem right to me. Wouldn't it be _much_
more sensible to just ignore the erroneous option and go on? That would
have avoided the problem...

Hope this helps someone.

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82486] Re: [feisty] very nasty bug with libata

[José M . López-Cepero]

Sorry, forgot to report. Using kernel 2.6.20-5-generic.

-- 
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79320] Re: [Feisty] failures in update to feisty

[José M . López-Cepero]

Hi Jeff,

I'm afraid that reverting to Edgy is not straightforward. However, I can
report that, after running "sudo dpkg --reconfigure -a" two times and
installing ubuntu-desktop, my system runs OK (there are rough edges, but
feisty is still beta after all). Why do you want to revert to edgy? Did
you have any other, more serious problem?

Best regards

-- 
[Feisty] failures in update to feisty
https://launchpad.net/bugs/79320

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81621] Re: problems when "cd" to Directories with german umlauts and "_"

[José M . López-Cepero]

I can confirm that with Spanish accents. Looks like an UTF-8 conversion
problem to me. Maybe multibyte constants are not handled correctly
somewhere in the shell code?

This error is very annoying, specially because it means that no shell
command can be executed from the command line (the "can't change
directory" message means that the shell remains on the parent directory,
even though the correct directory is shown in the panel).

This is a regression comparing with the Edgy version, so IMHO it should
be fixed before release.

Best regards.

** Changed in: mc (Ubuntu)
   Status: Unconfirmed => Confirmed

-- 
problems when "cd" to Directories with german umlauts and "_" 
https://launchpad.net/bugs/81621

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 79331] Re: [Feisty] nvidia driver not working for 2.6.19 kernel

[José M . López-Cepero]

Yes indeed, rt73 now works fine, thanks. But I have yet another driver
(em2880) still making me remain under 2.6.19. I am aware that Markus,
the driver mantainer, is working on making it compatible with 2.6.20, so
hopefully I'll be able to run 2.6.20 soon.

However, the main problem is that 2.6.19 has been pulled from the
repositories for some unknown (to me) reason. Since 2.6.17 won't boot
for me under Feisty (doesn't recognize the root partition, or something
of the sort), I'm left with the option of running the 2.6.19 kernel that
I had installed before it vanished from the repos, and manually
installing the official nvidia driver whenever I need to. Not to mention
reinstalling the driver whenever there is an update to nvidia-glx. I
hope the em2880 work is finished soon, but obviously it would be very
rude to nag the one doing all the hard work... So I'm sticking to 2.6.19
for the time being.

-- 
[Feisty] nvidia driver not working for 2.6.19 kernel
https://launchpad.net/bugs/79331

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs