Pmount stopped working in Puppy 4.1

Message

DOSDEMIGOD · #1 Post by **DOSDEMIGOD** » Fri 24 Oct 2008, 21:43

Hello all,

Pmount has just stopped working. It was right after I switched to IceWM.

I am not sure why. It opens..but when I attempt to mount a drive it just closes and does nothing. I installed Pdrive which seems to work perfectly. I can mount and unmount no problem. Any ideas?

Thanks in advance.

disciple · #2 Post by **disciple** » Mon 10 Nov 2008, 11:25

Yes, I may have the same problem. I just got 4.1.1 (never had 4.10) and started setting it up, but Pmount stopped working - not sure if it was caused by changing the locale or the jwm or GTK theme or the wm settings or what. The rox buttons work, but it just closes when I click the refresh button, the mount buttons or the settings button.
I certainly hope we've broken something and it never happens to anyone else, because any user that it happens to should be put off Puppy all together

The new desktop icons thing isn't working for me either. Clicking on a drive just opens pmount, even if the drive is already mounted. I don't think it should open pmount even if the drive is unmounted.
And it really should have a feature to automount drives at bootup - I'm pretty sure that's the main thing people liked Hotpup for.

#3 Post by **BÃ©Ã¨m** » Mon 10 Nov 2008, 13:14

Oh boy,
Same for me in 4.1.1 and jwm.
I didn't notice as I use always the desktop icons for the devices.
Not very helpful, huh.

disciple · #4 Post by **disciple** » Thu 13 Nov 2008, 03:57

Pmount exits at line 295

Code: Select all

[ -s /tmp/pmounterr ] && exit

I'm afraid I don't really understand what line 294 is doing.

disciple · #5 Post by **disciple** » Thu 13 Nov 2008, 12:36

Interesting. I was trying xfce, so I installed xfce_pupevent_410.pet as well and pmount now works, although the desktop icons still just open pmount when I click on them...

alienjeff · #6 Post by **alienjeff** » Thu 13 Nov 2008, 13:30

Barry has noted both this and a USB bug in his dev blog,

Reference: http://puppylinux.com/blog/?viewDetailed=00484

#7 Post by **BÃ©Ã¨m** » Thu 13 Nov 2008, 14:54

This problem has nothing to do with Barry's comment about USB.
I have the same problem when trying to mount IDE HDD's.
It's definitely a problem in the pmount script. (or another script related)

PaulBx1 · #8 Post by **PaulBx1** » Thu 13 Nov 2008, 17:35

I ran pmount from rxvt, mounted sda1, and umounted it, and then quit. I had to ctrl-c out of the rxvt to get it to terminate even though the gui had exited. So pmount *apparently* worked for me, but the rxvt session was not clean:

Code: Select all

# pmount
/usr/sbin/pmount: line 289: 26804 Terminated              yaf-splash -font "8x16" -outline 0 -margin 4 -bg orange -text "Puppy Drive Mounter

Please wait, probing hardware..."
# /usr/sbin/pmount: line 294: 27398 Terminated              yaf-splash -font "8x16" -outline 0 -margin 4 -bg orange -text "Puppy Drive Mounter

Please wait, probing hardware..."
/usr/sbin/pmount: line 294: 28067 Terminated              yaf-splash -font "8x16" -outline 0 -margin 4 -bg orange -text "Puppy Drive Mounter

Please wait, probing hardware..."

#

I am not using xfce or icewm, just the standard jwm.

disciple · #9 Post by **disciple** » Thu 13 Nov 2008, 22:09

Sorry, just to clarify - it was broken before I tried xfce.

DOSDEMIGOD · #10 Post by **DOSDEMIGOD** » Fri 14 Nov 2008, 03:21

I guess this is still unresolved issue? Thanks for your posts guys. I was running Puppy 4.1 and it seemed to be working fine until I loaded the new window manager and themes. I am new to linux..so I am not sure why this would affect a utility that mounts drives.

disciple · #11 Post by **disciple** » Fri 14 Nov 2008, 04:19

I am new to linux..so I am not sure why this would affect a utility that mounts drives.

It shouldn't.

When I can think clearly again I'm going to try to replicate the problem and figure out what's going on. It will probably be a few days though.
In the meantime, you could try installing the .pet that fixed it for me. Search for xfce in the additional software part of the forum. It's not xfce itself, but a little .pet they recommended for the event manager.

disciple · #12 Post by **disciple** » Thu 20 Nov 2008, 10:27

OK, I've been unable to replicate the MUT problem, but as well as finding that installing the xfce event manager .pet fixed mut, I found that after uninstalling it both MUT and the desktop icons are fixed

I guess that .pet must have overwritten whichever file(s) caused the problems...

disciple · #13 Post by **disciple** » Thu 04 Dec 2008, 07:51

