From: Chong Yidong <cyd@stupidchicken.com>
To: emacs-devel@gnu.org
Subject: [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem
Date: Sat, 23 Feb 2008 17:00:52 -0500 [thread overview]
Message-ID: <877igvl4dn.fsf@stupidchicken.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 73 bytes --]
Does anyone here have a vfat/ntfs partition for investigating this bug?
[-- Attachment #2: Type: message/rfc822, Size: 10058 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 3212 bytes --]
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing
list,
and to the gnu.emacs.bug news group.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
The problem I have occurrs every time I start emacs so that my current
directory is either on a vfat fileystem or ntfs filesystem. Emacs
starts,
but it complains about errors when opening output file while processing
my .emacs file and the other files it tries to load.
I do not have emacs runing in a debugger, but I started it with
--debug-init
as instructed, and the resulting output is attached to this e-mail.
Best regards,
Petri Kaurinkoski
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/22.1/etc/DEBUG for instructions.
In GNU Emacs 22.1.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2007-12-15 on noname, modified by Debian
Windowing system distributor `The X.Org Foundation', version
11.0.10300000
configured using `configure '--build=i486-linux-gnu'
'--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib'
'--libexecdir=/usr/lib' '--localstatedir=/var/lib'
'--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs22:/etc/emacs:/usr/local/share/emacs/22.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/22.1/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/22.1/leim' '--with-x=yes' '--with-x-toolkit=athena' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g -O2''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: C
locale-coding-system: nil
default-enable-multibyte-characters: t
Major mode: HTML
Minor modes in effect:
show-paren-mode: t
encoded-kbd-mode: t
tooltip-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
Recent input:
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <menu-bar> <help-menu>
<report-emacs-bug>
Recent messages:
File error: Opening output file, invalid
argument, /mnt/scratch/Uinti/hss/doc/www/raw_html/hss/fin/petrin/uinti/#*scratch*#20913s5z#
To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file. Start Emacs with
the `--debug-init' option to view a complete error backtrace.
Loading sgml-mode...done
Loading emacsbug...
Loading regexp-opt...done
Loading emacsbug...done
--
Petri Kaurinkoski <Petri.Kaurinkoski@iki.fi>
[-- Attachment #2.1.2: emacs-backtrace.dump --]
[-- Type: application/octet-stream, Size: 2559 bytes --]
next reply other threads:[~2008-02-23 22:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 22:00 Chong Yidong [this message]
2008-02-23 22:22 ` [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem Eli Zaretskii
2008-02-23 22:30 ` Chong Yidong
2008-02-23 22:33 ` David Kastrup
2008-02-24 4:16 ` Eli Zaretskii
2008-02-24 14:36 ` Jason Rumney
2008-02-24 15:39 ` Stefan Monnier
2008-02-24 15:44 ` Miles Bader
2008-02-24 16:01 ` Jason Rumney
2008-02-24 19:44 ` Eli Zaretskii
2008-02-24 20:41 ` Stefan Monnier
2008-02-25 10:57 ` Richard Stallman
2008-02-25 15:57 ` Stefan Monnier
2008-02-26 12:36 ` Richard Stallman
2008-02-24 19:43 ` Eli Zaretskii
2008-02-24 23:04 ` Richard Stallman
2008-02-24 23:44 ` Jason Rumney
2008-02-25 19:01 ` Richard Stallman
2008-02-25 23:58 ` Jason Rumney
2008-02-26 1:57 ` Stefan Monnier
2008-02-26 3:41 ` Chong Yidong
2008-02-26 4:53 ` Stefan Monnier
2008-02-26 9:07 ` Jason Rumney
2008-02-26 9:39 ` Jason Rumney
2008-02-26 15:18 ` Stefan Monnier
2008-02-24 22:30 ` Richard Stallman
2008-02-24 15:23 ` Richard Stallman
2008-02-24 20:01 ` Eli Zaretskii
2008-02-25 10:57 ` Richard Stallman
2008-02-25 20:04 ` Eli Zaretskii
2008-02-25 20:52 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877igvl4dn.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).