Bug#917638: SOLVED. I am awfully sorry (Was: Bug#917638: infnoise: Job dev-infnoise.device/start failed with result 'timeout')

Gegen 21:31 des 01.01.19 verlautete von Stephen Kitt: That suggests something wrong with the device :-(. Does it show up when you run lsusb? Mine shows Bus 001 Device 039: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO) Hello Stephen, I really beg your

Bug#917638: infnoise: Job dev-infnoise.device/start failed with result 'timeout'

Package: infnoise Version: 0.3.0+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, thank you for providing infnoise! Unfortunately, the infnoise service does not start due to the dev-infnoise device not starting in turn. I picked the latest version from the

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

Am 27.02.2016 um 10:01 schrieb Mader, Alexander: > On Fri, 26 Feb 2016 23:45:01 +0100 "Mader, Alexander" wrote: >> On Mon, 22 Feb 2016 18:19:58 + Chris Boot wrote: >>> Adding "rootdelay=15" to the kernel command-line probably fixes this >>> (can

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

On Sat, 27 Feb 2016 10:01:21 +0100 "Mader, Alexander" <auma...@gmx.net> wrote: > On Fri, 26 Feb 2016 23:45:01 +0100 "Mader, Alexander" <auma...@gmx.net> > wrote: > > On Mon, 22 Feb 2016 18:19:58 + Chris Boot <bo...@debian.org> wrote: >

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

On Fri, 26 Feb 2016 23:45:01 +0100 "Mader, Alexander" <auma...@gmx.net> wrote: > On Mon, 22 Feb 2016 18:19:58 + Chris Boot <bo...@debian.org> wrote: > > Adding "rootdelay=15" to the kernel command-line probably fixes this > > (can't test

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

On Mon, 22 Feb 2016 18:19:58 + Chris Boot wrote: > Adding "rootdelay=15" to the kernel command-line probably fixes this > (can't test as we can't just reboot this production server at will) but > this isn't a nice fix. Hello, I just tried "rootdelay=15" as well as

Bug#675146: Empathy blocks Pidgin upgrade

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

Bug#636136: Re: [solved] update system is not working

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

Bug#610958: Multiseat: Gimp select rectangle crashes X (Single Seat: OK)

Am 24.01.2011 13:43, schrieb Julien Cristau: On Mon, Jan 24, 2011 at 13:10:02 +0100, Mader, Alexander wrote: Backtrace: Oh, sorry, forgot the dbg-backtraces; attached now. Best Regards, Alexander. Continuing. Program received signal SIGPIPE, Broken pipe. 0x7f8999a0b040

Bug#569984: Pls, re-assign to lcov

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

Bug#568008: Resolved for me (Was: Re: Bug#568008: ...)

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

Bug#568008: unusable cryptdisks means an important bug

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

Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device

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

Bug#546586: Re: Bug#546586: xorg: X server lockup in int10 when booting a secondary card

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

Bug#546586: xorg: X server lockup in int10 when booting a secondary card

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

Bug#546586: xorg: X server lockup in int10 when booting a secondary card

Hello Cyril, with AutoEnableDevices false the first test with two real seperate logins was successful :-) I still need the dummy X server started first as it seems and stability is not tested yet ;-) As for the int10 problem I would consider the issue as fixed :-) Many thanks for maintaining X

Bug#546586: xorg: X server lockup in int10 when booting a secondary card

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

Bug#546586: xorg: X server lockup in int10 when booting a secondary card

Cyril Brulebois schrieb: Julien Cristau jcris...@debian.org (14/09/2009): This will hopefully be fixed using kernel 2.6.32 and xorg-server 1.7. any news about that? Hello Cyril, right after reading your email yesterday evening I upgraded all the packages on hold: [HALTEN, ABHÄNGIGKEITEN]

Bug#569984: Code to reproduce problem

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

Bug#543375: initscripts: last superblock write time in future

Tomasz Grzelak schrieb: what is the status of the case - am I the only one experiencing the problem still? Is there anyone affected by this even with the new version of util-linux 2.16.1-4? As mentioned in an earlier e-mail everything works fine since I edited the hwclock-udev-rule as decribed

Bug#550825: Resolved: Unable to upgrade perl

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

Bug#550938: safe-rm not working any more with perl 5.10.1-5

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

Bug#550825: Unable to upgrade perl

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

Bug#550825: Resolved: Unable to upgrade 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

Bug#543375: initscripts: last superblock write time in future occurring sometimes

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

Bug#543375: initscripts: last superblock write time in future occurring sometimes

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

Bug#548623: Resolved: gnumeric: symbol lookup error

Hello, thanks a lot for providing the fix: 1.9.13-1 from unstable resolves the problem. Thanks again! Alexander. -- Alexander Mader auma...@gmx.net GPG public key:http://mader.seppi.de/pubkey-privat.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with

Bug#546586: xorg: X server lockup in int10 when booting a secondary card

Subject: xorg: X server lockup in int10 when booting a secondary card Package: xorg Version: 1:7.4+4 Severity: important Hello, I just run aptitude upgrade and my multiseat setup isn't working any more. The experience is as described in freedektop.org bug 18160. I would prefer helping with a

Bug#543375: Superblock last mount time is in the future

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.

Bug#543375: Superblock last mount time is in the future

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.

Bug#488760: Failed to start: Try to load non-existent libpython2.5.so

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

Bug#454467: Files and related reports

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

Bug#454467: Files and related reports

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]

Bug#432284: No DHCP for encrypted network

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

Bug#432284: No DHCP for encrypted network

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

Bug#325512: clamav-freshclam: Failed stop for init-script

Stephen Gran schrieb: Can you try 0.87-1 and let me know if you are still having this problem? I have revamped the init scripts to use lsb functions since then, and it may have better kill handling. Hello Stephen, many thanks for your email. I didn't find a 0.87-1-deb that fast and so I

Bug#314439: mozilla-thunderbird: activity bar during folder open exceeds its limits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Sack schrieb: I assume that you are using gnome ... right? What are your theme settings? Hello Alexander, the reported situation occurs with Mist -- A minimalistic interface; with Simple, Amaranth, Clearlooks, Crux, Default, Glider,

Bug#314439: mozilla-thunderbird: activity bar during folder open exceeds its limits

Alexander Sack schrieb: Maybe you can manage to take a screenshot of it? Hello, see the attached ones. Best regards, Alexander. -- Alexander Mader [EMAIL PROTECTED] Fon: +49-30-93033-636 NILES Werkzeugmaschinen GmbHFax: +49-30-93033-603