Further occurrence conditions:
It's not just when the cursor enters a tab. It also disappears
when the cursor enters a button, and when I click on a button.
I can confirm that Bug#557033 is still present in 2.6.32
Gerry
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Yes, I waited more than a minute.
I have subsequently investigated the problem booting 2.6.32 more carefully.
I suspect it is a bug you might want to know about, unrelated to Bug#557033, so
I am about to create a fresh bug report.
Some of the information I gave earlier in this thread related
Package: linux-2.6
Version: 2.6.32-5
Severity: important
Early in the boot process, kernel writes a trace to the screen then freezes.
The problem is intermittent. About one boot attempt in 5 succeeds.
Waiting a several minutes does not unfreeze the boot.
I am preparing this report under 2.6.3
I have a partial upgrade to squeeze and I am unable to continue because there
is no network connection.
I followed recommendations in squeeze release notes. That is
1. do a minimal upgrade.
2. upgrade kernel and udev.
3. During kernel upgrade, apt-get reported missing firmware files:
r8169: r
I have now bypassed the problem by installing another network
interface card. I was able to continue the squeeze upgrade,
which is now essentially complete.
However the onboard ethernet adaptor is still not working. syslog still
contains a message ``eth0: unable to apply firmware patch''.
I wo
The onboard ethernet adaptor is now working.
/etc/network/interfaces contained no entry for eth0. I don't know why.
When I started the squeeze upgrade the onboard adaptor at eth0 was
the only adaptor.
I don't know the state of /etc/network/interfaces at the completion of
the kernel and udev
Hello Ben
>I don't understand why you say that eth0 was broken, if it wasn't
>configured before. Are you saying that the upgrade *removed* an entry
>from /etc/network/interfaces? Are you using a network interface control
>program other than ifupdown, e.g. Network Manager or wicd?
I didn't reali
Package: coreutils
Version: 8.23-4
Severity: normal
Dear Maintainer,
I entered "info ls" at a command prompt, and the output contained the
character "latin small letter a with circumflex" (U+00E2) wherever
it should have contained "single quote".
All commands in the coreutils set are affected.
Package: gscan2pdf
Version: 1.3.8-1
Severity: normal
Tags: upstream
Dear Maintainer,
(1) Start gscan2pdf
(2) Set source = Flatbed
(3) Set tl-x, tl-y, br-x, br-y to required values.
(4) Do not set mode or resolution, as they are already the required values.
(5) Save the profile as "business ca
~/.gscan2pdf and gscan2pdf.log are attached.
.gscan2pdf
Description: Binary data
INFO - Starting gscan2pdf 1.3.8
INFO - Log level DEBUG
INFO - Using C locale
INFO - Startup LC_NUMERIC C
INFO - Reading config from /home/gerry/.gscan2pdf
INFO - Config file version 1.3.8
DEBUG - $VAR1 = {
Package: gscan2pdf
Version: 1.3.8-1
Severity: normal
Tags: upstream
Dear Maintainer,
(1) ~/.gscan2pdf contains a saved profile "business card" with
settings for tl-x, tl-y, br-x, br-y and mode = 24bitColour,
resolution=200, source=flatbed.
(2) Start gscan2pdf.
(3) Set scan mode = true gray
r
Good afternoon Jeffrey
Thank you for your reply. And thank you too for your work on gscan2pdf.
I have only recently started using gscan2pdf, and I may have a
misunderstanding
about how profiles should be used. Following is the way I assumed I could
use them:
(1) Suppose I always want to scan bus
Package: gscan2pdf
Version: 1.5.2-1
Severity: important
Dear Maintainer,
I scanned an image, then rotated it 180, by clicking the rotate 180
button on the toolbar.
The image dissolved into unsynchronised garbage.
I am attaching a jpg file prior to rotation and another file after rotation.
I a
With a bit more investigation, I believe this bug is related to imagemagick
bug 837778. I have submitted a further report there.
Good morning
> well unless you can't reproduce the message with 2.6.32
> this bug can be closed.
I can neither confirm nor deny that 2.6.32 fixes bug#557033, because I can't
boot 2.6.32, and at the moment I can't devote more time to it.
It's clearly a good policy to close bugs that cannot be co
Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Package: linux-2.6
Version: 2.6.31-1
Severity: normal
*** Please type your report below this line ***
syslog reports WARNING at hpet.c:390.
The system appears to run normally, except for a single message from
GNOME: "Your sy
I have reported to http://bugzilla.kernel.org, attaching a syslog obtained
with hpet=verbose.
Bug number: 14661.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
18 matches
Mail list logo
