-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, now that I've gotten all of the confusion cleared up, fixing this
should be as simple as changing gparted to use LANG=C.UTF-8 rather
than LANG=C when running dosfsck. It seems that the former causes
dosfsck to disable its normally correct UTF-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ok, I have been able to reproduce this and diagnose the problem. Your 3 1/2
inch floppy link file contains the 1/2 character, which in code page 437 (
the original IBM PC character set ) is 0xBD. In UTF-8, this is an incomplete
multi byte
Package: gparted
Version: 0.18.0-1
Followup-For: Bug #742942
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I noticed that I had another filesystem with the same funny filenames and
checksum errors as on /dev/sdc
From my fsck log:
fsck.fat
Package: gparted
Version: 0.16.1-1
Followup-For: Bug #742942
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Installing any version of gparted from 0.16.1-1 onwards and starting it.
* What exactly did you do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 8:18 AM, Arthur Marsh wrote:
(gpartedbin:15278): glibmm-CRITICAL **: unhandled exception (type
Glib::Error) in signal handler: domain: g_convert_error code : 1
what : Invalid byte sequence in conversion input
* What was the
Phillip Susi wrote, on 22/05/14 22:58:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 8:18 AM, Arthur Marsh wrote:
(gpartedbin:15278): glibmm-CRITICAL **: unhandled exception (type
Glib::Error) in signal handler: domain: g_convert_error code : 1
what : Invalid byte sequence in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 10:08 AM, Arthur Marsh wrote:
Is there any way to pinpoint where in the program the error is
occuring?
Yes, if you can run it under gdb and set a breakpoint in g_log, that
is where these messages are printed. If you can capture a
Phillip Susi wrote, on 22/05/14 23:55:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 10:08 AM, Arthur Marsh wrote:
Is there any way to pinpoint where in the program the error is
occuring?
Yes, if you can run it under gdb and set a breakpoint in g_log, that
is where these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like the problem may have originated in one of the other
threads, and only is being displayed by the main thread. Could you
use the info threads command to list the other threads and use the
thread command to switch to each, and grab a bt
Phillip Susi wrote, on 23/05/14 01:23:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like the problem may have originated in one of the other
threads, and only is being displayed by the main thread. Could you
use the info threads command to list the other threads and use the
thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 12:17 PM, Arthur Marsh wrote:
(gdb) bt #0 0xb7fffa80 in __kernel_vsyscall () #1 0x4102dc5b in
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2 0x413cd8e0 in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought of something else to try. Can you run it under gdb but
*without* setting a breakpoint? It seems this error should result in
the program terminating but you originally said it just hung, so the
question is whether gdb sees a SIGTRAP, and
Phillip Susi wrote, on 23/05/14 02:34:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 12:17 PM, Arthur Marsh wrote:
(gdb) bt #0 0xb7fffa80 in __kernel_vsyscall () #1 0x4102dc5b in
pthread_cond_wait@@GLIBC_2.3.2 () at
Phillip Susi wrote, on 23/05/14 02:55:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought of something else to try. Can you run it under gdb but
*without* setting a breakpoint? It seems this error should result in
the program terminating but you originally said it just hung, so the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 1:34 PM, Arthur Marsh wrote:
fsck.fat 3.0.26 (2014-03-07) Checking we can access the last sector
of the filesystem Boot sector contents: System ID MSWIN4.1 Media
byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per
Package: gparted
Version: 0.18.0-1
Followup-For: Bug #742942
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
# LC_ALL=C gparted
==
libparted : 2.3
==
(gpartedbin:11550): GLib-CRITICAL **: Source ID 7 was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/29/2014 9:24 AM, Arthur Marsh wrote:
(gpartedbin:11550): glibmm-CRITICAL **: unhandled exception (type
Glib::Error) in signal handler: domain: g_convert_error code : 1
what : Invalid byte sequence in conversion input
The older gparted in
Phillip Susi wrote, on 29/04/14 23:04:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/29/2014 9:24 AM, Arthur Marsh wrote:
(gpartedbin:11550): glibmm-CRITICAL **: unhandled exception (type
Glib::Error) in signal handler: domain: g_convert_error code : 1
what : Invalid byte sequence in
Package: gparted
Version: 0.18.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
running gparted /dev/sdc
* What exactly did you do (or not do) that was effective (or
ineffective)?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/29/2014 03:29 AM, Arthur Marsh wrote:
Package: gparted Version: 0.18.0-1 Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
running
20 matches
Mail list logo
