Confirming that "exit 1" instead of 0 like the Debian bug report fixed
my PRS300 problem.
--
some ebook readers not detected without calibre-mount-helper
https://bugs.launchpad.net/bugs/561958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
PRS300 user here. Tried creating the dummy script but seems the script
is a bit more involved.
Unable to open device
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/device.py", line 106, in do_connect
dev.open()
File "/usr/lib/calibre/calibre/devices/prs505/driver.p
OpenOffice says this issue is fixed (
http://qa.openoffice.org/issues/show_bug.cgi?id=49426 and
http://qa.openoffice.org/issues/show_bug.cgi?id=19976 ) but I still see
this bug in Hardy.
--
[Upstream] [hardy] openoffice apps are rude and steal wm focus
https://bugs.launchpad.net/bugs/20767
You re
Tcsh seems to handle the "!" mark in file names more gracefully now, but
no, it's still not saved properly in the history file.
$ echo bye\!\! > file
$ history -S
$ tail ~/.history
...
#+1224787164
echo bye!! > file
#+1224787166
history -S
The file .history is saved incorrectly.
$ tcsh
$
Thanks for your advice. Indeed it dies with:
/usr/lib/scim-1.0/scim-panel-gtk: error while loading shared libraries:
libscim-gtkutils-1.0.so.8: cannot open shared object file: No such file or
directory
Installing scim-gtk2-immodule fixed the problem. I wonder the
dependencies were broken somewhe
Public bug reported:
Binary package hint: tcsh
tcsh fails to save commands with "!" in the .history file properly.
Since "!" is a special character for tcsh, it needs to be escaped by a
backslash character. Auto-expansion automagically adds the backslash.
However, this is not the case for the .hi
Attached in the .history file (yeah, I know my privacy is now bust:)
Replace your .history file with the one attached, and tcsh segfaults.
Removing random lines removes the segfault, though.
** Attachment added: "history.bz2"
http://launchpadlibrarian.net/8310091/history.bz2
--
tcsh segmentat
I've narrowed it down to problems in the .history file, but this is as
far as I can get. It is not a short history list, but removing any more
lines will simply remove the segfault. Possible reason might be non-
ASCII characters at certain positions. The same .history file will
segfault tcsh in Fre
I'm also experiencing sudden segfaults with tcsh. Don't know what I did
but I've been using it as a login shell till this morning. Symptoms are
identical to Sami Nybacka; "tcsh -f" works, "source" works, without -f
crashes.
--
tcsh segmentation fault
https://bugs.launchpad.net/bugs/86683
You rece
