seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2021/02/25, 15:17:19


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: (NOT solved) gparted: Failed to get D-Bus connection: Unbekannter Fehler -1  (Read 5162 times)

0 Members and 1 Guest are viewing this topic.

Offline michaa7

  • User
  • Posts: 2.129
gparted crashes while scanning the devices:
Quote
$ gksu gparted
glibtop: Non-standard uts for running kernel:
release 3.17-0.towo-siduction-686=3.17.0 gives version code 200960

Failed to get D-Bus connection: Unbekannter Fehler -1
Too few arguments.
======================
libparted : 3.2
======================
Segmentation fault
Too few arguments.

Google knows nothing about it. Do you ;-) ?
« Last Edit: 2014/10/13, 15:05:54 by michaa7 »
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
ok, that's solved. It seems the newer kernels don't cooperate with gksu anymore. But they work with
Code: [Select]
su-to-root -X -c <application>.

I tried suxterm, but didn't understand how to launch gparted even after reading the manual. Not a problem for me because I can use the above cited way, but I wanted give feedback so maybe someone could add some additional info to the manual.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
It is NOT soved:

After starting gparted as mentioned above, it worked for a while, but then it crashed while rescanning the partitions. Now, no matter how I try to start gparted, I get the same error as mentioned above. It *seems* (but I have no clue how to verify) gparted leaves some remnants down the way to nirvana which now prevent the system to restart it agian. This is really annoying.

