Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2979
Today's Topics:
Where to report bug? sparc64 crashes [ Dominik Reusser ]
startx gdm [ Mark Grieveson ]
Re: Installation help [ Cassiano Bertol Leal ]
How to send a function when the lapt [ Jabka Atu ]
printer problem (prints postscript s [ Miles Bader ]
Re: Download Opera brower package [ Angus Auld ]
Date: Mon, 10 Dec 2007 17:11:43 +0100
From: Dominik Reusser <dreusser@uni-potsdam.de>
To: debian-user@lists.debian.org
Subject: Where to report bug? sparc64 crashes probably from mysqld
Message-Id: <200712101711.43808.dreusser@uni-potsdam.de>
Content-Type: Multipart/Mixed;
boundary="Boundary-00=_/UWXHZKKQt+sZkd"
--Boundary-00=_/UWXHZKKQt+sZkd
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
I get unaligned access errors and I suspect mysqld to cause these, as it
reports page corruption just before. How would I find out whether this is
true?
is mysql-server-5.0 the package to file a bug report for the problem. What
else to include in the report?
mysql-Version: 5.0.32-7etch1
Description of what is happening:
mysqld finds a page corruption in a InnoDB database.
The kernel then reports an unaligned access.
mysqld restarts and performs the crash recovery.
unaligned access occurs again and ssh, ping, apache, mysql do not respond
anymore starting from this point.
Based on /var/log/syslog (see attachment) I suspect mysqld causes these
problems.
Any help would be appreciated
--
Dominik Reusser
--Boundary-00=_/UWXHZKKQt+sZkd
Content-Type: text/plain;
charset="us-ascii";
name="syslog.part"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="syslog.part"
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a backup.
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:43 InnoDB: Page dump in ascii and hex (16384 bytes):
Dec 10 10:11:44 libdb mysqld[3524]: len 16384; hex c4deb3030 --snip-- ;InnoDB: End of page dump
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:44 InnoDB: Page checksum 2910718267, prior-to-4.0.14-form checksum 3244052608
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: stored checksum 3302929155, prior-to-4.0.14-form stored checksum 126
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page lsn 49 3962043205, low 4 bytes of lsn at page end 4096
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page number (if stored to page already) 1672847,
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page may be an index page where index id is 0 523
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: (index LocatID_2 of table iller/TBL_Sample)
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a backup.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: It is also possible that your operating
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: system has corrupted its own file cache
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: and rebooting your computer removes the
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: error.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: If the corrupt page is an index page
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: you can also try to fix the corruption
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: by dumping, dropping, and reimporting
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: the corrupt table. You can use CHECK
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: TABLE to scan your table for corruption.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: See also InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: about forcing recovery.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Ending processing because of a corrupt database page.
Dec 10 10:11:45 libdb kernel: Kernel unaligned access at TPC[4c6af0] do_task_stat+0x188/0x588
Dec 10 10:11:45 libdb kernel: Unable to handle kernel paging request in mna handler<1> at virtual address 8000000000a65493
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 000000000000099b
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = fffff80016884000
Dec 10 10:11:45 libdb kernel: \|/ ____ \|/
Dec 10 10:11:45 libdb kernel: "@'/ .. \`@"
Dec 10 10:11:45 libdb kernel: /_| \__/ |_\
Dec 10 10:11:45 libdb kernel: \__U_/
Dec 10 10:11:45 libdb kernel: ps(6642): Oops [#1]
Dec 10 10:11:45 libdb kernel: TSTATE: 0000004411009603 TPC: 00000000004c6af0 TNPC: 00000000004c6af4 Y: 00000000 Not tainted
Dec 10 10:11:45 libdb kernel: TPC:
Dec 10 10:11:45 libdb kernel: g0: fffff800110dd000 g1: 0000000000000013 g2: 8000000000a653e7 g3: 00000000170008a0
Dec 10 10:11:45 libdb kernel: g4: fffff80011062980 g5: 7374617400000000 g6: fffff8001c660000 g7: fffff8001fb41c60
Dec 10 10:11:45 libdb kernel: o0: fffff8001fc82500 o1: fffff8001c663c38 o2: fffff8001c663c30 o3: fffff8001c663d48
Dec 10 10:11:45 libdb kernel: o4: 0000000000000252 o5: fffff80010d18800 sp: fffff8001c6631c1 ret_pc: 00000000004c6a3c
Dec 10 10:11:45 libdb kernel: RPC:
Dec 10 10:11:45 libdb kernel: l0: 0000000000000007 l1: fffff8001c663d48 l2: fffff8001fb86e40 l3: 0000000000000013
Dec 10 10:11:45 libdb kernel: l4: 0000000000000011 l5: 0000000000000001 l6: 0000000000030400 l7: 0000000000000053
Dec 10 10:11:45 libdb kernel: i0: fffff8001fc82500 i1: fffff800148ea000 i2: 0000000000000001 i3: 0000000000000000
Dec 10 10:11:45 libdb kernel: i4: 0000000000000001 i5: 0000000000000000 i6: fffff8001c663451 i7: 00000000004c4aa0
Dec 10 10:11:45 libdb kernel: I7:
Dec 10 10:11:45 libdb kernel: Caller[00000000004c4aa0]: proc_info_read+0x54/0xb4
Dec 10 10:11:45 libdb kernel: Caller[000000000048ab50]: vfs_read+0xa0/0x14c
Dec 10 10:11:45 libdb kernel: Caller[000000000048ae3c]: sys_read+0x34/0x60
Dec 10 10:11:45 libdb kernel: Caller[00000000004069d4]: linux_sparc_syscall32+0x3c/0x40
Dec 10 10:11:45 libdb kernel: Caller[00000000f7f11adc]: 0xf7f11ae4
Dec 10 10:11:45 libdb kernel: Instruction DUMP: c427a78b c45b6008 c6036010 c400a0b0 83286014 da036108 82104002 053ffc00
Dec 10 10:11:45 libdb mysqld_safe[6648]: Number of processes running now: 0
Dec 10 10:11:45 libdb mysqld_safe[6650]: restarted
Dec 10 10:11:47 libdb mysqld[6653]: 071210 10:11:47 InnoDB: Database was not shut down normally!
Dec 10 10:11:47 libdb mysqld[6653]: InnoDB: Starting crash recovery.
Dec 10 10:11:47 libdb mysqld[6653]: InnoDB: Reading tablespace information from the .ibd files...
Dec 10 10:11:48 libdb mysqld[6653]: InnoDB: Restoring possible half-written data pages from the doublewrite
Dec 10 10:11:48 libdb mysqld[6653]: InnoDB: buffer...
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]: WARNING: mysqlcheck has found corrupt tables
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]: /usr/bin/mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... FAST'
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]:
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]: Improperly closed tables are also reported if clients are accessing
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]: the tables *now*. A list of current connections is below.
Dec 10 10:11:49 libdb /etc/mysql/debian-start[6664]:
Dec 10 10:11:50 libdb mysqld[6653]: 071210 10:11:50 InnoDB: Starting log scan based on checkpoint at
Dec 10 10:11:50 libdb mysqld[6653]: InnoDB: log sequence number 58 1742537654.
Dec 10 10:11:50 libdb mysqld[6653]: InnoDB: Doing recovery: scanned up to log sequence number 58 1742537654
Dec 10 10:11:51 libdb mysqld[6653]: InnoDB: Last MySQL binlog file position 0 1080000, file name /var/log/mysql/mysql-bin.000128
Dec 10 10:11:51 libdb mysqld[6653]: 071210 10:11:51 InnoDB: Started; log sequence number 58 1742537654
Dec 10 10:11:51 libdb mysqld[6653]: 071210 10:11:51 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
Dec 10 10:11:51 libdb mysqld[6653]: 071210 10:11:51 [Note] Starting crash recovery...
Dec 10 10:11:51 libdb mysqld[6653]: 071210 10:11:51 [Note] Crash recovery finished.
Dec 10 10:11:51 libdb mysqld[6653]: 071210 10:11:51 [Note] /usr/sbin/mysqld: ready for connections.
Dec 10 10:11:51 libdb mysqld[6653]: Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
Dec 10 10:17:01 libdb /USR/SBIN/CRON[6674]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 10 10:22:36 libdb kernel: Kernel unaligned access at TPC[557c60] pty_chars_in_buffer+0x24/0x50
Dec 10 10:22:36 libdb kernel: Unsupported unaligned load/store trap for kernel at <0000000000557c60>.
Dec 10 10:22:36 libdb kernel: \|/ ____ \|/
Dec 10 10:22:36 libdb kernel: "@'/ .. \`@"
Dec 10 10:22:36 libdb kernel: /_| \__/ |_\
Dec 10 10:22:36 libdb kernel: \__U_/
Dec 10 10:22:36 libdb kernel: sshd(4723): Kernel does fpu/atomic unaligned load/store. [#2]
Dec 10 10:22:36 libdb kernel: TSTATE: 0000004411009600 TPC: 0000000000557c60 TNPC: 0000000000557c64 Y: 00000000 Not tainted
Dec 10 10:22:36 libdb kernel: TPC:
Dec 10 10:22:36 libdb kernel: g0: fffff80017b82ef1 g1: 4557412920284457 g2: 0000000000000001 g3: 0000000000000001
Dec 10 10:22:36 libdb kernel: g4: fffff80018287260 g5: 00000000000019fc g6: fffff80017b80000 g7: 0000000000000000
Dec 10 10:22:36 libdb kernel: o0: fffff80010d18800 o1: fffff8001f8d6340 o2: 00000000006b21d0 o3: fffff80010717000
Dec 10 10:22:36 libdb kernel: o4: 0000000000000000 o5: 0000000000004a00 sp: fffff80017b82f31 ret_pc: 00000000005c57a0
Dec 10 10:22:36 libdb kernel: RPC:
Dec 10 10:22:36 libdb kernel: l0: fffff8001126f1e0 l1: 00000000006b21d0 l2: fffff80010717000 l3: 00000000007694e0
Dec 10 10:22:36 libdb kernel: l4: 0000000000000800 l5: 000000000000001d l6: fffff80010b720e8 l7: 00000000864a0000
Dec 10 10:22:36 libdb kernel: i0: fffff8001038f000 i1: fffff8001038f1e0 i2: 0000000000000000 i3: 0000000000650f78
Dec 10 10:22:36 libdb kernel: i4: 0000000000769070 i5: 0000000000000010 i6: fffff80017b82ff1 i7: 0000000000556238
Dec 10 10:22:36 libdb kernel: I7:
Dec 10 10:22:36 libdb kernel: Caller[0000000000556238]: normal_poll+0x14c/0x17c
Dec 10 10:22:36 libdb kernel: Caller[0000000000551f18]: tty_poll+0x60/0x78
Dec 10 10:22:36 libdb kernel: Caller[000000000049d8d4]: do_select+0x204/0x3bc
Dec 10 10:22:36 libdb kernel: Caller[00000000004b45a8]: compat_core_sys_select+0x11c/0x18c
Dec 10 10:22:36 libdb kernel: Caller[00000000004b6c98]: compat_sys_select+0xe0/0x180
Dec 10 10:22:36 libdb kernel: Caller[00000000004069d4]: linux_sparc_syscall32+0x3c/0x40
Dec 10 10:22:36 libdb kernel: Caller[000000000001c584]: 0x1c58c
Dec 10 10:22:36 libdb kernel: Instruction DUMP: c2586048 22c0400c 90102000 <9fc04000> 01000000 c25e2008 c25060be 80a06002 02400005
--Boundary-00=_/UWXHZKKQt+sZkd--
Date: Sun, 09 Dec 2007 15:38:05 +0100
From: Thilo Six <T.Six@gmx.de>
To: debian-user@lists.debian.org
Subject: Re: gmane suppresses the cc list
Message-ID: <fjgukd$mdk$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Kamaraju S Kusumanchi wrote the following on 09.12.2007 08:01
> I am using gmane to read the Debian mailing list discussions. I am usin=
g
> knode 0.10.5 on unstable for this purpose. The problem I have is that
> whenever a message is sent to multiple lists I am not able to see the o=
ther
> groups on the CC list. Looking at the message, I could not even figure =
out
> if the message is CCed to other groups.This is problematic because
> sometimes the message is copied to one group but the discussion usually
> takes place in another group. Without the CC list it is tough to figure=
out
> the best way to reply to it and take part in the discussion...
>=20
> Any ideas/suggestions overcoming this problem?
>=20
> thanks
> raju
I am reading through gmane with Thunderbird and i am pretty sure gmane
doens=B4t supress the CC(headers). instead i think you need to tell knode=
to
show them.
But sorry i haven=B4t any experience with knode so can=B4t help with that=
.
bye
--=20
Thilo
key: 0x4A411E09
Date: Sun, 9 Dec 2007 01:36:47 -0500
From: Mark Grieveson <dg135@torfree.net>
To: debian-user <debian-user@lists.debian.org>
Subject: startx gdm
Message-ID: <20071209013647.3f047fa8@localhost>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hello. I'm wondering if there is a way to, without using gdm, have x
started, my user logged in, and fluxbox opened, automatically. Perhaps
a script, or something.
Mark
Date: Mon, 10 Dec 2007 11:35:50 -0200
From: Cassiano Bertol Leal <cassianoleal@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Installation help
Message-ID: <475D40B6.9040808@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
cls@truffula.sj.ca.us wrote:
> [This message has also been posted to linux.debian.user.]
> In article <9xSj4-6zc-1@gated-at.bofh.it>, Aumnayan D'Letti wrote:
>> I am installing the latest stable version of Debian (40rl) and am
>> having an issue with how it's seeing my primary HD.
>>
>> It's set up as the master on the primary IDE chain, which to me
>> signifies that it should be seen as IDE1, or HDA. However, the
>> partitioner is picking it up as IDE5 (hde). Which posses no problems
>> for me until the installation is completed, as there is no /dev/hde.
>
> Welcome to the brave new world of udev.
> Device names in /dev are no longer stable. They get created
> on the fly as needed, and they don't always get created
> in the same order from one boot to the next.
> There's a persistence mechanism but you can't rely
> on it yet.
(... snip ...)
You can also use the symlinks from /dev/disk/by-**** . These are created
on the fly as well, but they use some physical characteristics of the
volumes to link them to the correct /dev/[hs]d[a-z].
Cheers,
Cassiano Leal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHXUC2q4Bz51JiUuERAvIRAJ0Q4YBcInPLUNYIN9960k/zeyswIwCeK0gb
JMzryAEIaAEJASX760PqAjQ=
=2kh3
-----END PGP SIGNATURE-----
Date: Sun, 9 Dec 2007 19:21:13 +0200
From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: forwarding _versus_ domain name service on a Linux router
Message-ID: <20071209172113.GA4379@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ"
Content-Disposition: inline
--rwEMma7ioTxnRzrJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Dec 08, 2007 at 08:52:54PM -0800, PETER EASTHOPE wrote:
> Folk,
>=20
> A system, connected to the 'net by a telephone modem,=20
> is configured to be a router providing a network connection=20
> to one Windows system and also to be a workstation.
>=20
> Which is the lesser of evils: running a dns for one client=20
> or forwarding name requests over the slow connection?
Maybe dnsmasq is what you need.
Regards,
Andrei
--=20
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--rwEMma7ioTxnRzrJ
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)
iD8DBQFHXCQJqJyztHCFm9kRAl2QAJ4sd20NqsqVk3rA4seKYGI7soMB4QCfYueW
8Twz6bAKX3xsdAYMVe3R8A8=
=Kt2l
-----END PGP SIGNATURE-----
--rwEMma7ioTxnRzrJ--
Date: Mon, 10 Dec 2007 16:14:43 -0200
From: Cassiano Bertol Leal <cassianoleal@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Where to report bug? sparc64 crashes probably from mysqld
Message-ID: <475D8213.4070905@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Shuler wrote:
> On 12/10/2007 11:04 AM, Cassiano Bertol Leal wrote:
>> Dominik Reusser wrote:
>> [...]
>>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 000000000000099b
>>> Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = fffff80016884000
>>> Dec 10 10:11:45 libdb kernel: \|/ ____ \|/
>>> Dec 10 10:11:45 libdb kernel: "@'/ .. \`@"
>>> Dec 10 10:11:45 libdb kernel: /_| \__/ |_\
>>> Dec 10 10:11:45 libdb kernel: \__U_/
>> [...]
>>
>> Is this for real???
>
> Yes. This is still in the 2.6.23.9 sparc and sparc64 arch
> kernel/traps.c source.
>
> /* Amuse the user. */
> printk(
> " \\|/ ____ \\|/\n"
> " \"@'/ .. \\`@\"\n"
> " /_| \\__/ |_\\\n"
> " \\__U_/\n");
>
LOL... That's why I love free software! Heh!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHXYISq4Bz51JiUuERAnGgAJ9H52oiVsv0Q32dwFWUJnFrP0hN1wCg3668
0qAGb4QyvaPg27/RruJpqxc=
=Lhxu
-----END PGP SIGNATURE-----
Date: Mon, 10 Dec 2007 13:45:32 -0500
From: Kris Deugau <kdeugau@vianet.ca>
To: debian-isp@lists.debian.org
CC: John Miller <jmiller@thecsl.org>, debian-user@lists.debian.org
Subject: Re: OT: SATA Backplanes drivebays and caddies
Message-ID: <475D894C.3070304@vianet.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Joe Emenaker wrote:
> Lately, I've been trying out StarTech's trayless cages and those work
> nicely as well. No trays, no screws... you just open the door, slide the
> drive in, and close the door. If you can operate a refrigerator, you can
> operate these cages.
FWIW, I had a particularly bad experience with a pair of 3-drive cages
from Startech; the LSI Megaraid controller would mark all 6 drives as
FAIL within about 2 hours, from a cold start. Once warmed up, the
"failures" happened within ~10 minutes. Not only did the Startech bays
not work anywhere near "according to spec", I received a grand total of
1 response to the first of a string of messages to their tech support,
about six weeks after I sent the request.
I replaced them with a pair of "Icy Dock" (sorry, don't recall the
company name) cages, and they worked fine for several years. I've only
just recently had trouble with mistaken failures again, most likely
triggered by far too many power failures in a short time. :/
-kgd
Date: Sun, 09 Dec 2007 13:36:50 +0200
From: Jabka Atu <mashrom.head@gmail.com>
To: ML Debian-User <debian-user@lists.debian.org>
Subject: How to send a function when the laptop Lid is closed ?(acpi)
Message-ID: <475BD352.7020407@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,..
There is special file in /proc/acpi that changed it state when the lid
is closed :
/proc/acpi/button/lid/LID (on my acer 5102wlmi).
so if i close the lid it will :
(lid open) cat /proc/acpi/button/lid/LID/state
state: open
(lid closed) cat /proc/acpi/button/lid/LID/state
state: closed
I would like to do a spesific event when it happen (start a timer then
hibernate-disk).
the question is how ?
i tried creating the next file in /etc/acpi/event :
/etc/acpi/events# cat ./lid
event=button[/]lid
action=touch /tmp/lidfilename
Debian testing
- --
- --
Could you at least use man ?
Jabka Atu (aka mha13/Mashrom Head) || bsh83.blogspot.com
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBR1vTUm9p6JnF9I1qAQIxqA//Qk7Br4rVaEFw6LDLpqbnDqUsjPFHDYYU
WlBISCjxfjCo+AEouN7VIpdcFpRTRYb25j4Vehvsq9x3cyucE2E3fuWXKlUCi0uH
f29cHpG7tpqWrlHvocePod2jgMWwo0nc0Y5TtbzjlI7coWxdz+SQZbgMVQqDT7NE
cLfCTT8Fvl6y+ZPvA5MsJtZg/LYnT5mj3I04JQgXyHtewrhec55lSmUh8hrUoIsu
VPQvVDfQc/55pbiFEUHpUiym8ANnCBnY/id4WrBjh5YEB5iBqmKVAyqKWmKyOl3b
z4mGvpZHjQTSmCrfY6RNJfeY7ngSvHU8X/GFAQjT0F+qNTC7yvRpAMTLdyuTI0BS
+4RzV9F1a/jo9KaH/25EEMBxpgqQ18N7+gYClIIuTy97wXhoHKrE0a2kwNGNuLr6
//9bhmQurx/rBw5LWHzHNaet1sKeQF9Flar3HqWxm9BDKYAij+bPN2lpAiqkOP/l
car9ztzeX9ysc+KAONZ8ZJIcFLiavLyod7N435XFpre1Wwx7yvsRL0KFb9qoKx7q
M4e0527OaXZotsHg1RyElhKtV1he2vBId+HrlenpgopUMtVsILty4EEp4E7KzB1f
txXJy6g0EHdWpESYQqIYiFQnADkGjy0v+YYKO53P7xirnquiN0JR+zCyLpsLeCXC
PPi9rAjYOCs=
=rt3m
-----END PGP SIGNATURE-----
Date: Mon, 10 Dec 2007 15:27:15 +0900
From: Miles Bader <miles.bader@necel.com>
To: debian-user@lists.debian.org
Subject: printer problem (prints postscript source, not document)
Message-Id: <buoy7c3njy4.fsf@dhapc248.dev.necel.com>
Content-Type: multipart/mixed; boundary="=-=-="
--=-=-=
My work has a combo copy-machine/fax/printer that works great with
windows (and seems really fast), but I can't seem to get it working
properly with debian/cups.
The printer model is: "Canon iR C4580F"
I managed to locate it on the net, and configured it with cups'
webpage-configuration stuff, and even found a .ppd file for it on
Canon's website (no easy task, as naturally they distribute everything
as windows installable archives...).
The printer seems to use the "IPP" protocol, with a URL of
"ipp://dhypr434:631/ipp" (I've attached the /etc/cups/printers.conf
entry to this message).
The problem is that when I print to this printer, while it _does_ print
something, it prints the _postscript souce code_ for whatever I'm trying
to print! This seems to happen no matter what input I feed cups
(postscript file, pdf file, ...) or what frontend I use (lpr command
from .ps file, mozilla print command, evince print command etc).
So, for instance, a very simple 1 page postscript file (see "test.ps"
attached to this message) results in the printer printing about 8 pages
of postscript source code.
Upon examining the postscript source code thus printed, I see two
things:
(1) It's obviously the same postscript I fed it, but has been
"augmented" by some filter along the way, fleshing out the various magic
comments and adding some setup code etc. I assume cups does this, but I
don't think it's the problem.
(2) The source code is "stair-stepped", with newlines only moving
vertically. This suggests that whoever converted the postscript into
text for printing was expecting a windows line-ending convention.
I suppose (2) could be part of the problem, if somebody along the way is
expecting postscript using windows line-endings, and gets confused
because it gets only unix-style newlines.
If anybody has read this far, do you have any suggestions on where I
could look for the problem?
[Using wireshark, I can see lots of negotiation between cups and the
printer when I print something, but I'm not really sure what's correct
and what's not...]
Thanks,
-Miles
test.ps:
--=-=-=
Content-Type: application/postscript
Content-Disposition: attachment; filename=test.ps
Content-Transfer-Encoding: base64
Content-Description: test.ps
JSFQUy1BZG9iZS0zLjANCiUlVGl0bGU6IHRlc3QucHMNCiUlRm9yOiBNaWxlcyBCYWRlcg0KJSVE
b2N1bWVudERhdGE6IENsZWFuN0JpdA0KJSVPcmllbnRhdGlvbjogUG9ydHJhaXQNCiUlUGFnZXM6
IDENCiUlUGFnZU9yZGVyOiBBc2NlbmQNCiUlRG9jdW1lbnRNZWRpYTogQTQgNTk1IDg0MiAwICgp
ICgpDQolJURvY3VtZW50TmVlZGVkUmVzb3VyY2VzOiBIZWx2ZXRpY2ENCiUlRG9jdW1lbnRQcm9j
ZXNzQ29sb3JzOiBCbGFjayANCiUlRW5kQ29tbWVudHMNCg0KJSVQYWdlOiAxIDENCg0KL0hlbHZl
dGljYSBmaW5kZm9udCA3MiBzY2FsZWZvbnQgc2V0Zm9udA0KDQoxNTAgNTAwIG1vdmV0bw0KKGhl
bGxvIHdvcmxkKSBzaG93DQpzaG93cGFnZQ0KDQolJVRyYWlsZXINCmVuZA0KDQolJUVPRg0K
--=-=-=
cups printer.conf entry:
--=-=-=
Content-Type: application/xml; charset=utf-8
Content-Disposition: attachment; filename=dhypr434.xml
Content-Description: cups printers.conf for dhypr434
<Printer dhypr434>
Info dhypr434
Location 14F
DeviceURI ipp://dhypr434:631/ipp
State Idle
StateTime 1192513184
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
</Printer>
--=-=-=
--
The secret to creativity is knowing how to hide your sources.
--Albert Einstein
--=-=-=--
Date: Sun, 9 Dec 2007 07:38:46 -0800 (PST)
From: Angus Auld <aonghas_auld@yahoo.com>
To: debian-user <debian-user@lists.debian.org>
Subject: Re: Download Opera brower package
Message-ID: <151011.83040.qm@web53010.mail.re2.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
--- Angus Auld <aonghas_auld@yahoo.com> wrote:
>=20
> --- hce <webmail.hce@gmail.com> wrote:
>=20
> > Thanks Mark.
> >=20
> > That works fine. The only thing when I call the
> > opera from the command
> > line, it has following errors although it still
> > works. Should I
> > concern that error messages or not?
> >=20
> >=20
> > ~$ opera
> > ~$ ERROR: ld.so: object 'libjvm.so' from
> LD_PRELOAD
> > cannot be
> > preloaded: ignored.
> > ERROR: ld.so: object 'libawt.so' from LD_PRELOAD
> > cannot be preloaded: ignored.
> > ** Message: plugin_get_value 1 (1)
> >=20
> > ** Message: plugin_get_value 2 (2)
> >=20
> > Thank you.
> >=20
> > Kind Regards,
> >=20
> > Jim
> >=20
> > On 12/4/07, Mark Grieveson <dg135@torfree.net>
> > wrote:
> > > On Mon, 3 Dec 2007 11:29:22 +0000 (UTC)
> > > debian-user-digest-request@lists.debian.org
> wrote:
> > >
> > > > Hi,
> > > >
> > > > I tried to install Opera brower packge from
> the
> > apt-get install, but
> > > > could not find the package? What am I missing?
> > > >
> > > > Thank you.
> > > >
> > > > Jim
> > >
> > >
> > > Just add the following to your
> > /etc/apt/sources.list, update, and then
> > > you'll be able to install opera.
> > >
> > > deb http://deb.opera.com/opera/ etch non-free
> > >
> > > Mark
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> The error is an issue to do with java and preloaded
> Xt. Opera has=20
> a workaround for this. The plugin messages could be
> related to=20
> this, but I am unsure of that.
> Try starting Opera with debugjava option (opera
> --debugjava).=20
> Test your java install here:
>=20
> http://www.java.com/en/download/installed.jsp
>=20
> If the workaround is indeed working, opera
> --debugjava
> will=20
> make this apparent, as well as offer a technical
> explanation=20
> of the issue.
>=20
> Regards.
>=20
> -- Angus
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
To elaborate a little, I have been an Opera user for
many=20
years, first under M$ and for several years now under=20
Linux. I was having so many plugin issues with Opera's
latest releases for Linux (they are working on it),
that I have gone=20
back to Opera 9.20 Build 638
(opera_9.20-20070409.6-shared-
qt_en_i386.deb), an archived version, available here:
http://deb.opera.com/opera/pool/non-free/o/opera/
I am having better results with the older version, but
of course=20
YMMV.
Hopefully this issue is to be worked out soon.=20
More info can be found at Opera Desktop Team site,
here:
http://my.opera.com/desktopteam/blog/
HTH's a little. :)
Regards.
-- Angus
######Linux Laptop powered by Debian Linux######
###########Reg. Linux User #278931###########
___________________________________________________________________=
_________________
Be a better friend, newshound, and=20
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_y=
lt=3DAhu06i62sR8HDtDypao8Wcj9tAcJ=20
End of debian-user-digest Digest V2007 Issue #2979
**************************************************
Received on Tue Dec 11 16:36:19 2007