Bug#344385: Work with latest version
I no longer see this bug feel free to close it. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344385: Works in iceweasel version 2.0.0.7-2
I'm happy for the bug to be closed, I no longer see this problem. Thanks for your time. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337701: gsnes9x: looks for a joystick at /dev/js0 when the defualt location seems to be at /dev/input/js0
On Sunday 06 November 2005 22:37, Alain Schröder wrote: Am Samstag, den 05.11.2005, 20:47 + schrieb Grahame: I'm using udev but I'm not sure if it's that that is assigning the gamepad to /dev/input/js0 Since devfs there was a migration from /dev/js0 to /dev/input/js0. Although up to now it included a symlink from /dev/js0 to /dev/input/js0. It's not a solution to just use /dev/input/js0, because it wouldn't work on systems without udev/sysfs oder devfs. I'll have to patch it, to autodetect it... Sounds like the best way. Thanks for taking the time to look into this. Grahame
Bug#328950: libhal-storage0: Fails to install
On Sunday 18 September 2005 12:31, you wrote: On Sun, Sep 18, 2005 at 12:06:05PM +0100, Grahame wrote: Version 0.4.8-7 fails to upgrade with the following error: dpkg-query: parse error, in file `/var/lib/dpkg/status' near line 8587 package `libhal-storage0': `Depends' field, reference to `libhal0': version contains ` ' Reading changelogs... dpkg: parse error, in file `/var/lib/dpkg/status' near line 8587 package `libhal-storage0': `Depends' field, reference to `libhal0': version contains ` ' I'm afraid this points to a corruption problem with your status file, not a problem with the package. You can try restoring from /var/lib/dpkg/status-old; otherwise, you will probably have to edit the file by hand to correct the error. Yep that worked, thanks :) Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 19 July 2005 12:07, maximilian attems wrote: thanks for your further feadback. On Wed, 08 Jun 2005, Grahame White wrote: On Wednesday 08 June 2005 13:11, maximilian attems wrote: On Wed, 08 Jun 2005, Grahame white wrote: Since upgrading from woody to sarge I've been getting the following apperaring in the reports sent by logcheck: E: File could not be read: /var/log/mail/mail.err E: File could not be read: /var/log/mail/mail.warn E: File could not be read: /var/log/mail/mail.info E: File could not be read: /var/log/mail/mail.log rereading your bug report. i forgot to ask about the permissions of the /var/log/mail/ dir. please send the ouput of ls -ld /var/log/mail/ drwxrws--- 2 root smmsp 1024 Jul 19 06:30 /var/log/mail/ Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 19 July 2005 13:06, you wrote: On Tue, 19 Jul 2005, Grahame White wrote: On Tuesday 19 July 2005 12:07, maximilian attems wrote: snipp On Wed, 08 Jun 2005, Grahame white wrote: Since upgrading from woody to sarge I've been getting the following apperaring in the reports sent by logcheck: E: File could not be read: /var/log/mail/mail.err E: File could not be read: /var/log/mail/mail.warn E: File could not be read: /var/log/mail/mail.info E: File could not be read: /var/log/mail/mail.log rereading your bug report. i forgot to ask about the permissions of the /var/log/mail/ dir. please send the ouput of ls -ld /var/log/mail/ drwxrws--- 2 root smmsp 1024 Jul 19 06:30 /var/log/mail/ aah cool, no way logcheck could read inside of that dir. sorry for my sendmail ignorance, but is that the default permission, or did you harden it somehow? is that an sarge installation or woody upgrade? It was a standard woody install that I upgraded to sarge. I haven't touched the permissions on this directory myself so I assume that whatever program created it set them like that. which are the member of aboves group: getent group smmsp No one is in the group. either you change aboves dir to be readable for the adm group chgrp adm /var/log/mail/ (shouldn't pose problems to sendmail as it doesn't write aboves file with smmsp group permissions). Certainly shouldn't! I just double-checked, I don't even have sendmail installed :) or you add logcheck to aboves group: adduser --quiet logcheck smmsp -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 19 July 2005 13:58, maximilian attems wrote: On Tue, 19 Jul 2005, Grahame White wrote: On Tuesday 19 July 2005 13:06, you wrote: On Tue, 19 Jul 2005, Grahame White wrote: snipp drwxrws--- 2 root smmsp 1024 Jul 19 06:30 /var/log/mail/ aah cool, no way logcheck could read inside of that dir. sorry for my sendmail ignorance, but is that the default permission, or did you harden it somehow? is that an sarge installation or woody upgrade? It was a standard woody install that I upgraded to sarge. I haven't touched the permissions on this directory myself so I assume that whatever program created it set them like that. which are the member of aboves group: getent group smmsp No one is in the group. either you change aboves dir to be readable for the adm group chgrp adm /var/log/mail/ (shouldn't pose problems to sendmail as it doesn't write aboves file with smmsp group permissions). Certainly shouldn't! I just double-checked, I don't even have sendmail installed :) ok strange. an smmsp google gave lots of sendmail hits, that's why i assumed it. whats you mail transfer agent? (exim4, postfix, ..) does it work fine with aboves change? I'm using exim4, and yes the change you suggested seems to have fixed the problem. i guess so, as nobody uses that group the permission group setting of /var/log/mail seems more like an accident. now that logcheck should run without troubles, can you confirm? i guess we can close that bug. Yes, I'm fine with closing the bug -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 19 July 2005 17:48, maximilian attems wrote: On Tue, 19 Jul 2005, Grahame White wrote: snipp I'm using exim4, and yes the change you suggested seems to have fixed the problem. i guess so, as nobody uses that group the permission group setting of /var/log/mail seems more like an accident. now that logcheck should run without troubles, can you confirm? i guess we can close that bug. Yes, I'm fine with closing the bug thanks for your feedback, i'm happy to hear logcheck is running fine. :) although this bug may need to be reassigned to the package, which created that strange group ownership of /var/log/mail. exim4 usually logs to /var/log/exim4 on all of standard installs i see around me. so what mail subsystem of yours is logging to aboves dir? do you have some custom syslog (or syslog-ng) rules that direct messages there? maybe we can grasp which packet added the smmsp user. what does belows command on your box show: egrep smmsp -r /var/lib/dpkg/info/ /var/lib/dpkg/info/sendmail.postrm: # Remove user/group smmsp /var/lib/dpkg/info/sendmail.postrm: deluser --quiet smmsp || true; /var/lib/dpkg/info/sendmail.postrm: userdel smmsp 2/dev/null || true; /var/lib/dpkg/info/sendmail.postrm: groupdel smmsp 2/dev/null || true; As you said earlier, it looks like a sendmail problem except that I don't have it installed. I don't recall having ever installed it previously either. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 19 July 2005 18:04, maximilian attems wrote: On Tue, 19 Jul 2005, Grahame White wrote: On Tuesday 19 July 2005 17:48, maximilian attems wrote: ok. but does look like removed and not purged after install. you can check the dpkg status, what does that show: dpkg -l sendmail rc sendmail 8.12.3-6.6A powerful, efficient, and scalable Mail Transport Agent Hmm, looks like I did have it installed at some point. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312194: Strace of k3b
I've attached the output of an strace of k3b.
execve(/usr/bin/k3b, [k3b], [/* 32 vars */]) = 0
uname({sys=Linux, node=borgmania, ...}) = 0
brk(0) = 0x712000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aabf000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.preload, O_RDONLY)= -1 ENOENT (No such file or directory)
open(/usr/lib/tls/x86_64/libk3bdevice.so.2, O_RDONLY) = -1 ENOENT (No such file or directory)
stat(/usr/lib/tls/x86_64, 0x7fea9fc0) = -1 ENOENT (No such file or directory)
open(/usr/lib/tls/libk3bdevice.so.2, O_RDONLY) = -1 ENOENT (No such file or directory)
stat(/usr/lib/tls, 0x7fea9fc0)= -1 ENOENT (No such file or directory)
open(/usr/lib/x86_64/libk3bdevice.so.2, O_RDONLY) = -1 ENOENT (No such file or directory)
stat(/usr/lib/x86_64, 0x7fea9fc0) = -1 ENOENT (No such file or directory)
open(/usr/lib/libk3bdevice.so.2, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\0\306\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=160784, ...}) = 0
mmap(NULL, 1207776, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2abc1000
mprotect(0x2abe4000, 1064416, PROT_NONE) = 0
mmap(0x2acc1000, 159744, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2acc1000
close(3)= 0
open(/usr/lib/libk3b.so.1, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\0\v\v\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=2009488, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ace8000
mmap(NULL, 3058544, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2ace9000
mprotect(0x2ae99000, 1289072, PROT_NONE) = 0
mmap(0x2aee9000, 962560, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x10) = 0x2aee9000
close(3)= 0
open(/usr/lib/libkparts.so.2, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\300\331..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=360144, ...}) = 0
mmap(NULL, 1407456, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2afd4000
mprotect(0x2b01f000, 1100256, PROT_NONE) = 0
mmap(0x2b0d4000, 360448, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2b0d4000
close(3)= 0
open(/usr/lib/libkio.so.4, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0[EMAIL PROTECTED]..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=3835056, ...}) = 0
mmap(NULL, 4892008, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b12c000
mprotect(0x2b462000, 1525096, PROT_NONE) = 0
mmap(0x2b52c000, 688128, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x30) = 0x2b52c000
mmap(0x2b5d4000, 9576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2b5d4000
close(3)= 0
open(/usr/lib/libkdeui.so.4, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0[EMAIL PROTECTED]..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=3674128, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b5d7000
mmap(NULL, 4725576, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b5d8000
mprotect(0x2b8d3000, 1600328, PROT_NONE) = 0
mmap(0x2b8d8000, 1576960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x20) = 0x2b8d8000
mmap(0x2ba59000, 2888, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2ba59000
close(3)= 0
open(/usr/lib/libkdecore.so.4, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\200\240..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=2641008, ...}) = 0
mmap(NULL, 3700952, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2ba5a000
mprotect(0x2bc92000, 1374424, PROT_NONE) = 0
mmap(0x2bd5a000, 544768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x20) = 0x2bd5a000
mmap(0x2bddf000, 10456, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2bddf000
close(3)= 0
open(/usr/lib/libDCOP.so.4, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\0005\1\0..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=232368, ...}) = 0
mmap(NULL, 1293888, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2bde2000
mprotect(0x2be14000, 1089088, PROT_NONE) = 0
mmap(0x2bee2000, 233472, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2bee2000
mmap(0x2bf1b000, 11840, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2bf1b000
close(3)= 0
open(/usr/lib/libkdefx.so.4, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\300\346..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=183408, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2bf1e000
mmap(NULL,
Bug#315979: Sample page as mentioned in previous message
This simple example was cut 'n pasted from the docs on the vlc website. I then modified it to point at a small sample avi instead of the example url that was included. I've check the avi and it plays fine in vlc so I don't think it's a problem there, but I can send the file if you want, it is pretty small, only about 200kb or so. Grahame Title: Demo of VLC mozilla plugin Demo of VLC mozilla plugin - Example 1 Play video1 Pause video1 Stop video1 Fullscreen
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Tuesday 21 June 2005 23:14, maximilian attems wrote: thanks for your provided feedback. saw no direct hint in the debug info there. but i had another idea of what could go wrong. could you please send the output of belows command as root # ls -l /var/lib/logcheck Sure. # ls -l /var/lib/logcheck/ total 14 drwx-- 4 logcheck logcheck 1024 Apr 17 2004 cleaned -rw--- 1 logcheck logcheck 13 Jun 22 06:02 offset.var.log.auth.log -rw--- 1 logcheck logcheck 13 Jun 22 06:02 offset.var.log.daemon.log -rw--- 1 logcheck logcheck 11 Jun 20 07:02 offset.var.log.debug -rw--- 1 logcheck logcheck8 Apr 24 07:02 offset.var.log.kern.log -rw--- 1 logcheck logcheck8 Jun 19 07:02 offset.var.log.lpr.log -rw--- 1 logcheck logcheck8 Feb 27 07:02 offset.var.log.mail.mail.err -rw--- 1 logcheck logcheck 14 Jun 7 18:02 offset.var.log.mail.mail.info -rw--- 1 logcheck logcheck 14 Jun 7 18:02 offset.var.log.mail.mail.log -rw--- 1 logcheck logcheck8 Feb 27 07:02 offset.var.log.mail.mail.warn -rw--- 1 logcheck logcheck 11 Jun 22 06:02 offset.var.log.messages -rw--- 1 logcheck logcheck 13 Jun 22 06:02 offset.var.log.syslog -rw--- 1 logcheck logcheck8 Sep 5 2004 offset.var.log.user.log -rw--- 1 logcheck logcheck8 Oct 16 2003 offset.var.log.uucp.log -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312412: [Logcheck-devel] Bug#312412: logcheck: Fails to read files under /var/log/mail/
On Wednesday 08 June 2005 13:11, maximilian attems wrote: On Wed, 08 Jun 2005, Grahame white wrote: Since upgrading from woody to sarge I've been getting the following apperaring in the reports sent by logcheck: E: File could not be read: /var/log/mail/mail.err E: File could not be read: /var/log/mail/mail.warn E: File could not be read: /var/log/mail/mail.info E: File could not be read: /var/log/mail/mail.log The permissions for these files are: -rw-r- 1 root adm2748 Jun 7 18:28 mail.err -rw-r- 1 root adm 1983524 Jun 8 00:07 mail.info -rw-r- 1 root adm 2268687 Jun 8 00:07 mail.log -rw-r- 1 root adm2748 Jun 7 18:28 mail.warn and the user logcheck is a member of the adm group. what version of logtail do you have installed? dpkg -l logtail 1.2.39 could you please send us the debug output of logcheck: logcheck -d -o Please find the output attached thanks for your feedback. -- maks logcheck.debug.tar.gz Description: application/tgz
Bug#312412: logcheck: Fails to read files under /var/log/mail/
Package: logcheck Severity: normal Since upgrading from woody to sarge I've been getting the following apperaring in the reports sent by logcheck: E: File could not be read: /var/log/mail/mail.err E: File could not be read: /var/log/mail/mail.warn E: File could not be read: /var/log/mail/mail.info E: File could not be read: /var/log/mail/mail.log The permissions for these files are: -rw-r- 1 root adm2748 Jun 7 18:28 mail.err -rw-r- 1 root adm 1983524 Jun 8 00:07 mail.info -rw-r- 1 root adm 2268687 Jun 8 00:07 mail.log -rw-r- 1 root adm2748 Jun 7 18:28 mail.warn and the user logcheck is a member of the adm group. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305272: Further information
XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12 2005022119 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.10-9-amd64-k8 x86_64 [ELF] Build Date: 20 February 2005 This version of XFree86 has been extensively modified by the Debian Project, and is not supported by the XFree86 Project, Inc., in any way. Bugs should be reported to the Debian Bug Tracking System; see URL: http://www.debian.org/Bugs/Reporting . We strongly encourage the use of the reportbug package and command to ensure that bug reports contain as much useful information as possible. Before filing a bug report, you may want to consult the Debian X FAQ: XHTML version: file:///usr/share/doc/xfree86-common/FAQ.xhtml plain text version: file:///usr/share/doc/xfree86-common/FAQ.gz Module Loader present OS Kernel: Linux version 2.6.11 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Mon Apr 18 18:58:42 BST 2005 T Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Apr 19 00:28:34 2005 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Simple Layout (**) |--Screen Screen_1 (0) (**) | |--Monitor Relisys_19 (**) | |--Device gf4 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout qwerty (**) XKB: layout: qwerty (**) Option XkbVariant gb (**) XKB: variant: gb (==) Keyboard: CustomKeycode disabled (WW) The directory /usr/X11R6/lib/X11/fonts/TrueType does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/local/share/fonts. Entry deleted from font path. (Run 'mkfontdir' on /usr/local/share/fonts). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts). (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (**) Option Xinerama True (**) Xinerama: enabled (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0282 card 1106,3282 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 1106,1282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:2: chip 1106,2282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:3: chip 1106,3282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:4: chip 1106,4282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:7: chip 1106,7282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b188 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:08:0: chip 1274,1371 card 1274,1371 rev 08 class 04,01,00 hdr 00 (II) PCI: 00:0b:0: chip 10ec,8169 card 1462,702c rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0d:0: chip 105a,3574 card 1462,7020 rev 02 class 01,04,00 hdr 00 (II) PCI: 00:0e:0: chip 1106,3044 card 1462,702d rev 46 class 0c,00,10 hdr 00 (II) PCI: 00:0f:0: chip 1106,3149 card 1462,7020 rev 80 class 01,04,00 hdr 80 (II) PCI: 00:0f:1: chip 1106,0571 card 1462,7020 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1462,7020 rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1462,7020 rev 81 class 0c,03,00 hdr 80
Bug#303813: bittornado-gui: Majority of downloads are failing with a corrupted error message
On Saturday 09 April 2005 00:23, you wrote: Hello, This seems to be a int.size bug on 64bit architectures... I know that mainline doesn't have this problem, and I *think* that I've got a patch that fixes this. Can you try installing the version of bittornado that is at http://people.debian.org/~micah and see if you can reproduce the problem? If it fixes it, I will upload that version to the archive. Thanks! Micah Looking good so far, it's even managed to recover one of the 'corrupted' downloads whereas before it would have started the download all over again. I'll wait a little while longer before I defiantly say it's fixed as sometimes it took a good few hours for the file(s) to corrupt. Grahame OK, I've had a couple of torrents running all night and no corruption errors have appeared so I'm going to say that the updated package fixes the bug. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303813: bittornado-gui: Majority of downloads are failing with a corrupted error message
OK, I've had a couple of torrents running all night and no corruption errors have appeared so I'm going to say that the updated package fixes the bug. Grahame D'oh, not five minutes after I sent the last message and one of my downloads corrupted. So no the new package doesn't fix the bug. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303813: bittornado-gui: Majority of downloads are failing with a corrupted error message
On Saturday 09 April 2005 20:57, you wrote: Hmm, I had a friend with an amd64 machine try this out and he had no problems at all (using the updated bittornado I had you try), he got download succeeded! with the md5sum: 21f473605f8aabb8bb54e2ebb09d170b Micah I was checking to see what processes I had running and noticed that I had an instance of that torrent still downloading (even though I'd managed to complete it a little while back). The odd thing is that I didn't have a window open for that torrent even though I'd been using bittornado-gui. I'm wondering if after failing to download earlier, and me then closing the window, the process didn't stop properly and was interfering with the download I'd started with the new package (hope that makes some kind of sense). Anyhow, the other torrents that I have running (and have had running since I installed the updated package) all seem to be OK. So I'm going to say that it seems to have done the job. Of course if I do get a torrent that gives the same problems I'll send the link for testing. Thanks for your time. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303813: bittornado-gui: Majority of downloads are failing with a corrupted error message
On Saturday 09 April 2005 00:23, you wrote: Hello, This seems to be a int.size bug on 64bit architectures... I know that mainline doesn't have this problem, and I *think* that I've got a patch that fixes this. Can you try installing the version of bittornado that is at http://people.debian.org/~micah and see if you can reproduce the problem? If it fixes it, I will upload that version to the archive. Thanks! Micah Looking good so far, it's even managed to recover one of the 'corrupted' downloads whereas before it would have started the download all over again. I'll wait a little while longer before I defiantly say it's fixed as sometimes it took a good few hours for the file(s) to corrupt. Grahame PS this has to be one of the fastest responses I've ever had to a bug report :D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294891: Just spotted this
This is a bug in kernel-package 8.120: http://bugs.debian.org/294751 An upgrade to 8.121 will fix the issue. I just spotted this, thanks. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294889: kernel-package locks up when building
On Saturday 12 February 2005 06:28, C.Y.M wrote: Manoj Srivastava wrote: Hi, Can't reproduce this. Do you have any additional details? Like a log of where the lock up happened? manoj snip make: *** No rule to make target `conf.vars', needed by `stamp-configure'. Stop. I've just posted a bug report against kernel-source-2.6.10 with the same error message. Looks like I may have reported against the wrong package. I went through the same steps: make-kpkg clean make-kpkg --revision=custom.1 kernel_image That's when I got the error. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289339: Might be GPL'd
I installed this game on a friend's windows PC and had to agree to a click-through GPL license during the install. This may mean the game is only GPL'd on windows but maybe not. There is no licence listed on the web page or in the source code itself. Grahame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