Barry sent me a PM trying to track this problem down:

I have a problem with finding the bug in Pmount that you have reported, as I don't have enough information...
...What I need are the contents of those files, after the crash. In /tmp you will find:
/tmp/pmountdlg.txt_${MYPID}
/tmp/pmounterr

The ${MYPID} will be some number, different each time Pmount runs. The latest run will normally have a higher number.

Would appreciate that info!

Does anybody have this problem at the moment, and can help with this?

CatDude · #14 Post by **CatDude** » Thu 04 Dec 2008, 18:59

Hi

I have experienced this, using Puppy-4.1.1-retro,
and i am able to replicate it.

I set up a fresh frugal install, the only thing i did, was to setup the connection.
Pmount was working as one would expect it to.
So i made a backup of this from another puppy install.

Upon booting back into said frugal install,
i decided to download and install this: icewm-1.2.35Latestv2.pet
As posted here: icewm for Puppy 4.0 Plus extras !!!!!2.6MB pet

I am not accusing ttuuxxx or anything, just stating facts.

After the install of the icewm package was finished (i did not restart X),
still in JWM i tried Pmount again, and found that it was broken.

Further investigation revealed that: /usr/share/themes/Gradient-grey
was overwritten when the above mentioned icewm was installed.

Going to: Menu > Desktop > Chtheme GTK theme chooser
Pmount works Ok, using any one of the following EXCEPT Gradient-grey.

Citrus-cut
Default
Emacs
Gradient-brown
Gradient-grey
Raleigh
Stardust

Looking at the contents of /tmp/xerrs.log
i saw quite a few WARNINGS,
such as:

Code: Select all

(gtkdialog2:3112): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(ROX-Filer:5161): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(geany:5368): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(seamonkey-bin:8064): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(ROX-Filer:13485): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(gtk-chtheme:16664): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

So i did a quick search of the forum for clearlooks.
I found, downloaded and installed this: gtk2-engines_2.12.2.pet
As posted here: gtk2-engines theme clearlooks puppy 4.0+
And Gradient-grey is now fixed, and Pmount works when using the Gradient-grey theme.

The files BarryK requested (amongst others) are in the attached file: pmount-problem-411-retro.tar.gz
there are 3 directories inside it

1 = after installing icewm, then trying Pmount.
2 = after a reboot.
3 = after installing gtk2-engines.

Hope this helps
CatDude
.

BarryK · #15 Post by **BarryK** » Thu 04 Dec 2008, 23:02

CatDude,
Thanks for your response.

Looking in your xerrs.log, it has this many times:

