mp/fmtutil.isqbK6Rx
> Please include this file if you report a bug.
Confirmed. I am seeing this on my testing boxes.
ael
Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-1
Severity: serious
Justification: 4
In the last week or so, offlineimap is usually (but not always)
failing to connect to outlook.office365.com
reporting:
$ offlineimap -a x
OfflineIMAP 8.0.0
Licensed under the GNU GPL v2 or any
was already installed
on devuan live image.
Thanks for the help. I will keep watching this thread.
ael
On Tue, Oct 05, 2021 at 10:27:58AM +0100, ael via sane-devel wrote:
> On Mon, Oct 04, 2021 at 08:39:58PM +0100, ael via sane-devel wrote:
> > On Mon, Oct 04, 2021 at 05:32:29PM +0200, Wolfram Sang wrote:
> > > There is a PPA with the latest development version here if you want t
On Mon, Oct 04, 2021 at 08:39:58PM +0100, ael via sane-devel wrote:
> On Mon, Oct 04, 2021 at 05:32:29PM +0200, Wolfram Sang wrote:
> > There is a PPA with the latest development version here if you want to
> > test right away:
> >
> > https://launchpad.net/~sane-proje
ndency problems prevent configuration of sane-utils:
sane-utils depends on libjpeg8 (>= 8c); however:
Package libjpeg8 is not installed.
libjpeg8 doesn't seem to be in debian...
ael
kends/-/commit/580c278dcafe4159213406b4307ee8598fe08f
e7
"
This is on the sane-devel list: sane-de...@alioth-lists.debian.net
ael
ngs: "Focus on glass" or "Focus on film". That is from memory,
but something close to that. SO perhaps this old model had just
a binary switch for two focus positions, and the epson backend
has been broken by assuming that this model has more focus facilities.
So far this is pure speculation on my part.
ael
used the simplest defaults I think.
In my history I just have
cmake ../navit/
make maptool
Does that tell you what you need to know?
ael
by
> compiling maptool from the git repo. What compilation flags did you
> use?
I used
./maptool --protobuf -i
/ssdback1/ael/mapping/mkgmap/great-britain-latest.osm.pbf test.bin
inside my local navit_build directory where I compiled maptool.
Many warnings and such scrolled past on the sc
On Sat, Jan 25, 2020 at 05:44:47PM -0800, Joseph Herlant wrote:
> Hi,
>
> On Fri, Jan 24, 2020 at 2:00 PM ael wrote:
> > Package: maptool
> > Version: 0.5.3+dfsg.1-2+b1
>
> Please try with the 0.5.4 version currently in unstable as here have
> been a lot of chan
at the issues with navit on wince:
see https://github.com/navit-gps/navit/issues/953#issuecomment-578313710
Search down that page to see the problem with the Debian testing
maptool:
maptool --protobuf -i
/ssdback1/ael/mapping/mkgmap/great-britain-latest.osm.pbf test.bin
but that SEGFAULTED almost
debian testing.
4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-11-02) x86_64 GNU/Linux
Package: synaptic
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 7810
Maintainer: Michael Vogt
Architecture: amd64
Version: 0.84.5
ael
Package: nfs-common
Version: 1:1.3.4-2.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since upgrading testing today ( 1:1.3.4-2.2 ) mount.nfs fails to mount
at least two other filesystems on other debian machines, also running
testing, and also upgraded today.
dmesg
Removing the slim package solves the problem, so slim seems to be the
culprit.
Package: slim
Version: 1.3.6-5
Severity: critical
Justification: breaks the whole system
I am not sure that this is a slim problem, but as the system is almost
unusable, I cannot investigate.
After an apt-get upgrade earlier today, the system presents a new slim
login page. Logging in works, but
On Fri, Jul 31, 2015 at 11:15:06PM +0200, Michael Biebl wrote:
Control: tags -1 moreinfo
Am 31.07.2015 um 20:57 schrieb ael:
Package: systemd
Version: 221-1
Severity: critical
Justification: breaks the whole system
I had to select the sysvinit option from the grub menu in order
Package: systemd
Version: 221-1
Severity: critical
Justification: breaks the whole system
I had to select the sysvinit option from the grub menu in order to
achieve a boot. The standard menu entry got as far as (probably) trying
to spawn X, and then hung. But it had no business doing that because
impossible.
One worked round, data seems not to be handled correctly.
I think josm-latest was last working in mid October.
ael
-
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing
to try to understand
how the error arises.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
gnumeric 1.10.0-1 from unstable fixes this problem, so perhaps this bug
can be closed.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-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
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) ...
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
For the record, after replacing drives *and* cables, the problem
persists. I can only assume that it is the controller after all :-(
I think I will live without a floppy on that particular box.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 7
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 8
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 9
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: a
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: c
6: 2
no disk change
ael
--
To UNSUBSCRIBE, email
for an hour or more, so can't report immediately.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
: 11
5: 12
5: 1
5: 2
5: 3
5: 6
5: 7
5: 9
5: a
???
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
sheet
and have only skimmed small portions, so I have some catching up to do...
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Alain Knaff wrote:
ael wrote:
Mark Hounschell wrote:
On 12/15/2009 10:08 AM, Alain Knaff wrote:
I mentioned I had multiple machines with this problem. Some running
different versions of SuSE. Mainly 11.0, which is where all the info
I've provided came from thus far. This machine also has
: 9
5: a
5: b
5: d
5: e
5: f
5: 10
5: 11
5: 12
5: 1
5: 2
5: 3
5: 4
5: 8
5: 9
5: a
5: b
5: c
5: d
5: e
5: f
5: 10
Is that what you wanted?
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
A.E.Lawrence wrote:
# fdrawcmd read 0 0 0 1 2 18 1 1 length=18432 /dev/null
remaining= 17920
0: 40 == So this is Abnormal termination?
1: 20 == CRC error? (id or data)
2: 20 == CRC error? (data)
Did I decode them correctly?
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
Alain Knaff wrote:
A.E.Lawrence wrote:
Alain Knaff wrote:
ael wrote:
Is that what you wanted?
ael
Yes. All sectors are there, ... so I wonder why you are getting errors.
So, next round of tests: trying to read these sectors:
fdrawcmd recalibrate 0
fdrawcmd read 0 0 0 1 2 18 1 1 length
sector= 17
remaining= 0
0: 44
1: 20
2: 20
3: 0
4: 1
5: 11
6: 2
no disk change
sector= 18
remaining= 0
0: 44
1: 20
2: 20
3: 0
4: 1
5: 12
6: 2
no disk change
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
, fdformat worked without problems on one i386
machine, but failed in the usual way on another.
My next message will report the results of Alain's test on the failing
machine.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Alain Knaff wrote:
Mark Hounschell wrote:
[...]
All kernels below 2.6.28 work on these boxes. All kernels 2.6.28 and higher do
NOT.
2.6.28 was when support for sector bases other than 0 or 1 were
introduced. So, rather than have sectors numbered from 1 to 18, you can
now have sectors
ael wrote:
Alain Knaff wrote:
then do a getfdprm -o /dev/fd0u1440 (or getfdprm /dev/fd0)
I should have mentioned that my tests were done under the current git
kernel:
# uname -a
Linux exact 2.6.32_exact-55846-gf405425 #194 Sun Dec 13 16:30:46 GMT
2009 i686 GNU/Linux
ael
Alain Knaff wrote:
On 14/12/09 12:27, ael wrote:
# getfdprm -o /dev/fd0u1440
2880 18 2 80 0 0x1b 0x00 0xcf 0x6c
# fdrawcmd drive=/dev/fd0u1440 readid 0 repeat=18
raw cmd: Invalid argument
... and if you try with /dev/fd0 instead?
Yes. I tried all the obvious things. The man/info page
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid argument
issue.
Ok, Will try and fit it in later today. Meanwhile, what exactly is the
command line that should work? The one you suggested
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid argument
issue.
Looks as if that was something to do with my command line. Below is the
strace giving the IO error which probably isn't much
Alain Knaff wrote:
On 14/12/09 16:24, ael wrote:
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid
argument
issue.
Looks as if that was something to do with my command line. Below
Just a note for anyone who comes across this report: it seems that
the problem is also occurs on SuSE, 10.3-11.2 -
Any kernel at or above 2.6.28 fails to fdformat a floppy.
That has been reported on the fdutils list and now there is a thread on
the kernel mailing list.
ael
installing a new drive 0 or floppy controller.
Not enough raw space on this disk for this format
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I just retested fdformat and superformat on one of the machines
with current testing and kernel 2.6.32 .
fdformat fails in usual way as previously reported.
superformat also fails, but maybe this result gives a clue:-
#
first reports that a member of my
local LUG had tested on Gentoo and had no problems with the same kernel.
It seems to be something specific to Debian which is extremely odd,
given you have tested on ubuntu.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
Alain Knaff wrote:
On 10/11/09 17:42, ael wrote:
I tried setting the density to dd instead of hd -- something that I
had also tried on fdformat without success. gfloppy managed to
Sorry. I think I should have posted more about that, but the report was
so long already that I held back.
I
involved in formatting, I know.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
was installed on 29-10-09.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
perhaps this report should
be re-assigned?
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
is involved after
all.
This under kernel 2.6.32-rc6. Has the floppy API been changed, perhaps?
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: xserver-xorg-input-joystick
Version: 1:1.4.1-1
Severity: grave
Justification: renders package unusable
Log file covers everything, I think:-
X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11,
synaptic installs packages from dvds without problems. Perhaps this bug
should be re-assigned back to aptitude?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I spoke too soon - in my last report.
The same problem (sometimes) happens in synaptic.
I guess means that the problem lies at a lower level than either synaptic or
aptitude.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
In my continuing attempts to pin this bug, I have rebuilt dpkg and apt
from sources with nostrip, but aptitude-0.4.11.11 does not rebuild
on current testing. I guess I could try 0.6.1-1 from sid or maybe
aptitude-dbg.
It seems as if apt-get no longer has problems installing from /dvd - I
haven't
when the dvds are not used, so it is not
easy to correlate the last segfault with any particular package update.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Continuing.
Program exited normally.
(gdb) q
===
So 0.7.21 seems not to give the segfault, but still has problems. Or
it is in another package
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
Just realised that my last report was run on 0.7.23.1 instead of 0.7.21 :-)
Working too long on this :-( Will try again tomorrow on he right version...
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
this problem, or is it unusual to get files from
/dvd rather directly from the network?
I will update my machine back to current testing for the moment before
my dependencies get into a nasty twist!
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
perhaps no
connection, although even then a segfault obviously isn't exactly
desirable :-(
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
And there is another presumbly related bug present as well
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sorry, had overlooked the request to try 0.7.21. but I think apt 0.7.23.1
was installed during the segfaults. Will try soon.
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
running aptitude or apt-get. It will take me a while to
work out how to get those things installed, I suspect...
ael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Tried unstable version of apt: Package: apt, Version: 0.7.24. Problem
still present:
kernel: cdrom[12053]: segfault at 200 ip b786771d sp bfda3c10 error 4 in
ld-2.9.so[b7854000+1c000]
Oct 9 12:54:04 conquest3 kernel: cdrom[12061]: segfault at 200 ip
b780a71d sp bfe3c510 error 4 in
Daniel Burrows wrote:
# ps -C cdrom
PID TTY TIME CMD
5845 pts/000:00:00 cdrom
conquest3:~# gdb aptitude 5845
You'll probably have better luck if you debug /usr/lib/cdrom instead
of aptitude. :) I don't know if that'll help much, though; it doesn't
have debugging symbols
Package: aptitude
Version: 0.4.11.11-1+b2
Severity: grave
Justification: renders package unusable
For over a month now (presumably since the last aptitude upgrade on testing)
I have been seeing segfaults recorded in /var/log/messages on two i386 boxes
and on an amd64, all running testing.
I
Subject: fdutils: fdformat fails under current kernel(s)
Package: fdutils
Version: 5.5-20060227-3
Justification: renders package unusable
Severity: grave
*** Please type your report below this line ***
fdformat fails completely on current kernels.
example: (retyped by hand ,so typos possible...)
Package: grub-rescue-pc
Version: 1.97~beta3-1
Severity: critical
Justification: breaks the whole system
$ ls -lh /usr/lib/grub-rescue/grub-rescue-floppy.img
-rw-r--r-- 1 root root 1.5M 2009-09-12 17:07
/usr/lib/grub-rescue/grub-rescue-floppy.img
A standard floppy is 1.44M, so
calls are working (echo tests ok), so
maybe it is harmless.
So what is bug now? Is it that upon changing version, ekiga should be
started twice?
As above, I think it is just a reference to the upstream bug. Perhaps it
should stay open until the upstream bug is closed?
ael
Package: ekiga
Version: 3.2.1~git20090515.9d0263-1
Severity: grave
Justification: renders package unusable
Ekiga 3.2.1 cannot register with my several sip providers.
The accounts window shows: Could not register (Timeout)
Using another machine running ekiga 2.0.11 IIRC on the same network and so
Package: policykit-gnome
Version: 0.9.2-2
Severity: grave
Justification: renders package unusable
Very like bug #523646 with a seg fault:
$ polkit-gnome-authorization
[WARN 12025] polkit-error.c:143:polkit_error_get_error_message(): error != NULL
Not built with -rdynamic so unable to print a
72 matches
Mail list logo
