Package: empathy
Version: 3.2.2-1+b3
Severity: normal
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Running aptitude safe-upgrade left the pidgin packages in the former
state. Trying to upgrade it
Am -10.01.-28163 20:59, schrieb Davide Prina:
I'm behind a proxy server with password.
I have configured eclipse to use the proxy server for http, https and socket.
To let eclipse to work correctly with update/install you must not set
proxy for socket.
Being in a similar situation this solved
Hello,
we found the bug to be fixed with lcov-1.9 from
ltp.sourceforge.net/coverage/lcov.php which is not in debian yet.
Please, re-assign to lcov.
Best regards, Alexander.
smime.p7s
Description: S/MIME Cryptographic Signature
Hello,
apparently the default encryption in cryptsetup changed with some
update. After adding cipher=cipher to /etc/crypttab the cryptsetup
worked correctly.
The kernel module error message remains but that's not important for me
any more :-)
I beg your pardon for bothering you, many
Hello,
please, change severity from minor to important as the cryptdisk
start-up failure imposes a real problem.
If any additional information is needed I will try to provide it.
Best regards,
--
Alexander Mader alexander.ma...@niles.de
--
To UNSUBSCRIBE, email to
8-- 8
On Mon, 2010-02-01 at 20:23 +, Julian Gilbey wrote:
Package: linux-image-2.6.32-trunk-amd64
Version: 2.6.32-5
Every time I boot - and I'm using crypto file systems - I get the
series of messages (copied from
Hello Cyril,
some more remarks ;-)
Am 20:59, schrieb Mader, Alexander (N-MSR):
The configuration is as described in
http://...
The configuration is archived in the first email of this bug report as well.
The restart with the upgraded packages gave me the GDM login screen. I
was able
Am 10.03.2010 09:18, schrieb Mader, Alexander:
Would effectively separating the input devices allow distinct logins again?
If so, how could I achieve this?
I will try Auto[Add|Enable]Devices asap.
--
Alexander Mader
smime.p7s
Description: S/MIME Cryptographic Signature
Hello,
now some details. As mentioned I did an upgrade and just restarted the
system. The configuration is as described in
http://lists.freedesktop.org/archives/xorg/2008-October/039421.html
and worked with the packages on hold together with the respective latest
2.6.32-kernel (currently
Hello,
attached you will find the example code I mentioned in the bug report.
Just unpack and type make clean;make from the top project directory.
Best regards, Alexander.
LcovTst.tar.bz2
Description: Binary data
smime.p7s
Description: S/MIME Cryptographic Signature
JetWhiz schrieb:
What exactly did you do to fix this, Alexander? My apt is hosed by this
same issue right now.
Perhaps I suffered from some other issue. I had safe-rm installed where
/usr/bin/rm is a symbolic link to /usr/bin/safe-rm which is a perl
script. So I just removed the link
Hello,
although #550946 is merged with this bug I re-post my observations with
safe-rm to have the information in this bug report:
*Both* during *and* after the perl-upgrade to 5.10.1-5 safe-rm produced
messages like this:
8
Do you have liblocale-gettext-perl 1.05-5 installed? If so, upgrading
it to 1.05-6 should help.
Hello,
as you can see the version mentioned is installed:
8 --- 8
:~# aptitude show liblocale-gettext-perl
Paket: liblocale-gettext-perl
Hello,
the culprit was:
safe-rm
which is an perl script itself and apparently prevented perl paths from
deletion. After replacing it by the original rm (/bin/rm not
/usr/bin/rm) the upgrade succeeded.
I beg your pardon for the fast cry in the first place :-)
Best regards,
--
Alexander
Let's try some simple and stupid debugging. Somebody who can reliably
reproduce the problem please add something like this to the *end* of
/lib/udev/rules.d/85-hwclock.rules :
KERNEL==rtc0, RUN+=/bin/touch /dev/rtc0-appeared
KERNEL==rtc0, RUN+=logger.agent
Hello,
I did try it and it was
LaMont Jones schrieb:
On Mon, Oct 05, 2009 at 08:04:23AM +0200, Mader, Alexander (N-MSR) wrote:
Something additional: I am running a Debian kernel not a self built one,
and /lib/udev/rules.d/85-hwclock.rules was not there in the first place
so I had to create it.
That file is delivered
Hello,
some additional information as far as I could gather.
I put some echo lines into hwclockfirst.sh so I could see that
hwclockfirst.sh is called *before* the fsck complains and seems to work
properly: Because /dev/.udev exists no actual call to hwclock is made in
the script, anyway.
Hello,
unfortunately, I am experiencing the same behaviour with my laptop. On
my differently configured desktop computer there is no such problem,
which I tend to blame to the different UTC setting. Hopefully, the
following information on the two systems will help.
Best regards, Alexander.
Emilio Pozuelo Monfort schrieb:
This is fixed in the experimental package by loading libpython2.5.so.1. As the
changelog entry says, that's an ugly workaround, but it's probably better than
depending on python-dev and bringing a lot of dependencies.
I've backported this patch to the unstable
Hello,
attached you'll find the promised files.
Pls, let me mention that I read the reports #454163 and #454164.
Best regards,
--
Alexander Mader [EMAIL PROTECTED]
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration
Hello,
attached you'll find the promised files.
Pls, let me mention that I read the reports #454163 and #454164.
Best regards,
--
Alexander Mader [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kel Modderman schrieb:
This was crappy snapshot of SVN, see the same ticket for more details.
Hello,
I tried
http://snapshots.madwifi.org/special/madwifi-r2651-no-preemptscan.tar.gz
and apparently get the same phenomenon as described in the beginning:
Our DHCP server answers but my machine
Kel Modderman schrieb:
Sorry for period of silence.
No problem at all. Thanks for answering :-)
I'd say it is related to #403933 and http://madwifi.org/ticket/275.
This is obviously an upstream problem than but I send this to debian and
you anyway, as you most probably communicate the right
23 matches
Mail list logo