/sbin/pup_event_frontend_d: line 503: [: too many arguments

Line 503 in pup_event_frontend_d is this:

if [ $RAMSAVEINTERVAL -ne 0 -a $SAVECNT -gt $RAMSAVEINTERVAL ];then

Now, SAVECNT is a count variable inside pup_event_frontend_d, however
RAMSAVEINTERVAL is got out of /etc/eventmanager. Looking earlier in
the script:

. /etc/eventmanager #has RAMSAVEINTERVAL, ICONDESK, HOTPLUGNOISY, ICONPARTITIONS, BACKENDON
RAMSAVEINTERVAL=`expr $RAMSAVEINTERVAL \* 60` #convert minutes to seconds.

Now, also in xerrs.log, I see this:

expr: syntax error
/sbin/pup_event_frontend_d: line 503: [: too many arguments

...the first time that the "too many arguments" is reported.

By logical deduction, something is wrong with your RAMSAVEINTERVAL in
/etc/eventmanager.
Could you please post what it is?

BarryK · #16 Post by **BarryK** » Thu 04 Dec 2008, 23:31

Pmount fixed, see my blog:

http://puppylinux.com/blog/?viewDetailed=00512

CatDude, still got your problem, see my previous post.

CatDude · #17 Post by **CatDude** » Fri 05 Dec 2008, 11:54

Hello Barry

I wasn't sure whether the contents of: /etc/eventmanager
would be different at the various stages described in my last post.
So i ran through it again, taking note of the contents of: /etc/eventmanager
at all stages the contents were exactly the same.

Here is the contents of: /etc/eventmanager

Code: Select all

#configuration file for 'events' in Puppy.
#this file is read/written by /usr/sbin/eventmanager.

#this parameter is read by /sbin/pup_event_frontend_d...
#For odd-numbered PUPMODE, periodic save in minutes. 0=no periodic save...
RAMSAVEINTERVAL=

#read by pup_event_frontend_d. major switch to kill pup_event_backend_d...
BACKENDON=

#read by pup_event_frontend_d. major switch to turn off all hotplug desktop icon support...
HOTPLUGON=

#read by pup_event_frontend_d. whether hotplug drive icons on desktop or a single 'drives' icon...
ICONDESK=false

#read by pup_event_frontend_d. only effecive if ICONDESK=true. show individual partitions as icons...
ICONPARTITIONS=false

#read by pup_event_frontend_d and /root/.pup_event/drive_*
#true if want an automatic 'handler' to run if a drive plugged in...
HOTPLUGNOISY=false

#read by /root/.pup_event/drive_*
#true if want 'handler' to auto-run appropriate target application...
AUTOTARGET=true

#if /sys/block/fd0 exists, show 'fd0' icon on desktop. Puppy does not detect insert/remove
#of diskettes, so this icon will just remain on desktop. Read by pup_event_frontend_d.
FD0ICON=true

BarryK wrote: CatDude, still got your problem, see my previous post.

Like i said in my previous post
after installing the gtk2-engines_2.12.2.pet
Pmount was once again working OK

CatDude
.

BarryK · #18 Post by **BarryK** » Fri 05 Dec 2008, 21:26

CatDude,
That's your problem, RAMSAVEINTERVAL has no value. Ok, I can put in a workaround for that.

When you ran the Event manager you must have deleted the default entry for RAMSAVEINTERVAL.

I'm puzzled how you got BACKENDON and HOTPLUGON set to nothing. They are radio buttons in the Event manager and are either true or false.

EDIT:
Fixes applied, see my blog.

CatDude · #19 Post by **CatDude** » Sat 06 Dec 2008, 14:59

Hello Barry

BarryK wrote:CatDude,
That's your problem, RAMSAVEINTERVAL has no value. Ok, I can put in a workaround for that.

I do not know how that happened.

BarryK wrote: When you ran the Event manager you must have deleted the default entry for RAMSAVEINTERVAL.

The only thing i did,
was to Right click on one of the desktop drive icons (i was trying to get rid of them)
and selected: Run Desktop Drive Icon Manager
then selected: Show full Event Manager
i then unticked all of the boxes,

2 on the Activate tab
3 on the Desktop Icons tab
2 on the Icon Handler tab
1 on the Legacy tab

that was it.
Pmount was still working OK after doing this,
but there is still one icon (drives) that will not go away.

BarryK wrote: I'm puzzled how you got BACKENDON and HOTPLUGON set to nothing. They are radio buttons in the Event manager and are either true or false.

You and me both mate.

Anyways, i decided to create a Fresh Frugal Install.
I did exactly as i did previously (with regard to unticking boxes)
then i had a look at: /etc/eventmanager

here is the contents:

Code: Select all

#configuration file for 'events' in Puppy.
#this file is read/written by /usr/sbin/eventmanager.

#this parameter is read by /sbin/pup_event_frontend_d...
#For odd-numbered PUPMODE, periodic save in minutes. 0=no periodic save...
RAMSAVEINTERVAL=30

#read by pup_event_frontend_d. major switch to kill pup_event_backend_d...
BACKENDON=false

#read by pup_event_frontend_d. major switch to turn off all hotplug desktop icon support...
HOTPLUGON=false

#read by pup_event_frontend_d. whether hotplug drive icons on desktop or a single 'drives' icon...
ICONDESK=false

#read by pup_event_frontend_d. only effecive if ICONDESK=true. show individual partitions as icons...
ICONPARTITIONS=false

#read by pup_event_frontend_d and /root/.pup_event/drive_*
#true if want an automatic 'handler' to run if a drive plugged in...
HOTPLUGNOISY=false

#read by /root/.pup_event/drive_*
#true if want 'handler' to auto-run appropriate target application...
AUTOTARGET=false

#if /sys/block/fd0 exists, show 'fd0' icon on desktop. Puppy does not detect insert/remove
#of diskettes, so this icon will just remain on desktop. Read by pup_event_frontend_d.
FD0ICON=false

So i have no idea what happened in the last install i did.

With regard to the fix you posted on your blog,
i did as described and Pmount continued to work OK even after i installed the icewm pet.

I still have one question though, how do i get rid of that icon ?

i do not like desktop icons, if i want shortcuts, i put them on wbar.

CatDude
.

BarryK · #20 Post by **BarryK** » Sun 07 Dec 2008, 11:01

I still have one question though, how do i get rid of that icon ? Twisted Evil
i do not like desktop icons, if i want shortcuts, i put them on wbar.

Good question.
Um, I think if you untick everything that has to do with hotplug support, then delete that icon, hopefully it won't come back next time X is started.

That needs to be tidied up though, for those like yourself who want a cleaner desktop. Another checkbox maybe in the Event Manager, to choose not to display any drive icons at all.

...that would have to be for 4.2, as 4.1.2 is in it's final day of testing.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Pmount stopped working in Puppy 4.1

Pmount stopped working in Puppy 4.1

Pmount is broken in 4.1.1

Was anyone able to resolve this issue?