2.13 Beta bugs
I've been using pmount lately instead of MUT and I agree, it's the 'open with ROX' button I miss.
I also find myself having to think twice whether 'red' or 'green' means 'mount' or 'unmount' (I realize that when a drive is mounted, details show up to the left).
However, MUT's use of 'mount' and 'unmount' can't be much clearer.
Paul
EDIT: I'm no graphics artist, but how about modifying the icons something like this
I also find myself having to think twice whether 'red' or 'green' means 'mount' or 'unmount' (I realize that when a drive is mounted, details show up to the left).
However, MUT's use of 'mount' and 'unmount' can't be much clearer.
Paul
EDIT: I'm no graphics artist, but how about modifying the icons something like this
- Attachments
-
- pmount_icons.jpg
- (15.18 KiB) Downloaded 1064 times
Last edited by pakt on Thu 28 Dec 2006, 10:29, edited 1 time in total.
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
bump
/me is the only one with lock screen not functioning on 2.13 beta?
Re: bump
Yes, there is a problem with 'lock' in 2.13beta, but it will only show up if you don't already have /root/.xlockrcdebernardis wrote: /me is the only one with lock screen not functioning on 2.13 beta?
If /root/.xlockrc is missing, the usual (for 2.13beta) problem of mrxvt vs. rxvt problem surfaces.
This is what happens in the lock script if I execute part of the offending line in mrxvt
It's a good thing Barry is putting the rxvt binary back in# rxvt -bg orange -g 36x1 -title "Create key (password)"
mrxvt: bad option "key"
mrxvt: bad option "(password)"
mrxvt: Use -h, -help or --help to get help
#
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Crash booting
I have a P4 3GHz hyper threaded system. It has the onboard shared memory graphics adapter and I also have an ATI Catalyst on the PCI bus. If I boot with the ATI selected as the primary graphics adapter 2.13 crashes. If I switch back and set the embedded controller as default it boots, but I get the problem iof X not running and can't even get XVesa to run.
I modified pmount with a rox launcher and Barry downloaded my modified code. Not sure why he didn't include it since it seems to work good for me.
You can get it in this thread:
http://www.murga-linux.com/puppy/viewto ... 3&start=15
I know dougal's been modifying pmount too so maybe he'll include that feature.
You can get it in this thread:
http://www.murga-linux.com/puppy/viewto ... 3&start=15
I know dougal's been modifying pmount too so maybe he'll include that feature.
Thanks, plinej, I missed that thread. I just tried it and it works greatplinej wrote:I modified pmount with a rox launcher and Barry downloaded my modified code. Not sure why he didn't include it since it seems to work good for me.
Yes, he has streamlined it. He sent me a copy to test - it is 30% faster on the eBox, where the difference is quite noticeable. He told me he has been quite busy, so he probably hasn't had time to post his version yet. Seems like merging his version with yours will make pmount a real winnerplinej wrote: I know dougal's been modifying pmount too so maybe he'll include that feature.
EDIT: I've PM'ed Dougal, asking him if I can post his version for him. Then, if you like, you could perhaps merge the two versions. Maybe we can make it into 2.13 final
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
bugs
Just out of perverse and morbid curiosity, are unresolved 2.12 bug reports "carried over" to 2.13 for consideration and hopefully resolution? The reason I ask is this: while trying to use gcrontab in v2.12, I noted that clicking the help icon in the gui resulted in my browser to report " /usr/local/share/gcrontab/help/C/gcrontab-DOC.000.html cannot be found. Please check the location and try again." The link works in v2.01, so somewhere along the 2.01>2.12 path the link was broken.
I resorted to http://www.unixgeeks.org/security/newbi ... ron-1.html for the help needed, so save your links. heh.
The question of pre-existing bug resolution is what I'd like addressed and/or discussed.
Thanks.
I resorted to http://www.unixgeeks.org/security/newbi ... ron-1.html for the help needed, so save your links. heh.
The question of pre-existing bug resolution is what I'd like addressed and/or discussed.
Thanks.
[size=84][i]hangout:[/i] ##b0rked on irc.freenode.net
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
Sorry to sing a sour note about pmount, but besides the missing ROX button (which I use a lot), it also has an actual bug in handling USB flash drives, that MUT does not have:A lot of people like MUT. As long as it is there on the menu, they are accommodated. IMHO we have to use as default what works and is known to work. In the case of the Rox update, it makes sense to change to Pmount as default desktop icon.
http://www.murga-linux.com/puppy/viewtopic.php?t=13267
See my last post for an updated description of the problem.
My opinion is this needs to be cleaned up before making pmount the default, as it causes no end of confusion.
The problem with the pup_213.sfs not being loaded from the hard drive is a SATA drive problem. If I boot with "puppy PMEDIA=satahd" boot option, then the pup_213.sfs file IS loaded from the hard drive. If I don't pass that option then it loads from the CD and sets PUPMODE=13.
Just tried booting 2.12 from the CD, same problem. I got this laptop a couple weeks ago and went straight to a frugal install of 2.12. Had the same kind of problem with PUPMODE=13, so I added PMEDIA=satahd to grub.
Here's my PUPSTATE file when booting 213B from CD:
PUPMODE=13
PDEV1='hdc'
DEV1FS='iso9660'
PUPSFS='pup_213.sfs'
PUPSAVE='ext3,sda4,/pup_save.2fs'
PMEDIA='idecd'
SATADRIVES='sda '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_ro1'
PUP_LAYER='/pup_ro2'
ZDRV='ext3,sda4,/zdrv_213.sfs'
Just tried booting 2.12 from the CD, same problem. I got this laptop a couple weeks ago and went straight to a frugal install of 2.12. Had the same kind of problem with PUPMODE=13, so I added PMEDIA=satahd to grub.
Here's my PUPSTATE file when booting 213B from CD:
PUPMODE=13
PDEV1='hdc'
DEV1FS='iso9660'
PUPSFS='pup_213.sfs'
PUPSAVE='ext3,sda4,/pup_save.2fs'
PMEDIA='idecd'
SATADRIVES='sda '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_ro1'
PUP_LAYER='/pup_ro2'
ZDRV='ext3,sda4,/zdrv_213.sfs'
PaulBx1, have you tried plinej's modified version of pmount? (see 8 posts up in this thread).PaulBx1 wrote:Sorry to sing a sour note about pmount, but besides the missing ROX button (which I use a lot)
He has added the ROX buttons Works great.
There just remains the incorrect-description problem you mentioned.
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Is the universal installer working?
I tried installing 2.13Beta on my laptop last night, and once I got through all the prompts, rebooted, I was presented with a question: where do I want grub to be installed?
Ok, that's odd, since I was already asked that. I installed grub, rebooted, and once I pointed grub at the correct install...nothing: no error messages, no hard drive activity just a black screen. Odd.
I will try it again tonight to see if I can replicate that.
Other than that, there may be an issue with ROX proper: some of the icon launchers did not work at all (setup for example) where the underlying apps worked fine from menu. Actually, anything related to ROX seemed sort of slow, whereas using the menus (or console) the whole system was blazing.
The system I used was:
Compaq Presario 2100US
1.5 ghz Celeron
512 RAM
40GB HD
64mb IGP Radeon
I will test it proper on my desktop.
I tried installing 2.13Beta on my laptop last night, and once I got through all the prompts, rebooted, I was presented with a question: where do I want grub to be installed?
Ok, that's odd, since I was already asked that. I installed grub, rebooted, and once I pointed grub at the correct install...nothing: no error messages, no hard drive activity just a black screen. Odd.
I will try it again tonight to see if I can replicate that.
Other than that, there may be an issue with ROX proper: some of the icon launchers did not work at all (setup for example) where the underlying apps worked fine from menu. Actually, anything related to ROX seemed sort of slow, whereas using the menus (or console) the whole system was blazing.
The system I used was:
Compaq Presario 2100US
1.5 ghz Celeron
512 RAM
40GB HD
64mb IGP Radeon
I will test it proper on my desktop.
dunno why i'm posting
that would be a real pity. mut is one of the best things about puppy. no util, not even pmount, which is cool, makes mounting easier on people that are new to linux. there's automount, but that's just no good. suggestion: maintain mut... it would have been cool to see a cli version of mut for one bone too... ah well. EDIT: i stand by my suggestion regarding mut, but i will note that i was under the impression (based on his apparent love of tcl/tk) that barry wrote mut, and i couldn't understand why he wouldn't maintain it. it's a REALLY good util. but today i saw it was actually written by jesse liley. eh.Hmm, I wonder if we should change the "drives" icon on the desktop to use Pmount, as MUT is not really being maintained.
In Pmount, a ROX window open on a partition that is to be unmounted is first closed before the unmount.
ROX-Filer
Hi all,
this is my first shot at using the bug report, I hope I am in the
right place for this report. I am new to playing with these puppies!
I have downloaded a few versions of these little fellows, right now I
have got versions V2.0, 2.02, 2.10, 2.11, 2.12, 2.13BETA and 2.13 FINAL!
I have been playing with V2.13 FINAL and the front desk looks i.e. background wallpaper, icons and their font texts. I have found that the text for me is not as crisp and sharp (yes I have checked my glasses)as that used in v2.12, I have tried the various fonts offered via ROX-Filer in the "Pinboard" menu window, and I am not happy with the selection, maybe it would be better with an LCD screen? It would be nice to have back in V2.13, the "RECTANGULAR BACKGROUND SLAB" function this adds great value to the use of various background wallpapers. The slab colour is there to be changed but it can't be actioned. I want to get a version working well so as to pass on to a mate who is strugling with a HP machine using WIN98E with 64Mb mem and 5400rpm HD How do I add these changes?
Cheers Tui
this is my first shot at using the bug report, I hope I am in the
right place for this report. I am new to playing with these puppies!
I have downloaded a few versions of these little fellows, right now I
have got versions V2.0, 2.02, 2.10, 2.11, 2.12, 2.13BETA and 2.13 FINAL!
I have been playing with V2.13 FINAL and the front desk looks i.e. background wallpaper, icons and their font texts. I have found that the text for me is not as crisp and sharp (yes I have checked my glasses)as that used in v2.12, I have tried the various fonts offered via ROX-Filer in the "Pinboard" menu window, and I am not happy with the selection, maybe it would be better with an LCD screen? It would be nice to have back in V2.13, the "RECTANGULAR BACKGROUND SLAB" function this adds great value to the use of various background wallpapers. The slab colour is there to be changed but it can't be actioned. I want to get a version working well so as to pass on to a mate who is strugling with a HP machine using WIN98E with 64Mb mem and 5400rpm HD How do I add these changes?
Cheers Tui
Last edited by Tui on Thu 04 Jan 2007, 12:17, edited 1 time in total.
Re: ROX-Filer
I just switched today to CRT/VGA/XVESA from LCD/XORG Seems like you might have a point.Tui wrote:maybe it would be better with an LCD screen?
Although I do prefer the font type change itself. Something does seem a bit fuzzy now.