Any help?
« Last Edit: 2014/10/13, 15:36:03 by michaa7 »
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
dmesg shows a gparted error. Could it somehow be related to the floppy controller? I since some time (I'd say since some kernel update) have errors during boot related to the (always empty) floppy drive. Will have a closer look the next time I am booting.
But maybe the gparted error is unrelated to the floppy error?

Quote
[  122.933504] floppy driver state
[  122.933506] -------------------
[  122.933538] now=4294914176 last interrupt=4294913274 diff=902 last called handler=recal_interrupt [floppy]
[  122.933541] timeout_message=floppy start
[  122.933543] last output bytes:
[  122.933546]  0 90 4294913273
[  122.933549] 13 90 4294913273
[  122.933551]  0 90 4294913273
[  122.933554] 1a 90 4294913273
[  122.933556]  0 90 4294913273
[  122.933558]  3 90 4294913273
[  122.933561] c1 90 4294913273
[  122.933563] 10 90 4294913273
[  122.933566]  7 80 4294913273
[  122.933568]  0 90 4294913273
[  122.933571]  8 81 4294913274
[  122.933573] e6 80 4294913274
[  122.933575]  0 90 4294913274
[  122.933578]  0 90 4294913274
[  122.933580]  0 90 4294913274
[  122.933583]  1 90 4294913274
[  122.933585]  2 90 4294913274
[  122.933587] 12 90 4294913274
[  122.933590] 1b 90 4294913274
[  122.933592] ff 90 4294913274
[  122.933594] last result at 4294913274
[  122.933597] last redo_fd_request at 4294913273
[  122.933600] 20 00                                             .
[  122.933608] status=50
[  122.933610] fdc_busy=1
[  122.933616] do_floppy=main_command_interrupt [floppy]
[  122.933619] delayed work.function=f801e2d0 expires=28
[  122.933622] cont=f8023754
[  122.933624] current_req=f4f523a0
[  122.933626] command_status=-1

[  122.933633] floppy0: floppy timeout called
[  122.933640] end_request: I/O error, dev fd0, sector 0
[  122.933646] floppy: error -5 while reading block 0
[  128.414068] gpartedbin[4588]: segfault at 0 ip   (null) sp b4e8ceb0 error 4 in gpartedbin[8048000+116000]

[  720.006643] floppy driver state
[  720.006645] -------------------
[  720.006676] now=126002 last interrupt=125100 diff=902 last called handler=recal_interrupt [floppy]
[  720.006679] timeout_message=floppy start
[  720.006681] last output bytes:
[  720.006683]  0 90 125100
[  720.006686] 13 90 125100
[  720.006689]  0 90 125100
[  720.006691] 1a 90 125100
[  720.006693]  0 90 125100
[  720.006696]  3 90 125100
[  720.006698] c1 90 125100
[  720.006700] 10 90 125100
[  720.006703]  7 80 125100
[  720.006705]  0 90 125100
[  720.006707]  8 81 125100
[  720.006710] e6 80 125100
[  720.006712]  0 90 125100
[  720.006714]  0 90 125100
[  720.006717]  0 90 125100
[  720.006719]  1 90 125100
[  720.006721]  2 90 125100
[  720.006724] 12 90 125100
[  720.006726] 1b 90 125100
[  720.006729] ff 90 125100
[  720.006731] last result at 125100
[  720.006733] last redo_fd_request at 125100
[  720.006737] 20 00                                             .
[  720.006744] status=50
[  720.006746] fdc_busy=1
[  720.006752] do_floppy=main_command_interrupt [floppy]
[  720.006755] delayed work.function=f801e2d0 expires=28
[  720.006758] cont=f8023754
[  720.006760] current_req=f4f4cbc8
[  720.006762] command_status=-1

[  720.006769] floppy0: floppy timeout called
[  720.006776] end_request: I/O error, dev fd0, sector 0
[  720.006783] floppy: error -5 while reading block 0
[  724.729659] gpartedbin[7339]: segfault at 0 ip   (null) sp b4e5eeb0 error 4 in gpartedbin[8048000+116000]
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
It sometimes works and sometimes crashes immediately, but according to dmesg it really seems floppy related:

From dmesg:
Quote
[ 6902.612823] floppy0: floppy timeout called
[ 6902.612831] end_request: I/O error, dev fd0, sector 0
[ 6902.612837] floppy: error -5 while reading block 0
[ 6910.858503] gpartedbin[4414]: segfault at 0 ip   (null) sp b4ec2eb0 error 4 in gpartedbin[8048000+116000]

I can open gparted 3,4,5 time in row, but then the next time(s) it crashes during the start. It may also crash while runing when I refresh. Even in this occasion dmesg shows the same floppy related lines. It seems gparted scanns, or tries to even the floppy and then encounters some timing error or whatever error occurs.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
I detached the floppy by pulling the cables, no change, I blacklisted "floppy", no change which confuses me completly because now I wonder what causes the system to care about a floppy when there is none and the module isn't available?

towo, any ideas?
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline michaa7

  • User
  • Posts: 2.129
I was hoping disabeling the floppy in the BIOS would help.

Nada.

The dev fd0 error went away, but the gparted error stays
Quote
gpartedbin[32134]: segfault at 0 ip   (null) sp b4ed3eb0 error 4 in gpartedbin[8048000+116000]
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.080
    • Land of the Buckeye
FYI, a quick check on a 32-bit LXDE system (with "gksu") and a 64-bit KDE system (with "kdesu") shows gparted working correctly here.  Both systems are fully updated.  Neither of these systems has a floppy disk drive.
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD1003FZEX in BTRFS

Offline michaa7

  • User
  • Posts: 2.129
Thanks dibl, that's usefull info as now I must assume some failure in my 32bit system (thanks for trying 64bit, too), not in gparted.
Currently I am working with an old firestarter.ISO . And gparted works fine.

So no clue what's wrong with the installation.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.080
    • Land of the Buckeye
... I must assume some failure in my 32bit system ...


It must be in the air today -- I just finished ordering a new mobo and CPU, because a hardware glitch has been haunting me for weeks.
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD1003FZEX in BTRFS

Offline michaa7

  • User
  • Posts: 2.129
... I must assume some failure in my 32bit system ...
It must be in the air today -- I just finished ordering a new mobo and CPU, because a hardware glitch has been haunting me for weeks.
As our clima here in europe mostly is a result from what comes over the atlantic I'm afraid the glitch you had the last weeks now has arrived here. I'll consider to add this to the bugreport I sent some time ago  8)
Ok, you can't code, but you still might be able to write a bug report for Debian's sake