From: Edward Shishkin <edward.shishkin@gmail.com>
To: Serkan Kaba <serkan@gentoo.org>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: problem with GNOME 2.30
Date: Mon, 12 Apr 2010 02:07:51 +0200 [thread overview]
Message-ID: <4BC26457.5020107@gmail.com> (raw)
In-Reply-To: <4BC15348.80205@gentoo.org>
Serkan Kaba wrote:
> After an upgrade to GNOME 2.30 I cannot create new files with data
> (i.e save as) or cpoy/move files into reiser4 partition. The files are
> created with no content (i.e 0 bytes). Command line copy/move works as
> expected. And the issue happens with combination of GNOME 2.30 and
> reiser4 (other combinations do work) I also reported this to GNOME
> bugzilla (http://bugzilla.gnome.org/show_bug.cgi?id=615346) , but do
> you have any idea what may be causing it?
Sorry, no ideas.
Try to figure out why gnome ask VFS to create empty files.
Thsnks,
Edward
next prev parent reply other threads:[~2010-04-12 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 4:42 problem with GNOME 2.30 Serkan Kaba
2010-04-12 0:07 ` Edward Shishkin [this message]
2010-04-13 1:23 ` Christian Kujau
2010-09-12 17:30 ` Serkan Kaba
2010-09-12 17:53 ` Edward Shishkin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC26457.5020107@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=serkan@gentoo.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.
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 NNTP newsgroup(s).