As noted in the upstream ticket, this now seems to have been
resolved with josm-latest and (possibly repeatedly) clearing
preferences.
I will close this bug.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
On Mon, Nov 28, 2011 at 03:00:54AM +0100, Cyril Brulebois wrote:
ael law_ence@ntlworld.com (27/11/2011):
Attempting to start x as a normal user segfaults.
You're getting VESA here.
Starting as root succeeds...
And MGA there.
Yes, but I noted that the same problem arises
On Wed, Oct 26, 2011 at 09:09:47AM +0200, Bart Hartgers wrote:
2011/10/25 ael law_ence@ntlworld.com:
On Tue, Oct 25, 2011 at 08:40:09PM +0200, Bart Hartgers wrote:
I think I got it. The ark seems sensitive to a specific combination of
setting the termios and enabling interrupts
On Tue, Oct 25, 2011 at 08:40:09PM +0200, Bart Hartgers wrote:
Hi ael,
I think I got it. The ark seems sensitive to a specific combination of
setting the termios and enabling interrupts/submitting the interrupt
urb. The old driver does not suffer because it does not use the
interrupt urb
No problems recently so will close.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I now believe that the problem arose on the xserver-xorg upgrade to 1:7.6+9.
I will consider whether I should raise a new bug against xserver rather
than synaptics...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
The Synaptics right button disabled is present almost every time I start
X.
One new datum: if I
rmmod psmouse; modprobe psmouse
then on the controlling terminal (but not in /var/log/Xorg.log) I get
[typed by hand since copy-and-paste no longer possible]:
This problem with a partially disabled touchpad - the right button
failing to work is especially problematic - seems to have become
more severe. Restarting X repeatedly is now failing to clear the
problem.
I can see no obvious recent package upgrade that might explain the
problem. But many of the
I have now found that the problem that I encountered is more
subtle.
1) Only some of the synaptics functions were disabled. In particular,
the second right (button 3) was not recognised. However scrolling
was still working.
2) Restarting X re-enabled full button recognition. Maybe a race
My synaptics touchpad is not longer working because the module is
uloaded:
- extract from Xorg.log --
[40.390] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/event11)
[40.390] (**) SynPS/2 Synaptics TouchPad: Applying InputClass
Package: cups
Version: 1.5.0-8.01
Severity: normal
Tags: upstream patch
I am trying to locate a bug in cups which currently looks like a
broken pipe. After attempts to write to a socket, an http status
of HTTP_ERROR is returned which does not have a case in the relevant
switch statement in
Package: cups
Version: 1.5.0-8
Severity: normal
The cups package does not support debugging (beyond providing
cups-debug). In particular setting DEB_BUILD_OPTIONS to
either noopt nostrip or just to noop means that
dpkg-buildpackage -rfakeroot -b ...fails.
This is a real problem because I am
to try to understand
how the error arises.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
-lang_default = cupsLangDefault();
switch (status)
{
...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
help:-( I could maybe hack around
with the source a bit trying to change register bits. I must have a
16450 datasheet somewhere which should help a bit with avoiding
messing up the known bits.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
I have changed the severity to grave since this problem
completely disables printing via cups.
I tried purging and then reinstalling the packages:
cups-drivers-gutenprint
cups
cups-bsd
cups-client
cups-common
ghostscript-cups and
cups-ppdc.
Using the localhost web admin page, there are no
with ubuntu, so I might be
able to help.
It *should* be straight forward, but you never know...
I will have a quick attempt tonight, but may have to leave things
to at least tomorrow if there are any complications.
I too am very interested to see what happens...
ael
--
To UNSUBSCRIBE, email
into the kernel without problems.
Off the get the get the gps and ark3116 hardware. Fingers crossed :-)
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
is behaving just as before.
Very disappointing: sorry again to be the bearer of bad news...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
that now parallel
provides more information:
# /usr/lib/cups/backend/parallel
direct parallel:/dev/lp0 Brother HL-1250 series Brother HL-1250 series LPT
#1 MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-1250 series;CLS:PRINTER;
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Mon, Oct 03, 2011 at 09:45:23AM +0200, Bart Hartgers wrote:
2011/10/3 ael law_ence@ntlworld.com:
Under the old working kernel, I saw packets in both directions.
For the record, the gps tx line was swinging between +5.6V and -5.4V,
while the ark3116 board was driving the gps rx
Package: cups
Version: 1.5.0-8
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
a connection to an
ordinary serial port is there?
Is there anything else I can do at this stage?
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
After the upgrades, and the same xrandr command, the panning seems
to be restricted to approximately 601 or 602 pixels.
This is surely a bug, or is the xrandr command not the correct way to
enable panning across a virtual screen? Is there some documentation
I have missed?
ael
On Sat, Oct 01, 2011 at 12:42:26PM +0200, Julien Cristau wrote:
On Sat, Oct 1, 2011 at 10:47:54 +0100, ael wrote:
I now confirm that panning seems to be restricted to 1 or 2 pixels
(vertically in this case).
To summarize, before the recent upgrades, panning worked as expected
support.
I have yet to check other aspects and get an oscilloscope on the
signals, nor try the other experiments suggested, so this is partial
and to be continued.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
-3.0.0 in the
next message.
Any suggestions before I get the oscilloscope out?
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
think.
I just might get the 'scope out later this evening if I have time.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sat, Oct 01, 2011 at 06:01:24PM +0100, ael wrote:
3) Both ark and garmin attached and working.
pin 2 (tx on gps) : 0.01V on module load
pin 3 (rx on gps) : -5.52V on module load
Looks to me as if I reversed pins 2 3 above, although it is what I
wrote down at the time...
ael
. As noted in the first report,
current changes to 1024 x 1024 despite --mode 1024x600. I am not
sure whether that is significant.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Sep 29, 2011 at 04:35:31PM +0200, Bart Hartgers wrote:
Hi ael,
I have a real RS232 port on a desktop (back at home now), so
I guess I could connect from the netbook USB - ark3116 - RS232
desktop. I will have to see what cables I have, but I think I have
a very old RS232 breakout
Package: x11-xserver-utils
Version: 7.6+3
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this
On Wed, Sep 28, 2011 at 08:55:40PM +0200, Bart Hartgers wrote:
2011/9/21 ael law_ence@ntlworld.com:
I have just done another test. This because that garmin odd connector
often fails to make proper contact. So in this case I first verified
that I could use gpsbabel successfully
.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
that it was making contact: I tried to check
carefully, although that is not always reliable.
I'll try to see if my
3116 still works with a 3.0 kernel, hopefully tomorrow. Maybe that
brings us further.
Thanks again,
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
--
As far as I can see that is just the same as when debug is not set.
Or did I get the parameter wrong? I can't see any acknowledgement
that debug is set.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
On Sun, Sep 18, 2011 at 01:55:50PM +0200, Bart Hartgers wrote:
2011/9/18 ael law_ence@ntlworld.com:
On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote:
[Previous messages are logged at http://bugs.debian.org/640391.
I have now tested properly with debug=1. Unfortunately
converter now attached to ttyUSB0
Hope something here gives a clue...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote:
2011/9/13 ael law_ence@ntlworld.com:
On Tue, Sep 13, 2011 at 08:56:54PM +0200, Bart Hartgers wrote:
[Previous messages are logged at http://bugs.debian.org/640391.
truncated the termios data. Could you please rerun
contact. I am pretty sure that it was ok
for this run, but it is just possible that the connector was playing
up. (Known problem on this model, I fear.)
ael
fstat64(3, {st_dev=makedev(0, 3), st_ino=4026532018, st_mode=S_IFREG|0444,
st_nlink=1, st_uid=0, st_gid=0, st_blksize=1024, st_blocks=0
echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Sep 08, 2011 at 06:33:29PM +0200, Bart Hartgers wrote:
Hi Ben, ael,
I am reading this on my phone and will not be able to look into this
properly (ie access a computer) before next week.
In the mean time: strace logs would be very useful. And maybe the problen
has to do
already aware? I doubt that it is a debian
specific bug...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Tue, Sep 06, 2011 at 04:16:11AM +0100, Ben Hutchings wrote:
On Mon, 2011-09-05 at 19:46 +0100, ael wrote:
On Mon, Sep 05, 2011 at 12:11:26PM +0100, Ben Hutchings wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression
On Sun, Sep 04, 2011 at 09:07:17PM +0100, Ben Hutchings wrote:
On Sun, 2011-09-04 at 19:42 +0100, ael wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
The hardware is a USB -serial port
On Sun, Sep 04, 2011 at 09:07:17PM +0100, Ben Hutchings wrote:
On Sun, 2011-09-04 at 19:42 +0100, ael wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
The hardware is a USB -serial port
with my current limited connectivity if it would help.
But at least I can recover my gps data for now.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
The hardware is a USB -serial port converter.
It was last used on this machine running debian testing in December
2011. It ran successfully with the debian kernel
On Wed, May 25, 2011 at 05:00:35PM +, maximilian attems wrote:
On Wed, May 25, 2011 at 05:49:03PM +0100, ael wrote:
Package: linux-2.6
Version: 2.6.38-5
Severity: normal
The Acer Aspire One netbook has two card readers, left right.
Until recently (sorry not sure when regression
Package: linux-2.6
Version: 2.6.38-5
Severity: normal
The Acer Aspire One netbook has two card readers, left right.
Until recently (sorry not sure when regression happened) hotplugging
the right hand card worked. But now such a card is only seen
on cold boot.
I am reporting on a system which
Package: offlineimap
Version: 6.3.3-3
Severity: important
offlineimap fails to update local INBOX: traceback:
==
* Processing account ntlspam
Copying folder structure from Gmail to Maildir
Establishing connection to
on the upstream mailing list where I
see that bug 626417 is almost certainly the same problem.
Turning off -1 to stop most multithreading cures the problem here,
so I suspect a race condition exposed in 6.3.3-3 which maybe was
hidden in earlier versions.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist
)
===
So it nows looks as if there is a udev problem on the amd64 system since
things seem to work on i386. I will try and find time to dig deeper into
this as time permits.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
-0:1
- ../../sdd
lrwxrwxrwx 1 root root 10 May 1 16:09
usb-MStar_Semiconductor__Inc._Mass_Storage_Device_14273211-1575-4252-9161-419514811863-0:1-part1
- ../../sdd1
===
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
small touchpad
on a netbook. I know that others have found such examples helpful:
they have emailed me about getting touchpads working.
Thanks for the help. I will now close this bug.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Package: xserver-xorg-input-synaptics
Version: 1.4.0-1
Severity: important
After the recent testing upgrades, my Synaptics configuration specified
in my xorg.conf:-
--
Section InputClass
Identifier SynPS/2 Synaptics TouchPad
to reboot :-)
I am now trying to find where
InputClass evdev touchpad catchall
and
InputClass touchpad catchall
are defined and whether these are the root cause of the problem.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Fri, Apr 29, 2011 at 09:46:53PM +0200, Julien Cristau wrote:
On Fri, Apr 29, 2011 at 20:03:38 +0100, ael wrote:
Package: xserver-xorg-input-synaptics
Version: 1.4.0-1
Severity: important
After the recent testing upgrades, my Synaptics configuration specified
in my xorg.conf
I have just discovered /usr/share/X11/xorg.conf.d/50-synaptics.conf
I hadn't seen any documenataion of these new configuration files :-(
Moving 50-synaptics.conf out of the way changes things: the touchpad
is now configured in some as yet unknown way. It is far too sensitive
and is almost
On Fri, Apr 29, 2011 at 10:06:55PM +0200, Julien Cristau wrote:
On Fri, Apr 29, 2011 at 20:57:14 +0100, ael wrote:
I tried adding
Option Device/dev/input/event10
into xorg.conf in the hope that it would ensure that the
configuration would be applied to the touchpad alone
On Fri, Apr 29, 2011 at 10:41:26PM +0200, Julien Cristau wrote:
On Fri, Apr 29, 2011 at 21:36:25 +0100, ael wrote:
Ok. I saw the MatchIsTouchpad in 50-synaptics.conf and was about to
look at the man page. I guess these are new parameters since I
last read the man page.
So you added
release. I confirm that NoAccel appears to fix the
problem on 1:0.0.16+git20101210+8bb8231-2. Although the non accelerated
version is very painful compared to nv :-( .
Will test unstable version later today, I hope.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Turning off acceleration fixes the problem as with the earlier
version.
I will report upstream when I have read about their tracking system
Thanks for the help,
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
is talking to a kernel
which is not configured for the right version, it is a tall order for
it to diagnose that that is the problem.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I was at when I reported
the bug: I confess that I had forgotten about the report.
Maybe I had something wrong in the kernel configs, but I doubt it.
As noted above, I only had version 4 configured in one of them:
might that have upset the negotiation/default somehow?
ael
--
To UNSUBSCRIBE
Acquire::cdrom::AutoDetect false;
fixed it here as well. Thanks. Sorry for long delay: maybe I wasn't
subscribed, but I didn't see your response before.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: apt
Version: 0.8.0
Severity: important
Since testing update to 0.7.97.1, apt-cdrom -m add has ceased to work.
Example: with debian-testing-i386-DVD-1.iso mounted on /dvd:
/dev/loop3 on /dvd type iso9660 (rw,loop=/dev/loop3)
running apt-cdrom -m add gives:
install the package;
you should find them in /usr/lib/grub-rescue/, and the documentation in
/usr/share/doc/grub-rescue-pc/README.Debian should work.
Just checked on one machine and indeed the files are there...
Apologies if I somehow missed them.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist
Trackball configuration moved from hal to udev, but with
xserver-xorg-core version 1.76-2 it has moved back to xorg.conf.
To help others with similar track balls, here are InputClass clauses
which work with a range of Logitech trackballs. Of course, you may want
to modify the details according to
, and I imagine that I will need to do the same for a
Synaptics touchpad on a netbook.
To save others the time and trouble, I am happy to make them available
to others. I could add them to an existing bug (probably the one on
trackballs). Or should they appear as examples in one of the packages?
ael
(ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event*, GOTO=xorg_marble_end
#ENV{ID_PATH}!=platform-i8042-serio-1, GOTO=xorg_marble_end
# Above for PS/2, misses USB. name below seems to be enough
ATTRS{name}==ImExPS/2 Logitech Explorer Mouse, GOTO=marbles
ATTRS{name}==Logitech USB Trackball
correlation with the spurious interrupt message, I doubt that I
have enough information to make a useful bug report. And I should
probably try with the latest git kernel before reporting. So it may take
a while
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
: 1
MIS: 0
ael
--
- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG
I have just observed a correct boot (keyboard working), but with
the atkbd.c Spurious ACK ... present in /var/log/messages.
So this is much less clear than I thought.
I have a good and bad versions log /var/log/messages am now
wondering on how to best compare them. I need to look into a diff
, all these things
work.
So the mini version is broken?
ael
---
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.33 (PREEMPT)
Locale
is deprecated. Mode %d isn't recognized.
Use set gfxpayload=WIDTHxHEIGHT[xDEPTH] before
linux command instead.\n,
and so on
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
this package contains no binaries, no images, and not even a hint
about how to create rescue images or media. So it has no purpose as it
stands. Just adding a simple example of how to create rescue floppy and
one for a rescue iso would mean it has some use.
ael
Package: grub-rescue-pc
Version: 1.98-1
Severity: minor
packags description says:
This package contains two GRUB rescue images that have been built for
use with traditional PC/BIOS architecture:
- grub-rescue-floppy.img: floppy image.
- grub-rescue-cdrom.iso: El Torito CDROM image.
is broken?
Using --force did however work: I can't see why blocklists should
not be safe on a ro boot rescue floppy?
There needs to be a note, perhaps along the above lines, on how to
produce a floppy image.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
-
So yes, this bug needs to be re-opened a mechanism to flag whether or
not extlinux is booting the host system needs to be introduced.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: linux-2.6
Version: 2.6.32-9
Severity: important
File: linux-image-2.6.32-3
# dpkg -i /var/cache/apt/archives/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
(Reading database ... 231498 files and directories currently installed.)
Preparing to replace linux-image-2.6.32-3-amd64 2.6.32-9
Package: extlinux
Version: 2:3.85+dfsg-1
Severity: important
Please see bug 573962 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573962
which perhaps should have been transferred to to extlinux rather than
closed...
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
extlinux. Even after purging that
package /etc/kernel/postrm.d/extlinux remained! I had to manually
delete it.
I was not actually using extlinux to boot the host system.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
bug, purging extlinux did not remove the script
(which was a symbolic link), so maybe it was some historical relic which
might not recur.
I will try find time tomorrow to make the test...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
the GUI and you go through the process, you will get
Ok, but it was not documented anywhere that I found.
PS I'm not the firestarter package maintainer
So the lack of documentation isn't your fault :-) Thanks for the reply.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
On Sat, Mar 06, 2010 at 01:05:00PM +0100, Brice Goglin wrote:
ael wrote:
I could send my rules if it would be useful.
Yes, please, it could help some people, especially the submitter.
In my quick reply, I hadn't noticed that this was a bug report. My working
udev rules are already
gnumeric 1.10.0-1 from unstable fixes this problem, so perhaps this bug
can be closed.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: gnumeric
Version: 1.9.17-1
Severity: grave
Justification: renders package unusable
==
$gnumeric xxx.gnumeric
gnumeric: error while loading shared libraries:
libgoffice-0.8.so.7: cannot open shared object file: No such
/deadlock. Maybe the hardware
itself latched up somehow: it certainly looks like something of that
sort.
So I suggest that this bug is closed: if it happens again, I can reopen.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Package: gpm
Version: 1.20.4-3.3
Severity: important
This update to gpm has broken my mouse support.
gpm seems to load (although initialy I saw crashes).
It seems to run as
gpm -m /dev/input/mice -t exps2
taken from /etc/gpm.conf. (It is hard to write this with no cut paste)
Package: offlineimap
Version: 6.2.0+nmu2
Severity: normal
I encountered the bug reported at:-
http://software.complete.org/software/issues/show/197
The fix there solved the problem. So the debian package needs updating?
-- System Information:
Debian Release: squeeze/sid
APT prefers
of problem negotiating the nfs version
between the client server? And a totally misleading error message?
ael
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32 (PREEMPT)
Locale: LANG=en_GB.UTF-8
-trackball.rules
Here are the contents:
-
# Logitech Marble Mice PN 804377-, PN 810-000767 or
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event
or
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event*, GOTO=xorg_marble_end
#ENV{ID_PATH}!=platform-i8042-serio-1, GOTO=xorg_marble_end
# Above for PS/2, misses USB. name below seems to be enough
ATTRS{name}==ImExPS
.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: firestarter
Version: 1.0.3-8
Severity: grave
Justification: renders package unusable
-
Installing firefighter from aptitude:-
===
Unpacking firestarter (from .../firestarter_1.0.3-8_i386.deb) ...
Package: network-manager
Version: 0.7.2-2
Severity: wishlist
network-manager pulls in dhcp3-client dhcp3-common which are
unneccessary when static IPs are used.
So it becomes impossible to have a slim efficient installation
on light weight machines. Perhaps a meta-full package might be needed
on the earlier
dvds is cached somewhere: the dvd is changed, and when that cached path
is used later, it is, of course, no longer valid.
This bug would seem to make debian installation from multiple DVDs
nearly impossible: so pretty serious for those without high
bandwidth connections.
ael
.
Will experiment more later today: I ought to try the whole thing with
ext3 and see if I get swap partition problems again.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
no wasted space with partman,
so simply guess sizes.
The installation then completed without problems - using ext3.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
301 - 400 of 491 matches
Mail list logo
