Bug#444643: Further testing
Hi Modestas Thanks for the info. I use Xfce now. I'll check if Amarok 2 supports iPods, if it does, I'll try it. Did you try it? :) Yes, I did try it, and it does support well my iPod 80GB. I tried Amarok 2 for about a month but it didn't feel comfortable enough with my large collection (around 500GB of MP3 files) so I fell back to Amarok 1.4. I've been watching Amarok's blog closely and will give it another try when I feel Amarok 2 looks ripe enough. Thanks for your interest ! Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582409: soundkonverter: decoders for ape and flac files are not recognized
Package: soundkonverter Version: 0.9.90-1 Severity: important Hello soundkonverter doesn't recognize the decoders for flac and ape files, installed from these packages: ii flac1.2.1-2+b1 ii monkeys-audio 3.99-u4-b5-0.1 It stopped recognizing them after it was converted to KDE4. The version from lenny (0.3.8-2), for KDE3, recognizes correctly these decoders. soundkonverter is undoubtedly the best audio conversion utility I have ever used, and I have been using it very heavily on a daily basis, but this renders it practically unusable. Thanks Paulo -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (700, 'unstable'), (500, 'experimental'), (400, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages soundkonverter depends on: ii kdelibs4c2a4:3.5.10.dfsg.1-3 core libraries and binaries for al ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcdparanoia0 3.10.2+debian-9 audio extraction tool for sampling ii libgcc11:4.4.4-1 GCC support library ii libqt3-mt 3:3.3.8b-6Qt GUI Library (Threaded runtime v ii libstdc++6 4.4.4-1 The GNU Standard C++ Library v3 ii libtag1c2a 1.6.2-1 TagLib Audio Meta-Data Library Versions of packages soundkonverter recommends: pn cdda2wav none (no description available) ii cdparanoia 3.10.2+debian-9 audio extraction tool for sampling pn faad none (no description available) pn ffmpeg none (no description available) ii flac 1.2.1-2+b1 Free Lossless Audio Codec - comman pn kdemultimedia-ki none (no description available) pn mp3gain none (no description available) ii mplayer 2:1.0~rc3+svn20100502-2 movie player for Unix-like systems pn mppenc none (no description available) pn speexnone (no description available) pn timidity none (no description available) ii vorbis-tools 1.4.0-1 several Ogg Vorbis tools pn vorbisgain none (no description available) pn wavpack none (no description available) Versions of packages soundkonverter suggests: pn soundkonverter-amarok none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444643: Further testing
Hi Modestas ! Sorry, but Amarok 1 is unmaintained with the exception of security bugs. And I don't own iPod, I cannot do anything about this bug even if I wanted... Upstream stopped caring about 1 series even before lenny was released. It is (slowly) getting better... 2.2 is already configurable extensively. Thanks for the info. I use Xfce now. I'll check if Amarok 2 supports iPods, if it does, I'll try it. Regards, Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444643: Further testing
Hi Modestas Please retest with Amarok 2.1.1. Since I'm tracking stable now, I'm stuck with Amarok 1.4.10, can't retest as requested. Still use Amarok to manage my iPod but gave up on lyrics when I noticed the bug wasn't touched by anybody. I didn't feel comfortable with KDE 4, even less with Amarok 2. I feel Amarok didn't move forward but backwards instead … So I'll stick with 1.4.10 for now. Regards Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517218: libsane: “scanimage -L” outputs “No scanners were identified”
Hi Evgeni First of all, accept my gratitude for your swift response. On Thu, Feb 26, 2009 at 05:06:37PM +0100, Evgeni Golov wrote: […] When I run “scanimage -L” under user “paulo”, this is the output: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). If I run it under “root”, this is the output: device `hpaio:/usb/PSC_1500_series?serial=BR58R1R0D60498' is a Hewlett-Packard PSC_1500_series all-in-one […] Add the user paulo to the lp group. You have one of those stupid HP all-in-ones which are only reachable as a lp user. At least that helped a friend of mine with a similar hardware. You're right: I'm trying to scan from a HP PSC 1510, one of those «beasts». Did as you told me, added “paulo” to group “lp”, here's the output from running “groups”: paulo adm lp dialout cdrom floppy sudo audio video plugdev staff scanner mldonkey But the problem persists: the device is not identified under “paulo“ but it is under “root”. Browsing /var/log/aptitude, I observed these upgrades to libsane: Feb 17th: 1.0.19-23 - 1.0.19-24 Feb 21st: 1.0.19-24 - 1.0.19-25 I'd risk a guess that I haven't used the scanner since the 1st upgrade, so the problem seems to have crept in at version 1.0.19-24 or 1.0.19-25. Let me know how we can further debug the problem. Once again my sincere thanks for your readiness Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517218: libsane: “scanimage -L” outputs “No scanners were identified”
Hi Evgeni […] Browsing /var/log/aptitude, I observed these upgrades to libsane: Feb 17th: 1.0.19-23 - 1.0.19-24 Feb 21st: 1.0.19-24 - 1.0.19-25 I downgraded all sane-related packages which had been upgraded in February. Here's how they stand now: libsane1.0.19-23 libsane-extras 1.0.19.11 sane-utils 1.0.19-23 But the problem persists … I'm stumped again. Regards Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517218: libsane: “scanimage -L” outputs “No scanners were identified”
Hi Julien On Thu, Feb 26, 2009 at 07:00:09PM +0100, Julien BLACHE wrote: Did as you told me, added “paulo” to group “lp”, here's the output from running “groups”: paulo adm lp dialout cdrom floppy sudo audio video plugdev staff scanner mldonkey If you added your user to one of those groups recently, did you log out and log in again afterwards? This is needed for group membership to take effect. Yes I did. That's why I inserted the current output from running “groups”, as you can see above. Thanks for your speed-lightning reply Paulo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506921: User account wasn't member of group scanner (SOLVED)
Hi ! Apologies for having unnecessarily raised this bug. I have just discovered that the user account trying to scan from the printer needs to be a member of group scanner. If I run now: scanimage -L the output is: device `hpaio:/usb/PSC_1500_series?serial=BR58R1R0D60498' is a Hewlett-Packard PSC_1500_series all-in-one as expected, and I manage to scan from my HP PSC 1510 using xsane. This bug can be safely closed. Regards, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#507058: b43-fwcutter fails to install: input file is wrong
On Thu, Nov 27, 2008 at 04:09:00PM +0100, Rene Engelhard wrote: I'd debug your network connection. Or the file was at some time corrupted on the mirror. Nothing this package can influence. Hey Rene, thank you so much for your speed-lightning reply ! If b43-fwcutter managed to download the files, I assume there's no problem with my network connection, right ? If your install was OK, I assume the files were not corrupted on the mirror. I confess I'm stumped. Not sure if this is relevant, but I checked b43-fwcutter's version with: b43-fwcutter -v and here's the result: b43-fwcutter version 009 Shouldn't it be 011 ? I tried to go through the install manually: 1) Install b43-fwcutter but don't download and extract the firmware 2) Download the file manually: wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 3) Extract it: tar xjvf broadcom-wl-4.150.10.5.tar.bz2 4) Extract the firmware: cd broadcom-wl-4.150.10.5/driver/ b43-fwcutter -w /lib/firmware wl_apsta_mimo.o And the result was exactly the same: Sorry, the input file is either wrong or not supported by b43-fwcutter. This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c. Running b43-fwcutter -l: b43-fwcutter version 009 Extracting firmware is possible from these binary driver files: driverfilename microcode MD5 checksum b43legacy wl_apsta.o 295.14 e08665c5c5b66beb9c3b2dd54aa80cb3 b43 wl_apsta.o 351.126 9207bc565c2fc9fa1591f6c7911d3fc0 b43 wl_apsta_mimo.o 351.126 722e2e0d8cc04b8f118bb5afe6829ff9 And md5sum wl_apsta_mimo.o: cb8d70972b885b1f8883b943c0261a3c wl_apsta_mimo.o I'm really stumped. Would you have any suggestion on how to continue debugging this ? Regards, Paulo I just tried it: [...] Setting up b43-fwcutter (1:011-5) ... --2008-11-27 16:06:31-- http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o Resolving downloads.openwrt.org... 195.56.146.238 Connecting to downloads.openwrt.org|195.56.146.238|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 652866 (638K) [application/x-object] Saving to: `wl_apsta-3.130.20.0.o' 100%[==] 652,866 3.12M/s in 0.2s 2008-11-27 16:06:32 (3.12 MB/s) - `wl_apsta-3.130.20.0.o' saved [652866/652866] --2008-11-27 16:06:32-- http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 Resolving mirror2.openwrt.org... 88.198.39.176 Connecting to mirror2.openwrt.org|88.198.39.176|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3888794 (3.7M) [application/x-tar] Saving to: `broadcom-wl-4.150.10.5.tar.bz2' 100%[==] 3,888,794 4.12M/s in 0.9s 2008-11-27 16:06:33 (4.12 MB/s) - `broadcom-wl-4.150.10.5.tar.bz2' saved [3888794/3888794] This file is recognised as: ID : FW10 filename : wl_apsta.o version: 295.14 MD5: e08665c5c5b66beb9c3b2dd54aa80cb3 Extracting b43legacy/ucode2.fw Extracting b43legacy/ucode4.fw Extracting b43legacy/ucode5.fw Extracting b43legacy/ucode11.fw Extracting b43legacy/pcm4.fw Extracting b43legacy/pcm5.fw Extracting b43legacy/a0g0bsinitvals2.fw Extracting b43legacy/b0g0bsinitvals5.fw Extracting b43legacy/a0g0initvals5.fw Extracting b43legacy/a0g1bsinitvals5.fw Extracting b43legacy/a0g0initvals2.fw Extracting b43legacy/a0g1initvals5.fw Extracting b43legacy/b0g0bsinitvals2.fw Extracting b43legacy/b0g0initvals5.fw Extracting b43legacy/b0g0initvals2.fw Extracting b43legacy/a0g0bsinitvals5.fw broadcom-wl-4.150.10.5/ broadcom-wl-4.150.10.5/driver/ broadcom-wl-4.150.10.5/driver/config/ broadcom-wl-4.150.10.5/driver/config/wlconfig_apdef broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_ap broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_ap_1chipG broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_ap_micro broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_ap_mimo broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_apsta broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_apsta_1chipG broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_apsta_micro broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_apsta_mimo broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_sta broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_sta_1chipG broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_sta_micro broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_router_sta_mimo broadcom-wl-4.150.10.5/driver/config/wlconfig_lx_shared broadcom-wl-4.150.10.5/driver/config/wlconfig_micro broadcom-wl-4.150.10.5/driver/config/wlconfig_nomimo broadcom-wl-4.150.10.5/driver/config/wl_default broadcom-wl-4.150.10.5/driver/config/wl_hnd broadcom-wl-4.150.10.5/driver/wl_ap_micro.o broadcom-wl-4.150.10.5/driver/wl_ap_mimo.o broadcom-wl-4.150.10.5/driver/wl_ap.o
Bug#507058: b43-fwcutter fails to install: input file is wrong
On Thu, Nov 27, 2008 at 03:57:12PM +, Debian Bug Tracking System wrote: Then you probably someowhen insxtalled it locally and it takes precendence? In any case, the package is 11. But that's an other data point that you just fucked up something ;-) Running b43-fwcutter -l: b43-fwcutter version 009 You *NEED* 011. You were right ! I did have a copy of b43-fwcutter in /usr/local/bin from old unsuccessful work on b43. Now I managed to install the package as expected. I heartily thank you for your patience in following this bug which wasn't a bug after all but solely my mistake ! Regards, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443398: k3b doesn't make cd copy (SOLVED)
I deleted these: ~/.kde/share/k3b/ ~/.kde/share/config/k3b.eventsrc ~/.kde/share/config/k3brc And now I can copy CDs again. I don't know what in those config files/dirs was causing the error I observed. Apologies for raising this bug in vain. It can be closed. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized
On Fri, Sep 07, 2007 at 06:36:34PM +0200, maximilian attems wrote: [...] can you be so kind and test tomorrow's build, just to know that git firewire doesn't rebork. ;) I've just installed and rebooted today's kernel build (2.6.23~rc5-1~experimental.1~snapshot.9473), and... FIREWIRE IS STILL WORKING !!! Here are the syslog messages: Sep 8 12:49:19 monk kernel: scsi0 : SBP-2 IEEE-1394 Sep 8 12:49:19 monk kernel: firewire_core: created new fw device fw1 (0 config rom retries, S400) Sep 8 12:49:19 monk kernel: firewire_core: phy config: card 0, new root=ffc0, gap_count=5 Sep 8 12:49:21 monk kernel: firewire_sbp2: orb reply timed out, rcode=0x11 Sep 8 12:49:21 monk kernel: firewire_sbp2: logged in to fw1.1 LUN (1 retries) Sep 8 12:49:27 monk kernel: firewire_sbp2: sbp2_scsi_abort Sep 8 12:49:32 monk kernel: scsi 0:0:0:0: Direct-Access WD 5000AAKS Externa 107a PQ: 0 ANSI: 4 Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00 Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00 Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Sep 8 12:49:32 monk kernel: sda: sda1 sda2 Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk This snapshot of the firewire_sbp2 module still doesn't have the 'workaround' parameter. Here's the dmesg message: firewire_sbp2: Unknown parameter `workaround' I'm currently tracking unstable. When will this kernel snapshot hit unstable ? May I bump into problems if I go on booting kernel snapshot and continue to track unstable ? Thanks a lot for fixing this, Maks ! Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized
On Fri, Sep 07, 2007 at 05:41:51PM +0200, maximilian attems wrote: On Fri, Sep 07, 2007 at 05:21:24PM +0200, maximilian attems wrote: ahh just noticed please 2.6.23-rc5-k7 is available and will be the updated build tomorrow. (shouldn't make a diff with current build) I installed 2.6.23-rc5-k7 and bingo: the HD is recognized ! Here are the syslog messages now: Sep 7 13:01:17 monk kernel: scsi0 : SBP-2 IEEE-1394 Sep 7 13:01:17 monk kernel: firewire_sbp2: logged in to sbp2 unit fw1.1 (0 retries) Sep 7 13:01:17 monk kernel: firewire_sbp2: - management_agent_address: 0xf003 Sep 7 13:01:17 monk kernel: firewire_sbp2: - command_block_agent_address: 0xf010 Sep 7 13:01:17 monk kernel: firewire_sbp2: - status write address: 0x0001 Sep 7 13:01:17 monk kernel: firewire_sbp2: sbp2_scsi_abort Sep 7 13:01:17 monk kernel: scsi 0:0:0:0: Direct-Access WD 5000AAKS Externa 107a PQ: 0 ANSI: 4 Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00 Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00 Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Sep 7 13:01:17 monk kernel: sda: sda1 sda2 Sep 7 13:01:17 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk also you can now load modprobe firewire-sbp2 workaround=1 to enable some workarounds that were in the old sbp2 driver. I tried that but the module wasn't loaded. Here's the error message (from dmesg): firewire_sbp2: Unknown parameter `workaround' Thank you very much, Maks, for the speed-lightning responses and the fix ! Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized
On Fri, Sep 07, 2007 at 02:58:40PM +0200, maximilian attems wrote: My Western Digital 500GB MyBook external HD fails to be recognized when I plug it through the Firewire 400 port. The following errors appear on the syslog: firewire saw fixes, try out latest 2.6.23-rc4, see apt trunk lines - http://wiki.debian.org/DebianKernel No joy, Maks. I installed linux-image-2.6.23-rc4 from trunk as you asked me: Linux monk 2.6.23-rc4-k7 #1 SMP Wed Sep 5 00:17:02 UTC 2007 i686 GNU/Linux plugged my WD HD via Firewire 400, and the error messages are practically the same: Sep 7 10:29:19 monk kernel: scsi0 : SBP-2 IEEE-1394 Sep 7 10:29:19 monk kernel: firewire_core: created new fw device fw1 (0 config rom retries, S400) Sep 7 10:29:20 monk kernel: firewire_sbp2: logged in to sbp2 unit fw1.1 (0 retries) Sep 7 10:29:20 monk kernel: firewire_sbp2: - management_agent_address: 0xf003 Sep 7 10:29:20 monk kernel: firewire_sbp2: - command_block_agent_address: 0xf010 Sep 7 10:29:20 monk kernel: firewire_sbp2: - status write address: 0x0001 Sep 7 10:29:25 monk kernel: firewire_sbp2: sbp2_scsi_abort Sep 7 10:29:30 monk kernel: scsi 0:0:0:0: Direct-Access WD 5000AAKS Externa 107a PQ: 0 ANSI: 4 Sep 7 10:29:30 monk kernel: firewire_core: phy config: card 0, new root=ffc0, gap_count=5 Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] READ CAPACITY failed Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Sense not available. Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00 Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Asking for cache data failed Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Sep 7 10:29:30 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk Sep 7 10:29:32 monk kernel: firewire_sbp2: orb reply timed out, rcode=0x11 Sep 7 10:29:32 monk kernel: firewire_sbp2: error status: 0:9 Sep 7 10:29:33 monk last message repeated 4 times Sep 7 10:29:33 monk kernel: firewire_sbp2: failed to reconnect to fw1.1 Sep 7 10:29:34 monk kernel: firewire_sbp2: logged in to sbp2 unit fw1.1 (0 retries) Sep 7 10:29:34 monk kernel: firewire_sbp2: - management_agent_address: 0xf003 Sep 7 10:29:34 monk kernel: firewire_sbp2: - command_block_agent_address: 0xf010 Sep 7 10:29:34 monk kernel: firewire_sbp2: - status write address: 0x0001 Regards, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435173: Bug can be closed
I hav just checked and current amarok version (1.4.7-1+b1) doesn't show this bug anymore. I suppose it can be closed. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437693: libxine1-ffmpeg doesn't seem to include mp3 demuxer
On Wed, Aug 15, 2007 at 07:41:27AM +0200, Reinhard Tartler wrote: [...] Just to be sure, are you absolutely sure that you have all packages, that are 'Recommended' by libxine 1.1.7-2 installed? The only one not installed is libxine1-doc. load_plugins: cannot open plugin lib /usr/lib/xine/plugins/1.1.7/xineplug_dmx_audio.so: libmodplug.so.0: cannot open shared object file: No such file or directory Can you please try to install the libmodplug0c2 and try again? Bingo ! When I installed 1.1.7-2, libmodplug0c2 was automatically deleted by aptitude. I checked back and it's on Depends for 1.1.7-1, and Suggests for 1.1.7-2, hence the automatic deinstallation. After installing it, mp3 streams/files can be played again. I just rechecked the source after Darrens comment, and it seems that demux_mpgaudio.c is actually part of xineplug_dmx_audio.so. So if it cannot resolve all libraries it has been linked to, it cannot be loaded ans therefore, playing streams fails like Paulo reported. If this guess is true, -3 will promote libmodplug0c2 to Recommends. Shouldn't it be in Depends, as it was in 1.1.7-1 ? Thanks a lot for taking this problem ahead and reaching a solution, Reinhard and Darren ! Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437693: libxine1-ffmpeg doesn't seem to include mp3 demuxer
On Tue, Aug 14, 2007 at 08:08:00AM +0200, Reinhard Tartler wrote: Paulo Marcel Coelho Aragao [EMAIL PROTECTED] writes: This indeeds looks like the http input plugin wasn't able to recognize the stream format. I tried to reproduce it on my laptop (running ubuntu atm, but anyway), and was able to play that stream in 19 of 20 times. This means that I indeed had problems one single time. Weird, this. I'm never able to play that stream, no matter how many times I try. This means that there is either a race somewhere, or the stream provider had problems at the time you testet. Can you please do the following tests: * play an mp3 file locally [...] please also collect the -v log of gxine and watch for messages like I quoted above. Have just tried it: same result: xine can't play it. I'm sending gxine -v output. Having said this, I can assure you that there have been no code changes from -1 to -2 which could affect this. If you look at the debdiff, the only changes have been done to the input_dvb and the demux_ts plugin. The weird thing is: if I revert to 1.7.1-1, I can play mp3 streams or local files. [...] Paulo load_plugins: skipping unreadable plugin directory /home/paulo/.xine/plugins. load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dxr3_spu.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_vcdo.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_dxr3.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_dxr3.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_nsf.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_qt.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_ao_out_file.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xdirectfb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xdirectfb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_slave.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_gsm610.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xxmc.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_asf.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_v4l.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_v4l.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_a52.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_yuv4mpeg2.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_bitplane.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_dvb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_image.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_fli.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_nsv.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_flac.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_flac.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_iff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_yuv_frames.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_rgb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_speex.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_mad.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_smb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_pva.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_real.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_real.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_ao_out_none.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_net.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_spucmml.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_flv.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dvaudio.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_theora.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dts.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_file.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr
Bug#437693: Additional information
I've downgraded both libxine1 and libxine1-ffmpeg from 1.1.7-2 to 1.1.7-1 and I can now play mp3 streams. Downgrading libxine1-ffmpeg only didn't work, I had to downgrade both. Therefore, a bug seems to have crept in with version 1.1.7-2. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437693: libxine1-ffmpeg doesn't seem to include mp3 demuxer
On Mon, Aug 13, 2007 at 10:47:42PM +0200, Reinhard Tartler wrote: I use amarok with the xine engine. It's not playing mp3 streams after the upgrade 1.1.7-1 - 1.1.7-2 today (13th Aug). Thank you for your bugreport. Could you please install gxine and run it with parameter -v. Please save its output to a file and send it as attachment to this bug. Thanks for the speed-lightning reply. I've done as you instructed, tried to open the same mp3 stream I had tried with amarok, and the output is attached as gxine.out It looks as though the mp3 demuxer was removed from the package. I can assure you that this is not the case. The ffmpeg plugin is still in place. If you say so. It just gave me this impression because, although the package is installed, the mp3 demuxer cannot be found. I could see there was a bug filed against libxine1 about this same problem. Which bug do you refer to here? #394412, which seems to have been fixed in version 1.1.2-6. It seems to have come back with version 1.1.7-2. Regards, Paulo load_plugins: skipping unreadable plugin directory /home/paulo/.xine/plugins. load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dxr3_spu.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_vcdo.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_dxr3.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_dxr3.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_nsf.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_qt.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_ao_out_file.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xdirectfb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xdirectfb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_slave.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_gsm610.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_vo_out_xxmc.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_asf.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_v4l.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_v4l.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_a52.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_yuv4mpeg2.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_bitplane.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_dvb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_image.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_fli.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_nsv.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_flac.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_flac.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_iff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_yuv_frames.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_rgb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_speex.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_mad.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_smb.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_pva.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_real.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_real.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_ao_out_none.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_net.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_spucmml.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_flv.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dvaudio.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_theora.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_dts.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_inp_file.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin /usr/lib/xine/plugins/1.1.7/xineplug_dmx_games.so found load_plugins: plugin
Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
On Mon, Jul 30, 2007 at 10:22:38AM +0200, maximilian attems wrote: hmm interesting yeah they are due to the new firewire stack. it be interesting if you could test latest -rc1 + git7 if they are still reproducible there and if yes holler upstream. Thanks for the reply, Maks ! Should we leave the bug open then, until the next release, hoping it'll be fixed there ? Regards, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432953: kid3: kid3 not allowing creation of new export/import formats
Urs, Thank you for your more than patient explanation. I believe I found what seems to be the bug: if one of the fields, either from the import or the export dialog, is not filled, kid3 doesn't store the new format. The same happens if I edit kid3rc directly: if one of the fields is left blank, kid3 restores the lists to their default values. Your example works because all fields have values. If one field is left empty, the format is not stored. This still seems to be a bug to me, particularly because some of the default formats do not have values for all fields, and it doesn't make sense to mandate all fields. In my particular case, I was trying to export a simple list of all track titles, so I don't need to have values for header nor trailer. And, for importing, I just wanted to parse a list of 'artist - title' lines, without any header. Regards, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347388: vim-gtk: gvim --remote results in a raised window without focus
Package: vim-gtk Version: 1:6.4-006+1 Severity: normal I use gvim to edit mutt mails with the command: gvim --remote I ran Xfce, and xfwm4 raises the gvim window but doesn't give it focus. I took this discussion to the Xfce user mailing list and it was found out that gvim is using the EWMH standard NET_ACTIVE_WINDOW to activate its existing window, but it's passing an old timestamp. More updated window managers, such as xfwm4, don't focus the window if the timestamp is too old. Older window managers, such as fluxbox, don't support the timestamp mechanism, so they always focus the window. I refer you more details on this article from the Xfce discussion thread: http://article.gmane.org/gmane.comp.desktop.xfce.user/11189 Paulo -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages vim-gtk depends on: ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libc6 2.3.5-11 GNU C Library: Shared libraries an ii libcairo2 1.0.2-3The Cairo 2D vector graphics libra ii libfontconfig12.3.2-1.1 generic font configuration library ii libglib2.0-0 2.8.5-1The GLib library of C routines ii libgpmg1 1.19.6-21 General Purpose Mouse - shared lib ii libgtk2.0-0 2.8.9-2The GTK+ graphical user interface ii libice6 6.9.0.dfsg.1-2 Inter-Client Exchange library ii libncurses5 5.5-1 Shared libraries for terminal hand ii libpango1.0-0 1.10.2-1 Layout and rendering of internatio ii libsm66.9.0.dfsg.1-2 X Window System Session Management ii libx11-6 6.9.0.dfsg.1-2 X Window System protocol client li ii libxcursor1 1.1.3-1X cursor management library ii libxext6 6.9.0.dfsg.1-2 X Window System miscellaneous exte ii libxi66.9.0.dfsg.1-2 X Window System Input extension li ii libxinerama1 6.9.0.dfsg.1-2 X Window System multi-head display ii libxrandr26.9.0.dfsg.1-2 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-2 X Toolkit Intrinsics ii vim-gui-common1:6.4-006+1Vi IMproved - Common GUI files ii vim-runtime 1:6.4-006+1Vi IMproved - Runtime files vim-gtk recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345907: locales: Package update overwrites manually set timezone info for Brazil
Package: locales Version: 2.3.5-11 Severity: normal The timezone information for Brazil is out-of-date, so I manually update with: wget http://avi.alkalay.net/software/zoneinfo/Brazil.txt sudo zic Brazil.txt Whenever package locales is upgraded, this timezone information is overwritten and I have to repeat the process. This has just happened again for 2.3.5-10 - 2.3.5-11. It would be good: either to update the timezone info for Brazil or, if that's not possible, to ask berfore overwriting manually updated timezone info, as it happens with configuration files. Paulo -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages locales depends on: ii debconf [debconf-2.0] 1.4.67 Debian configuration management sy ii libc6 [glibc-2.3.5-3] 2.3.5-11 GNU C Library: Shared libraries an locales recommends no packages. -- debconf information: * locales/default_environment_locale: None * locales/locales_to_be_generated: en_US ISO-8859-1, en_US.UTF-8 UTF-8, pt_BR ISO-8859-1, pt_BR.UTF-8 UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345436: xlibs: Keyboard not working properly after upgrade to 6.9.0.dfsg.1-1
Package: xlibs Version: 6.9.0.dfsg.1-1 Severity: grave Justification: renders package unusable After the upgrade to 6.9.0.dfsg.1-1, the keyboard stopped working properly under X. I've noticed the following: 1. ctrl-alt-fn doesn't switch to other virtual consoles 2. The key with characters '/' and '?' is dead Not switching to virtual consoles can be lived with, but the lack of '/' and '?' makes X unusable. Needless to say, the keyboard works properly on the consoles, and it worked properly before the upgrade. Paulo -- Package-specific info: Keyboard-related contents of X.Org X server log file /var/log/Xorg.0.log: (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout default_layout (**) |--Screen external_screen (0) (**) | |--Monitor samsung (**) | |--Device onboard_card (**) |--Input Device ps2_keyboard (**) |--Input Device usb_mouse (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/Type1 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (**) Option AllowMouseOpenFail true -- (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.so (II) Module trident: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.8 (II) LoadModule: kbd (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.so (II) Module kbd: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.so -- (**) TRIDENT(0): DPMS enabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES -- (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (**) Option CoreKeyboard (**) ps2_keyboard: Core Keyboard (**) Option Protocol standard (**) ps2_keyboard: Protocol: standard (**) Option AutoRepeat 500 30 (**) Option XkbRules xorg (**) ps2_keyboard: XkbRules: xorg (**) Option XkbModel abnt2 (**) ps2_keyboard: XkbModel: abnt2 (**) Option XkbLayout br (**) ps2_keyboard: XkbLayout: br (**) Option CustomKeycodes off (**) ps2_keyboard: CustomKeycodes disabled (**) Option Protocol IMPS/2 (**) usb_mouse: Device: /dev/input/mice (**) usb_mouse: Protocol: IMPS/2 (**) Option SendCoreEvents true (**) usb_mouse: always reports core events -- (==) usb_mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) usb_mouse: ZAxisMapping: buttons 4 and 5 (**) usb_mouse: Buttons: 9 (II) XINPUT: Adding extended input device usb_mouse (type: MOUSE) (II) XINPUT: Adding extended input device ps2_keyboard (type: KEYBOARD) Couldn't compile keymap file (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap (II) usb_mouse: ps2EnableDataReporting: succeeded Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 X.Org X server log files on system: -rw-r--r-- 1 root root 34558 Dec 31 12:15 /var/log/Xorg.0.log -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages xlibs depends on: ii libice6 6.9.0.dfsg.1-1 Inter-Client Exchange library ii libsm6 6.9.0.dfsg.1-1 X Window System Session Management ii libx11-6 6.9.0.dfsg.1-1 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-1 X Window System miscellaneous exte ii libxi6 6.9.0.dfsg.1-1 X Window System Input extension li ii libxmu6 6.9.0.dfsg.1-1 X Window System miscellaneous util ii libxmuu1 6.9.0.dfsg.1-1 lightweight X Window System miscel ii libxp6 6.9.0.dfsg.1-1 X Window System printing extension ii libxpm4 6.9.0.dfsg.1-1 X pixmap library ii libxrandr2 6.9.0.dfsg.1-1 X Window System
Bug#345436: xlibs: Keyboard not working properly after upgrade to 6.9.0.dfsg.1-1
Mattia Dongili wrote on Dec, 31: On Sat, Dec 31, 2005 at 12:26:39PM -0200, Paulo Marcel Coelho Aragao wrote: Package: xlibs Version: 6.9.0.dfsg.1-1 Severity: grave Justification: renders package unusable After the upgrade to 6.9.0.dfsg.1-1, the keyboard stopped working properly under X. I've noticed the following: 1. ctrl-alt-fn doesn't switch to other virtual consoles 2. The key with characters '/' and '?' is dead Not switching to virtual consoles can be lived with, but the lack of '/' and '?' makes X unusable. Needless to say, the keyboard works properly on the consoles, and it worked properly before the upgrade. [...] Versions of packages xlibs depends on: [...] ii libxtst6 6.9.0.dfsg.1-1 X Window System event recording an ii xlibs-data 6.8.2.dfsg.1-11 X Window System client data ^ maybe you only missed the xlibs-data update? Uhhm, you're right. What I'd done was: sudo aptitude update sudo aptitude upgrade and left it installing, unattended. After hitting the problem, I downgraded everything and, after your email, upgraded again. There was an error unpacking xlibs-data, but I couldn't capture it: something to do with not being able to unpack a file because it also belonged to package xlibs. Here's the weird thing: grep xlibs-data /var/log/aptitude | tail -1 [UPGRADE] xlibs-data 6.8.2.dfsg.1-11 - 6.9.0.dfsg.1-1 dpkg -l xlibs-data ii xlibs-data 6.8.2.dfsg.1-11 X Window System client data I guess the bug stands then. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345436: xlibs: Keyboard not working properly after upgrade to 6.9.0.dfsg.1-1
Paulo Marcel Coelho Aragao wrote on Dec, 31: Mattia Dongili wrote on Dec, 31: On Sat, Dec 31, 2005 at 12:26:39PM -0200, Paulo Marcel Coelho Aragao wrote: Package: xlibs Version: 6.9.0.dfsg.1-1 Severity: grave Justification: renders package unusable After the upgrade to 6.9.0.dfsg.1-1, the keyboard stopped working properly under X. I've noticed the following: 1. ctrl-alt-fn doesn't switch to other virtual consoles 2. The key with characters '/' and '?' is dead Not switching to virtual consoles can be lived with, but the lack of '/' and '?' makes X unusable. Needless to say, the keyboard works properly on the consoles, and it worked properly before the upgrade. [...] Versions of packages xlibs depends on: [...] ii libxtst6 6.9.0.dfsg.1-1 X Window System event recording an ii xlibs-data 6.8.2.dfsg.1-11 X Window System client data ^ maybe you only missed the xlibs-data update? Uhhm, you're right. What I'd done was: sudo aptitude update sudo aptitude upgrade and left it installing, unattended. After hitting the problem, I downgraded everything and, after your email, upgraded again. There was an error unpacking xlibs-data, but I couldn't capture it: something to do with not being able to unpack a file because it also belonged to package xlibs. Here's the weird thing: grep xlibs-data /var/log/aptitude | tail -1 [UPGRADE] xlibs-data 6.8.2.dfsg.1-11 - 6.9.0.dfsg.1-1 dpkg -l xlibs-data ii xlibs-data 6.8.2.dfsg.1-11 X Window System client data I guess the bug stands then. I'm missing something here. When I did the upgrade again, I used aptitude in visual mode. I selected 'U', then 'g'. After I sent you the email, I tried: sudo dpkg --audit but, strangely, there were no packages pending configuration. I then tried: sudo aptitude upgrade and many X packages plus xlibs-data were upgraded. Now: [UPGRADE] xlibs-data 6.8.2.dfsg.1-11 - 6.9.0.dfsg.1-1 ii xlibs-data 6.9.0.dfsg.1-1 X Window System client data but the results are even worse: X abends *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x80) [0x8088da0] 1: [0xe420] 2: /usr/X11R6/lib/modules/libfb.so(fbFillRegionSolid+0xcf) [0xb79f0def] 3: /usr/X11R6/lib/modules/libfb.so(fbPaintWindow+0x8c) [0xb79f10bc] 4: /usr/X11R6/lib/modules/libxaa.so(XAAPaintWindow+0x13e) [0xb7995d3e] 5: /usr/bin/X11/X [0x816c782] 6: /usr/bin/X11/X(miWindowExposures+0x28e) [0x81a3cde] 7: /usr/bin/X11/X [0x80b45e6] 8: /usr/bin/X11/X(miHandleValidateExposures+0x67) [0x819bf77] 9: /usr/bin/X11/X [0x808a242] 10: /usr/X11R6/lib/modules/libxaa.so [0xb79816e8] 11: /usr/bin/X11/X [0x8095bc2] 12: /usr/bin/X11/X [0x8095dad] 13: /usr/bin/X11/X [0x8176971] 14: /usr/bin/X11/X(Dispatch+0x172) [0x80c7752] 15: /usr/bin/X11/X(main+0x414) [0x80d40b4] 16: /lib/tls/libc.so.6(__libc_start_main+0xd0) [0xb7e37ed0] 17: /usr/bin/X11/X [0x80701d1] Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. I can't understand what's happening. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344631: manpages-dev: /usr/share/man/man3/open_memstream.3.gz is a dangling symlink
Package: manpages-dev Version: 2.17-1 Severity: minor After the upgrade 2.16-1 - 2.17-1, this link was left dangling. Paulo -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages manpages-dev depends on: ii manpages 2.17-1 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344063: xserver-xorg: Server config script doesn't generate correct modelines
Package: xserver-xorg Version: 6.8.2.dfsg.1-11 Severity: normal I have a Samsung SyncMaster 793DF monitor attached to a Trident 9388 onboard videocard. The server config script doesn't generate the correct modelines, which restricts the resolution to 800x600. I booted Knoppix Live CD which generated the correct modelines and X achieved 1024x768 resolution, as expected. Current /etc/X11/xorg.conf is Knoppix's XF86Config-4 with the identifiers and keyboard tweaked; the modelines are untouched. This xorg discussion thread has more details: http://article.gmane.org/gmane.comp.freedesktop.xorg/5028 Paulo -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 Aug 29 10:38 /etc/X11/X - /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 1833112 Nov 29 06:48 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3) /etc/X11/xorg.conf does not match checksum in /var/lib/xfree86/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 7401 Dec 18 00:59 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section ServerLayout Identifier default_layout Screen 0 external_screen 0 0 InputDevice ps2_keyboard CoreKeyboard InputDevice usb_mouse CorePointer EndSection Section ServerFlags Option AllowMouseOpenFail true EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc:unscaled FontPath /usr/X11R6/lib/X11/fonts/misc FontPath /usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi FontPath /usr/X11R6/lib/X11/fonts/100dpi:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi FontPath /usr/X11R6/lib/X11/fonts/Type1 EndSection Section Module Load ddc # ddc probing of monitor Load dbe Load dri Load extmod Load glx Load bitmap # bitmap-fonts Load type1 Load freetype Load record EndSection Section InputDevice Identifier ps2_keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel abnt2 Option XkbLayout br EndSection Section InputDevice Identifier usb_mouse Driver mouse Option Device/dev/input/mice Option SendCoreEventstrue Option Protocol IMPS/2 Option ZAxisMapping 4 5 EndSection # Auto-generated by KNOPPIX mkxf86config Section Monitor Identifier samsung Option DPMS true HorizSync 30 - 71 # DDC-probed VertRefresh 50 - 160 # DDC-probed # These are the DDC-probed settings reported by your monitor. # 1280x1024, 75.0Hz; hfreq=79.98, vfreq=75.03 ModeLine 1280x1024135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync # 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00 ModeLine 1152x864 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync # 1024x768, 85.0Hz; hfreq=68.68, vfreq=85.00 ModeLine 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync # 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03 ModeLine 1024x768 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync # 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07 ModeLine 1024x768 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync # 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06 ModeLine 800x600 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync # 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00 ModeLine 800x600 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync # 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32 ModeLine 800x600 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync # 640x480, 85.0Hz; hfreq=43.27, vfreq=85.01 ModeLine 640x480 36.00 640 696 752 832 480 481 484 509 -hsync -vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 ModeLine 640x480 31.50 640 656 720 840 480 481 484 500 -hsync -vsync # 640x480, 72.0Hz; hfreq=37.86, vfreq=72.81 ModeLine 640x480 31.50 640 656 696 816 480 481 484 504 -hsync -vsync # 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94 ModeLine 640x480 25.17 640 648 744 784 480 482 484 509 -hsync -vsync # Extended modelines with GTF timings # 640x480 @ 100.00
Bug#343171: vim-gui-common: Dangling symlinks for gvim man pages
Package: vim-gui-common Version: 1:6.4-004+1 Severity: minor After refactoring of vim packages, these gvim man pages symlinks were left dangling: /usr/share/man/man1/gview.1 /usr/share/man/man1/gvim.1 /usr/share/man/man1/rgview.1 /usr/share/man/man1/rgvim.1 /usr/share/man/man1/gvimdiff.1 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages vim-gui-common depends on: ii vim-common 1:6.4-004+1 Vi IMproved - Common files Versions of packages vim-gui-common recommends: ii vim-gtk 1:6.4-004+1 Vi IMproved - enhanced vi editor - -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (patch results)
Erik van Konijnenburg wrote on Dec, 13: [...] http://arch.debian.org/arch/yaird/[EMAIL PROTECTED]/yaird/yaird--devo/yaird--devo--0.1/patch-131/ Could you give it a try and let me know if it actually works? [...] **Decide if you want to go ahead with this test. Only try this if you know how to recover from a non-booting kernel ( if I'm correct you've just done that) It's mine and everybody else's interest to have this solved. **Save the attached patch. Had already downloaded it from the URL you gave. **Make backup: $ cp /usr/lib/yaird/perl/Hardware.pm just-in-case.pm **Apply patch: $ sudo patch /usr/lib/yaird/perl/Hardware.pm /dat/tmp/Hardware.pm.patch patching file /usr/lib/yaird/perl/Hardware.pm Hunk #1 succeeded at 216 (offset -18 lines). $ (the offset is a normal warning in this case) **Comment out any work-arounds (MODULE ide-generic) you may have made in /etc/yaird/Default.cfg This is an important bit: you would not want to report success with the patch if actually your edit in Default.cfg is what makes the system boot. **Use the patched version to make a new initrd.img. A quick way to do this is $ sudo apt-get install linux-image-2.6.14-2-686-smp but only if you don't actually have an SMP system. This should leave your normal single-cpu kernel in place and install an smp kernel, with new initrd.img, next to it. It would take a while to download, so I did: sudo yaird -v -o /boot/initrd.img-2.6.14-2-686.patched | tee yaird.log and edited grub initrd at boot time. **reboot into new kernel; report success; undo if you don't like the effect. Bingo ! Flawless boot: all IDE devices recognized. Thanks a lot for the speedy patch ! Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (SOLVED)
Erik van Konijnenburg wrote on Dec, 13: [...] http://arch.debian.org/arch/yaird/[EMAIL PROTECTED]/yaird/yaird--devo/yaird--devo--0.1/patch-131/ Could you give it a try and let me know if it actually works? Bingo ! Flawless boot: all IDE devices recognized. In haste, I didn't notice: DMA is turned off for all IDE devices. [...] That's odd. The patch is designed to load piix before ide-generic, so that you get working DMA. Perhaps in your test you did not remove 'MODULE ide-generic' from your /etc/yaird/Default.cfg, so that it gets loaded too early? My sincerest apologies: DMA is indeed enabled. I just don't know what I did wrong in my previous attempt. I recreated now the initrd image with the default config file and the IDE devices are recognized and DMA is enabled for all of them. [...] Thanks again for the speedy patch ! Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: Workaround
Taking a lead from Ricardo, worked around the problem with: 1. Added to /etc/yaird/Default.cfg: MODULE ide-generic MODULE ide-disk 2. Created new initrd image: rm /boot/initrd.img-2.6.14-2-686 yaird -v -o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686 3. Reboot. hda now properly recognized and boot completes. Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)
Erik van Konijnenburg wrote on Dec, 12: [...] Thanks for your feedback. There's a patch at the following location: http://arch.debian.org/arch/yaird/[EMAIL PROTECTED]/yaird/yaird--devo/yaird--devo--0.1/patch-131/ This should add ide-generic if you have piix controller without the need to add it explicitly in the /etc/yaird/Default.cfg file. Could you give it a try and let me know if it actually works? Apologies for the more than basic question: how do I apply the patch ? Thanks for the patience, Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'
Package: linux-image-2.6.14-2-686 Version: 2.6.14-5 Severity: critical Justification: breaks the whole system Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot is interrupted with repeated messages: /bin/cat: /sys/block/hda/hda1/dev: No such file or directory until it finally stops completely, with message: Device /sys/block/hda/hda1/dev seems to be down I'm having to reboot with 2.6.12. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.14-2-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-1 Yet Another mkInitRD Versions of packages linux-image-2.6.14-2-686 recommends: pn libc6-i686none (no description available) -- debconf information: * linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686: linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686: linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686: linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686: linux-image-2.6.14-2-686/postinst/kimage-is-a-directory: linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686: linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686: linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: Additional info
Added to /etc/yaird/Default.cfg: MODULE piix MODULE generic MODULE ide-disk and ran: yaird --verbose --output=/boot/initrd.img-2.6.14-2-686 2.6.14-2-686 Exactly the same problem: no joy. I thought this might be needed: :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:10.0 Communication controller: Agere Systems 56k WinModem (rev 01) :00:13.0 CardBus bridge: Texas Instruments PCI1221 :00:13.1 CardBus bridge: Texas Instruments PCI1221 :00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3) Paulo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: (INFO) linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted,
boot is interrupted with repeated messages:
/bin/cat: /sys/block/hda/hda1/dev: No such file or directory
until it finally stops completely, with message:
Device /sys/block/hda/hda1/dev seems to be down
Erik,
I saw you requesting additional info from someone that bumped into exactly the
same problem I had. I thought that it might be useful if I sent you the same
info.
Paulo
Linux cortazar 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686 GNU/Linux
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii yaird 0.0.12-1 Yet Another mkInitRD
yaird -v -o crap.img 2.6.12-1-686
yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: action: insmod,
/lib/modules/2.6.12-1-686/kernel/drivers/video/console/bitblit.ko
{optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.12-1-686/kernel/drivers/video/console/font.ko {optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.12-1-686/kernel/drivers/video/console/tileblit.ko
{optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.12-1-686/kernel/drivers/video/console/fbcon.ko {optionList=-- }
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod,
/lib/modules/2.6.12-1-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/input/evdev.ko
{optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-disk.ko
{optionList=-- }
yaird: hardware: completed pci:00/:00:07.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda1 {sysname=hda/hda1 }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/mbcache.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/jbd/jbd.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/ext3/ext3.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda1 fsType=ext3 isRoot=1 options=-o
'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude, {}
yaird -v -o crap.img 2.6.14-2-686
yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko
{optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko
{optionList=-- }
yaird: hardware: completed pci:00/:00:07.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda1 {sysname=hda/hda1 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda1 fsType=ext3 isRoot=1 options=-o
'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude, {}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341519: linux-image-2.6.14-2-686: USB devices dead after resuming from APM suspend
Package: linux-image-2.6.14-2-686 Version: 2.6.14-4 Severity: normal I have up-to-date sid, kernel 2.6.14-2-686, installed on a Fujitsu Lifebook E342 laptop. When it comes back from APM suspend, the USB devices (a 4-port hub and a mouse) are not brought up, and lsusb (or any access to /proc/bus/usb) hangs. This doesn't happen with a 2.6.12-1-686 kernel which I also have installed. Paulo /proc/cmdline: root=/dev/hda1 ro acpi=off From /var/log/syslog after APM suspend: Nov 29 02:46:07 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) Nov 29 02:46:08 localhost kernel: usb 1-1.4: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb 1-1: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb usb1: no poweroff yet, suspending instead Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.0 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.1 Nov 29 02:46:25 localhost kernel: eth0: lost link beat Nov 29 02:46:25 localhost kernel: usb 1-1: USB disconnect, address 4 Nov 29 02:46:25 localhost kernel: usb 1-1.4: USB disconnect, address 6 Nov 29 02:46:26 localhost kernel: eth0: found link beat Nov 29 02:46:26 localhost kernel: eth0: autonegotiation complete: 100baseT-FD selected uname -a: Linux cortazar 2.6.14-2-686 #1 Sat Nov 26 13:10:11 UTC 2005 i686 GNU/Linux lsusb: Bus 001 Device 003: ID 045e:0084 Microsoft Corp. Bus 001 Device 002: ID 05e3:0660 Genesys Logic, Inc. USB 2.0 Hub Bus 001 Device 001: ID : lspci: :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:10.0 Communication controller: Agere Systems 56k WinModem (rev 01) :00:13.0 CardBus bridge: Texas Instruments PCI1221 :00:13.1 CardBus bridge: Texas Instruments PCI1221 :00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3) dpkg -l udev: ii udev 0.076-3/dev/ and hotplug management daemon -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.14-2-686 depends on: ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-12 Yet Another mkInitRD linux-image-2.6.14-2-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336909: pcmcia-cs: cardmgr doesn't bring eth0 up
Package: pcmcia-cs
Version: 3.2.8-5.2
Followup-For: Bug #336909
I don't have hotplug installed, and cardmgr is not bringing eth0 up anymore. I
did:
1. Unset REFRAIN_FROM_IFUP in /etc/default/pcmcia
2. Added 'allow-hotplug eth0' to /etc/netork/interfaces
But cardmgr doesn't bring the interface up just the same.
I noticed these, in /etc/pcmcia/network.opts
# Extra stuff to do after setting up the interface
start_fn () { return; }
# Extra stuff to do before shutting down the interface
stop_fn () { return; }
and changed them to what they used to be:
# Extra stuff to do after setting up the interface
start_fn () { ifup $1; }
# Extra stuff to do before shutting down the interface
stop_fn () { ifdown $1; }
and now cardmgr does bring eth0 up as expected.
Paulo
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages pcmcia-cs depends on:
ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy
ii dmidecode 2.7-2 Dump Desktop Management Interface
ii libc6 2.3.5-7GNU C Library: Shared libraries an
ii lsb-base 3.0-11 Linux Standard Base 3.0 init scrip
ii module-init-tools 3.2-pre9-3 tools for managing Linux kernel mo
ii modutils 2.4.27.0-3 Linux module utilities
ii psmisc21.6-1 Utilities that use the proc filesy
Versions of packages pcmcia-cs recommends:
pn hotplug none (no description available)
-- debconf information:
pcmcia-cs/abort_upgrade: true
pcmcia-cs/error_stopping:
pcmcia-cs/abort_msg:
pcmcia-cs/not_stopped:
pcmcia-cs/stop_pcmcia: true
pcmcia-cs/fix_pcic: false
pcmcia-cs/run_probe: true
pcmcia-cs/upgrade_note:
pcmcia-cs/start_later:
pcmcia-cs/upgrade_action: ask
pcmcia-cs/start_pcmcia: true
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319234: ifupdown: Scripts in /etc/network/if-post-up.d/ are not executed
Package: ifupdown Version: 0.6.7 Severity: normal I run Etch on a laptop and cardmgr configures my ethernet card. I'm trying to configure ifupdown to start fetchmail only after the network is up. I then noticed that /etc/network/if-post-up.d/ didn't exist. I created it and dropped my script there. However, it's not executed when the interface is brought up. The man page for interfaces(5) says about the pre and post options: There exists for each of the above mentioned options a directory /etc/net- work/if-option.d/ the scripts in which are run (with no arguments) using run-parts(8) after the option itself has been processed. iface eth0 inet dhcp post-up /etc/network/if-post-up.d/fetchmail then the script is executed. I'm not quite sure if I'm missing something here, or the man page is not in sync with the behaviour of the utility. Paulo -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.4.52 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii net-tools 1.60-15 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
