[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#749438: marked as done (iconv maps 0xBD in CP-437 incorrectly)

Your message dated Tue, 27 May 2014 15:21:49 -0400
with message-id <5384E5CD.4070205@ubuntu.com>
and subject line Re: Bug#742942: Bug#749438: gparted stuck at "searching /dev/sdc partitions"
has caused the Debian Bug report #749438,
regarding iconv maps 0xBD in CP-437 incorrectly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
749438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749438
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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)?

program displays "searching /dev/sdc/partitions", does nothing further

when called from command line, I see the output:

gparted /dev/sdc
======================
libparted : 2.3
======================

(gpartedbin:6457): 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 outcome of this action?


   * What outcome did you expect instead?

display of partitions and file systems.



*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14.0-rc8+ (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gparted depends on:
ii  libatkmm-1.6-1      2.22.7-2
ii  libc6               2.18-4
ii  libgcc1             1:4.9-20140322-1
ii  libglib2.0-0        2.38.2-5
ii  libglibmm-2.4-1c2a  2.36.2-1
ii  libgtk2.0-0         2.24.22-1
ii  libgtkmm-2.4-1c2a   1:2.24.4-1
ii  libpangomm-1.4-1    2.34.0-1
ii  libparted0debian1   2.3-17
ii  libsigc++-2.0-0c2a  2.2.11-3
ii  libstdc++6          4.8.2-17
ii  libuuid1            2.20.1-5.7

gparted recommends no packages.

Versions of packages gparted suggests:
pn  dmraid         <none>
ii  dmsetup        2:1.02.83-2
ii  dosfstools     3.0.22-1
ii  gpart          0.1h-11+b1
pn  jfsutils       <none>
pn  kpartx         <none>
ii  ntfs-3g        1:2013.1.13AR.1-2
pn  reiser4progs   <none>
pn  reiserfsprogs  <none>
ii  xfsprogs       3.1.9
ii  yelp           3.10.1-1

-- debconf-show failed

--- End Message ---
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm not sure why this conversation got dragged over to the wrong bug
#, but I'm putting it back and closing it.  I realized finally that I
was just looking at the table wrong and the value I was looking at was
in fact, the UTF-16 value for the character rather than the value in
that CP.  It is very odd that this character is not the same value in
CP-437 and CP-1252/ISO-8859-1, but that does appear to be the case.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJThOXKAAoJEI5FoCIzSKrwMFIIAJOz5e/zqcafS02hjDQNhjoA
I5rPGN1XxXQh22jpX/sO37mw2ZZDuAEyQa3DMatIZ9OlB0T1RQ7p0Z8OCLw/MgJQ
Bx/SLVL94AH/0CDuqT93oHqBCkPxEpdaQ5/ooiWTVm39QjAFvgU6wPZRwRRwtg7A
TZqgqy4zZePBEMrusGygAv4sW9VBslth4bLSFfywphUSYzVAGXnwRjflL7vIavHv
JYF6R0Fgy69d+nSlEKLs1OEF/GSluCk+grz7nF1Gf9vwmQG+QcIyVOYXRWVt26jj
Ic4mT609AV6illyGe6cjeYhYEmJ67wgQs368TzMCw6iIbV7yjYaS1ArL5BwnSj8=
=5tG5
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: