Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2066
Today's Topics:
Re: mounting usb frustration [ Bob McGowan ]
Debian can't mount Camera Memory Sti [ Mike McCarty ]
Re: Debian can't mount Camera Memory [ Mike McCarty ]
Re: A question of fonts [ Florian Kulzer ]
Re: where is linux-2.6_2.6.22-2.diff [ andreimpopescu@gmail.com (Andrei Po ]
Re: Debian can't mount Camera Memory [ andreimpopescu@gmail.com (Andrei Po ]
Date: Mon, 30 Jul 2007 12:30:03 -0700
From: Bob McGowan <bob_mcgowan@symantec.com>
To: debian-user@lists.debian.org
Subject: Re: mounting usb frustration
Message-ID: <46AE3C3B.9080207@symantec.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010701010607090206000606"
This is a cryptographically signed message in MIME format.
--------------ms010701010607090206000606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Haines Brown wrote:
> I mounted a USB flash card with a reader OK once, but failed the
> second time. With two hard disks, an external USB mass storage deveice
> and with a USB-key, all mounted using sda-sdd interfaces,
>
> # mount -t vfat /dev/sde1 /media/reader
> mount: special device /dev/sde1 does not exist
>
> Indeed, udev has not generated any such interface. I have sdc, sdc1,
> sdd, sdd1, sde, sdf, sdf1. The sda and sdb interfaces are for hard
> disks.
>
> The flash card reader is seen on the USB bus and the necessary modules
> are loaded.
>
> But I get a very odd report from trying to mount sde1: :
>
> $ dmesg | tail
> sdf: assuming drive cache: write through
> SCSI device sdf: 234441648 512-byte hdwr sectors (120034 MB)
> sdf: Write Protect is off
> sdf: Mode Sense: 27 00 00 00
> sdf: assuming drive cache: write through sdf: sdf1
> sd 13:0:0:0: Attached scsi disk sdf
> usb-storage: device scan complete
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev sdb1.
>
> The message about FAT on sdb1 is correct, for it is ext2. Since udev
> had created a sdf1, if I try to mount using it:
>
> # mount -t vfat /dev/sdf1 /media/reader
> mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> I get the sense that for some reason udev is not creating sde1, and so
> sdf and sdf1 are created, but can't be used. I'm running Etch, and
> udev is 0.105-4.
>
I've seen this sort of thing happen, when the system, for whatever
reason, thinks the original device is still attached. The detection
event for the second use is then given a new device node.
You may want to try running an 'fdisk' on the device names, to see which
actually has partitions, and what their type(s) is(are). For example:
# fdisk -l /dev/sde
Disk /dev/sde: 65 MB, 65012224 bytes
8 heads, 32 sectors/track, 496 cylinders
Units = cylinders of 256 * 512 = 131072 bytes
Device Boot Start End Blocks Id System
/dev/sde1 * 1 484 61924+ 1 FAT12
Partition 1 has different physical/logical endings:
phys=(499, 7, 32) logical=(483, 7, 32)
which will at least tell you the device name to use with the mount
command, and the file system type.
--
Bob McGowan
--------------ms010701010607090206000606
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJHzCC
AuowggJToAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oX
DTA3MDkwNzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUG
CSqGSIb3DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHpt
ad6Ct6JWTjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNY
zefbNaEgM4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSE
d8k2YI/Iq1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NI
ZIa6ldIU7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN
0QIDAQABozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4c
bFCynmuyekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3a
dAInokaS9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAuowggJT
oAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oXDTA3MDkw
NzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUGCSqGSIb3
DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHptad6Ct6JW
TjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNYzefbNaEg
M4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSEd8k2YI/I
q1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NIZIa6ldIU
7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN0QIDAQAB
ozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0TAQH/BAIw
ADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4cbFCynmuy
ekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3adAInokaS
9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAz8wggKooAMCAQIC
AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh
cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm
BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1h
aWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQD
EyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B
1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79A
gAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8E
CDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEa
MBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7M
DaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk1
3iSx0x1G/11fZU8xggNkMIIDYAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQQIQYnTX54sAOPQklBDqZhgPtjAJBgUrDgMCGgUAoIIBwzAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA3MzAxOTMwMDNaMCMG
CSqGSIb3DQEJBDEWBBQhkOa0oM3GwUq5GSQWYiBH/NC3tTBSBgkqhkiG9w0BCQ8xRTBDMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc
VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ01+eLADj0JJQQ6mYYD7YwgYcGCyqGSIb3DQEJEAIL
MXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ0
1+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEBBQAEggEAAiZ0n5K3T3kj7M14cdEESVIMwnpW
qHZnBcuSdKz/xV31k9LGCKHeDvIpa6dgrWSrU8eGrWQr0wJBFuOuMjXc18KwmdvPnk9cU/X4
2Gr24br8LDUQs8aQpwLPOCWJFQxfnX05+xUe01e6GkjMnUCyqQPdcnMHfr1SHWoYuY6laWXX
1PVoez5WR3zULMUYL5RM4cxU0aUb3BiY/JiWVfp9UFOxCzyvlncjY/O2uctIveZ2/TrTUCHK
qbIC+dW9P+IzMCxgqSoVBa/69OcH2fTgLf6AtnLE1B+9osM2Nly6N4hwC10BiI+BdYC727iX
P4zqvhrorz/wmQiUtxLCzmIO4gAAAAAAAA==
--------------ms010701010607090206000606--
Date: Mon, 30 Jul 2007 15:19:26 -0400
From: Steve Kleene <skdeb@syrano.acb.uc.edu>
To: debian-user@lists.debian.org
Subject: Re: new Etch install fails to boot
Message-Id: <200707301919.PAA31107@syrano.acb.uc.edu>
On Sun, Jul 29, 2007 at 11:00:30PM -0400:
> [I wrote that my fresh Etch install calls grub and then stops.]
On Mon, 30 Jul 2007 17:30:41 +0000, Robert Cates wrote:
> ... I then re-installed Etch (from scratch) with still the same
> problem, until I decided to turn off (disable) the Power Management in the
> BIOS.
>
> I think your problem was with bootup, but maybe this helps you out, if you
> haven't already found a solution.
Thanks, I'll keep this in mind.
Date: Mon, 30 Jul 2007 13:48:01 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: Debian can't mount Camera Memory Stick
Message-ID: <20070730204800.GB31753@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="pqZtgxSH0iQu6R78"
Content-Disposition: inline
--pqZtgxSH0iQu6R78
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 30, 2007 at 03:37:58PM -0500, Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.
>
> Currently, she mounts using XP on the laptop, then e-mails the photos
> to herself over a dial-up, and then reads the mail back into Debian
> using an ADSL connection. Needless to say, this is not the desirable
> solution.
>
> When we try to mount that memory card, mount responds that it is
> unable to ascertain the file system type. It appears that fdisk
> is unable to read anything from it at all. OTOH, lsusb shows the
> Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
> are somewhat lengthy.
>
> Any who are willing to help understand what to do to get this
> card to mount, I'll ship them by e-mail, or if consensus agrees
> to it, I'll post them here. They are a few kilobytes altogether.
send them to me directly if you want, but first:
what is the output of=20
tail -f /var/log/syslog
when started before plugging the device in until after its plugged and
settled.=20
If this a regular flash memory stick/card? For example, my camera uses
bog-standard compact flash cards (about 1.25 inches square by 1/8 in
thick) and they plug into a standard card reader and mount as
/dev/sda1 as a vfat device. Is that what we're trying to do? or is it
some proprietary format device that doesn't plug into a standard
cardreader?=20
A
--pqZtgxSH0iQu6R78
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGrk6AaIeIEqwil4YRAk11AKCGg0CQwlAD14FsMXRjtTX8m9/g6ACgqImw
iP7b8sqGt4fNRfUNc+Z9d8M=
=zPhL
-----END PGP SIGNATURE-----
--pqZtgxSH0iQu6R78--
Date: Mon, 30 Jul 2007 21:40:08 +0100
From: andy <geek_show@dsl.pipex.com>
To: debian-user@lists.debian.org
Subject: Re: A question of fonts
Message-ID: <46AE4CA8.2010907@dsl.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Alan Ianson wrote:
>> Alan Ianson wrote:
>>
>> <snip>
> If you type env in a term what is lang= set to? You can adjust that setting by
> running "dpkg-reconfigure locales".
>
> I think etch uses utf-8 by default. A better solution would be if packages
> were utf-8 capable. It may be that xmms and iceweasel are not utf-8 aware but
> my knowledge if this stuff is sketcky at best.
>
>
>
Hi Alan
Thanks for the tips. I followed your suggestion and got, in part, this
as a result of env
LANG=en_GB.UTF-8
GDM_LANG=en_GB.UTF-8
How do I use this info to overcome what is really a lousy text display
in something like Xmms, and some other apps I've tried?
Cheers
A
--
"If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Date: Mon, 30 Jul 2007 15:37:58 -0500
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: Debian user list <debian-user@lists.debian.org>
Subject: Debian can't mount Camera Memory Stick
Message-ID: <46AE4C26.6040001@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
My GF has a situation in which she cannot mount a camera memory
stick. Here's the setup...
CPU<--->HUB<--->Dazzle[<--Stick
The HUB is from Radio Shack. The Dazzle is a device used to
interface the memory stick with USB. The memory stick is
a Sandisk 128 MB memory stick for a camera. Using her laptop
and XP, with the same Dazzle and memory stick, it mounts
just fine. With her desktop and Debian, it fails to mount.
Also connected to the hub are a WD USB hard disc, and an HP printer,
both of which work fine with Debian.
Currently, she mounts using XP on the laptop, then e-mails the photos
to herself over a dial-up, and then reads the mail back into Debian
using an ADSL connection. Needless to say, this is not the desirable
solution.
When we try to mount that memory card, mount responds that it is
unable to ascertain the file system type. It appears that fdisk
is unable to read anything from it at all. OTOH, lsusb shows the
Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
are somewhat lengthy.
Any who are willing to help understand what to do to get this
card to mount, I'll ship them by e-mail, or if consensus agrees
to it, I'll post them here. They are a few kilobytes altogether.
Thanks all for your time.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Date: Mon, 30 Jul 2007 21:45:07 +0100
From: andy <geek_show@dsl.pipex.com>
To: debian-user@lists.debian.org
Subject: Re: A question of fonts
Message-ID: <46AE4DD3.5000809@dsl.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Florian Kulzer wrote:
> On Sat, 28 Jul 2007 22:28:13 +0100, andy wrote:
>
> [...]
>
>
>> I do have the latest msttcorefonts installed. It just looks crap with
>> Xmms and sometimes Iceweasel seems difficult to read too. But
>> certainly Xmms is the worst of the bunch.
>>
>
> This could also be a problem with your settings for font display rather
> than with the fonts themselves. I do not use XMMS, so here is a
> demonstration of the influence of font settings on iceweasel (PNG image,
> 55.6 KB):
>
> http://users.icfo.es/Florian.Kulzer/fontconfig/iceweasel-font-comparison.png
>
> Maybe you can post your font settings and we can have a look:
>
> awk '/fontconfig/,/^$/' /var/cache/debconf/config.dat
>
> xrdb -query | grep Xft
>
>
Florian
Thanks for the image - a picture is worth ... and all that jazz.
Certainly, my font display is more like the image on the left.
In response to the awk string:
Name: fontconfig/enable_bitmaps
Template: fontconfig/enable_bitmaps
Value: false
Owners: fontconfig-config
Flags: seen
Name: fontconfig/hinting_type
Template: fontconfig/hinting_type
Value: Autohinter
Owners: fontconfig-config
Flags: seen
Name: fontconfig/subpixel_rendering
Template: fontconfig/subpixel_rendering
Value: Always
Owners: fontconfig-config
Flags: seen
And in response to xrdb -query:
Xft.antialias: 1
Xft.dpi: 120.000000
Xft.hinting: 1
Xft.hintstyle: hintfull
Xft.rgba: none
Any use?
Cheers,
Andy
--
"If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Date: Mon, 30 Jul 2007 15:41:58 -0500
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: Debian user list <debian-user@lists.debian.org>
Subject: Re: Debian can't mount Camera Memory Stick
Message-ID: <46AE4D16.6020605@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
[snip]
I forgot to mention that she has a pendrive which mounts just
fine using the same exact port on the hub into which we plug
the Dazzle.
Here's the line in /etc/fstab
/dev/sdc1 /media/pendrive auto rw,user,noauto 0 0
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Date: Mon, 30 Jul 2007 22:37:52 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: pidgin problem
Message-ID: <20070730203752.GA4417@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jul 30, 2007 at 11:01:54 +0800, Magicloud Magiclouds wrote:
> Dear all,
> I am using unstable brench. Today I did an "apt-get update; apt-get
> upgrade; reboot", then my pidgin can not response to keyboard at all. I can
> not key in anything, but my mouse works well (click, and paste text by
> right-click menu). And all other programs (firefox, and so on) have no
> problems.
Do you get any error messages if you start pidgin from a xterm? Is there
anything in ~/.xsession-errors?
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Mon, 30 Jul 2007 16:24:21 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: searching for graphical torrent client
Message-ID: <20070730202421.GA27045@buddy.mtntop.home>
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Rog=E9rio Brito(rbrito@ime.usp.br) is reported to have said:
> On Jul 27 2007, Kelly Clowers wrote:
> > I haven't used it a lot yet, but transmission seem pretty good so far.
> > It's available in the Debian repo.
>=20
> One good thing about "transmission" (which I am not sure if it is
> present on "rtorrent") is that it features peer exchange, which seems to
> be an extension of Azureus to the bittorrent protocol.
>=20
> Can anybody tell me if rtorrent has Distributed Hashtables (DHT), UPnP,
> and peer exchange? If it has those features, I would have no need for
> other clients.
Not that I can see. Ktorrent does though.
- uTorrent compatible peer exchange
- Port forwarding with UPnP=20
- Support for distributed hash tables (mainline version)
More info with apt-cache show ktorrent, of course.
Wayne
--=20
How an engineer writes a program: Start by debugging an empty file...
_______________________________________________________
Date: Mon, 30 Jul 2007 23:18:25 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: A question of fonts
Message-ID: <20070730211825.GA4579@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jul 30, 2007 at 21:45:07 +0100, andy wrote:
> Florian Kulzer wrote:
[...]
>> This could also be a problem with your settings for font display rather
>> than with the fonts themselves.
[...]
>> Maybe you can post your font settings and we can have a look:
>>
>> awk '/fontconfig/,/^$/' /var/cache/debconf/config.dat
>>
>> xrdb -query | grep Xft
>>
>>
> Florian
>
> Thanks for the image - a picture is worth ... and all that jazz. Certainly,
> my font display is more like the image on the left.
To produce the ugly image I turned off all hinting and anitaliasing. I
also enabled bitmap fonts which are normally disabled on my system. I
normally use Bitstream Vera Sans or Deja Vu Sans as the user interface
font.
> In response to the awk string:
>
> Name: fontconfig/enable_bitmaps
> Value: false
I think this is the correct choice.
> Name: fontconfig/hinting_type
> Value: Autohinter
Maybe you should try "Native" here. You can change these settings with
"dpkg-reconfigure fontconfig-config". (There will be a dialog with
multiple choices.) I think you have to restart X to see the effect of a
changed setting.
> Name: fontconfig/subpixel_rendering
> Value: Always
That should be OK for LCD displays. If all else fails you could try
"Never" or "Automatic".
> And in response to xrdb -query:
>
> Xft.antialias: 1
> Xft.dpi: 120.000000
> Xft.hinting: 1
> Xft.hintstyle: hintfull
> Xft.rgba: none
Strange, those are exactly the Xft seetings which I used for the nice
half of the picture. (Except for Xft.dpi, but that depends on the
display of course.) If you get jagged fonts in this configuration, then
maybe these settings are ignored for some reason. I know that some DEs
can override these settings under certain conditions. Which DE or WM are
you using and how do you start X? Also, if the file ".fonts.conf" exists
in your home directory, can you post its contents?
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Mon, 30 Jul 2007 16:44:42 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: GTK+ File dialog hangs
Message-ID: <46AE5BCA.2020703@cox.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/30/07 12:43, Douglas Allan Tutty wrote:
> On Mon, Jul 30, 2007 at 12:35:08PM -0500, Ron Johnson wrote:
>
>> The closest to that which I have seen is that the larger a directory
>> gets, the longer it takes to open a GTK File dialog. And it just
>> burns up the CPU. If there's more than 12000 files, the File dialog
>> will "never" open.
>>
>
> Wow. I've never had a single directory with 12000 files. What file
> dialog have you tried that does work?
The file picker *used* to handle large directories very well. It
went south around GNOME 2.16, I think. :(
> How do KDE file dialogs handle
> it?
Can't say.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGrlvKS9HxQb37XmcRAoDKAJ9cX0X6Fr5KnoAA5qXOpQ045KQ42ACfTWun
oxDjA2a9laNQoTrUb/Xaqzg=
=akvy
-----END PGP SIGNATURE-----
Date: Tue, 31 Jul 2007 01:03:43 +0300
From: andreimpopescu@gmail.com (Andrei Popescu)
To: debian-user@lists.debian.org
Subject: Re: where is linux-2.6_2.6.22-2.diff.gz?
Message-ID: <20070730220343.GA9439@think>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo"
Content-Disposition: inline
--envbJBWh7q8WU6mo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 30, 2007 at 07:32:06AM -0500, Hugo Vanwoerkom wrote:
=20
> But why there and not in ftp.debian.org?
I think Joey Hess mentioned some problems with ftp.d.o, but you might=20
want to search the archives for the exact quote.
Regards,
Andrei
--=20
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--envbJBWh7q8WU6mo
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGrmA/qJyztHCFm9kRAgs2AJ9Pj6ILIx78fXkZnzuiguvrcf0S7wCfeDlE
4jKIG6xv3McM/DWlENRDzNw=
=gWzt
-----END PGP SIGNATURE-----
--envbJBWh7q8WU6mo--
Date: Tue, 31 Jul 2007 01:15:21 +0300
From: andreimpopescu@gmail.com (Andrei Popescu)
To: debian-user@lists.debian.org
Subject: Re: Debian can't mount Camera Memory Stick
Message-ID: <20070730221521.GB9439@think>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="UHN/qo2QbUvPLonB"
Content-Disposition: inline
--UHN/qo2QbUvPLonB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 30, 2007 at 03:37:58PM -0500, Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>=20
> CPU<--->HUB<--->Dazzle[<--Stick
>=20
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
Since it does work on Windows it is probably not a hardware issue, but=20
did you try to connect the Dazzle directly to the USB port? Also I've=20
heard (on this list) about some strange formating issues, where=20
reformating the USB memory thingy solved the problem ...
Regards,
Andrei
--=20
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--UHN/qo2QbUvPLonB
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGrmL5qJyztHCFm9kRAowPAJ9kI8TzrbfPMJhM//NP0vdEPpIQpACgh3O/
3ZJ/jgC16FzxJrwkSxXK3Qg=
=C0MK
-----END PGP SIGNATURE-----
--UHN/qo2QbUvPLonB--
End of debian-user-digest Digest V2007 Issue #2066
**************************************************
Received on Mon Jul 30 18:38:34 2007