Custom Query (1145 matches)

Reported by geofft, 15 years ago.

I installed debathena-afs-config on a stock* Karmic live CD, and in the setup process, pyhesiodfs crashed and generated a file in /var/crash. The non-irrelevant portions of that file are:

PythonArgs: ['/usr/bin/pyhesiodfs', '-f', '/mit', '-o', 'nonempty']
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/pyhesiodfs", line 226, in <module>
     main()
   File "/usr/bin/pyhesiodfs", line 223, in main
     server.main()
   File "/usr/lib/python2.6/dist-packages/fuse.py", line 754, in main
     main(**d)
 FuseError: filesystem initialization failed

It would be great to catch the error and deal; it would also be okay not to make an entry in /var/crash and pop up an alert icon in my tray.

*Okay, I also installed debathena-ssh-config in advance and then loop-mounted an ext2 disk image from /tmp to /var/cache/openafs so I wouldn't have to deal with memcache. But that worked fine and isn't relevant.

Reported by pweaver, 15 years ago.

When a job is removed using lprm and it is the active job the job still continues to print even when it is removed from the queue and the printer is restarted.

Reported by fawkes, 15 years ago.

I printed a ruby script (via lpr) that contained some hirigana to meadow. They printed as blank boxes.

Geoff told me to file a ticket. So I did.