WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: gparted bug in startup script  (Read 6101 times)

Offline hiro

  • Hero Member
  • *****
  • Posts: 1228
gparted bug in startup script
« on: August 30, 2016, 02:01:11 PM »
startup script uses
if test "z`ps -e | grep gpartedbin`" != "z"; then                   
ps -e doesn't exist on standard tinycorelinux so this will match against itself in the ps output, thus gparted is not started.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14633
Re: gparted bug in startup script
« Reply #1 on: August 31, 2016, 04:47:28 AM »
adjusted "ps -e" -> "ps" in sbin/gparted and reposted - thanks

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10992
Re: gparted bug in startup script
« Reply #2 on: August 31, 2016, 09:22:34 AM »
Doesn't it also need "grep -v grep" to filter the grep calls out?
The only barriers that can stop you are the ones you create yourself.

Offline hiro

  • Hero Member
  • *****
  • Posts: 1228
Re: gparted bug in startup script
« Reply #3 on: August 31, 2016, 03:57:48 PM »
i agree with curaga

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14633
Re: gparted bug in startup script
« Reply #4 on: August 31, 2016, 10:48:38 PM »
Could you give an example of exactly the line you'd like to see in the script (I realise there are four of them).

I'd suggest you also report this as a bug to gparted.

Offline hiro

  • Hero Member
  • *****
  • Posts: 1228
Re: gparted bug in startup script
« Reply #5 on: September 01, 2016, 02:00:06 AM »
replace all ps -e | grep bla
with
ps | grep bla | grep -v grep

here it should be:
if test "z`ps | grep gpartedbin | grep -v grep`" != "z"; then

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14633
Re: gparted bug in startup script
« Reply #6 on: September 01, 2016, 07:13:22 AM »
re-modified and posted

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1702
Re: gparted bug in startup script
« Reply #7 on: September 04, 2016, 08:18:56 AM »
/usr/local/share/applications/gparted.desktop  seems to have a bad  Exec=  entry.
Code: [Select]
Exec= /usr/local/sbin/gparted %f
should be
Code: [Select]
Exec=sudo /usr/local/sbin/gparted

edit:
And it has no  X-FullPathIcon= .
« Last Edit: September 04, 2016, 08:21:20 AM by Misalf »
Download a copy and keep it handy: Core book ;)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14633
Re: gparted bug in startup script
« Reply #8 on: September 04, 2016, 10:01:18 AM »
There's been a few conversations about this - basically there's no desktop icon to make it a little harder to make a big mistake with gparted - see info file.

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1702
Re: gparted bug in startup script
« Reply #9 on: September 04, 2016, 10:20:30 AM »
Aha, I see.
Download a copy and keep it handy: Core book ;)

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: gparted bug in startup script
« Reply #10 on: September 04, 2016, 01:45:25 PM »
There's been a few conversations about this - basically there's no desktop icon to make it a little harder to make a big mistake with gparted - see info file.
But where's the fun in that! :p

Offline drunk

  • Newbie
  • *
  • Posts: 8
Re: gparted bug in startup script
« Reply #11 on: December 17, 2016, 01:31:37 AM »
Quote
The process gpartedbin is already running.
Quote
re-modified and posted

Hi!
Could you please fix 'gparted.tcz' for 'v7.2 x86_64' too?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14633
Re: gparted bug in startup script
« Reply #12 on: December 17, 2016, 05:01:18 AM »
posted

@Hiro - did you ever report this to gparted?

Offline hiro

  • Hero Member
  • *****
  • Posts: 1228
Re: gparted bug in startup script
« Reply #13 on: December 17, 2016, 06:22:03 AM »
no, i find the whole script overly badly written, platform specific and rather pointless, so apart from fixing our special case i didn't want to get engaged in this.