Saluki
XfcePowerTools
I've released a new version of the XfcePowerTools pet that fixes the localization error and a minor .desktop file adjustment. Also redesigned the layout to hopefully be easier to find items and be more visually appealing.
Details available at Saluki-Linux.
Details available at Saluki-Linux.
Last edited by elroy on Fri 31 Aug 2012, 21:39, edited 1 time in total.
Edit: 06/09/2012
Updated to version 2.6.9
The inbuilt editor is now disabled if there is no locale with UFT-8 support.
Added a reset to default for the inbuilt editors color and font settings.
Please test, as before it should be ok, I've tested numerous times.
Here is my latest attempt with xmenumaker, this version has a number of new features and a renewed text editor built with yad.
To begin with this version relies on locale settings to enable the text editor to function correctly.
if you generally don't use .UFT-8 then you will have to enable it once then you can disable it again,
this will be listed in /usr/lib/locale.
Typing locale -a in the terminal will list the locale types, there should be two for your locale one having .UFT-8
This is needed else the editor won't be able save all character sets and will possibly break the desktop files.
features of the text editor are the ability to change background and text color as well as the font.
I tried a different approach with this by saving the configuration settings back to xmenumaker thus no separate config file, this appears to work fine.
If you wish you can opt to use the system default text editor and bypass the yad editor by selecting the checkbox.
Added a undo button, this will allow for either the delete or edit's last action to be restored.
On the side menu are buttons to copy to desktop, hide or show a menu entry and add or remove from the Favorites menu.
To use these features a custom-xfce-applications.menu is used, which can be placed anywhere that you wish.
To switch to the custom menu, right-click the Saluki icon on the taskbar and select Properties, Use custom menu file,
then navigate to the custom-xfce-applications.menu where ever you have placed it, I keep mine in /root/.config
Extract the two .directory files, place them in /usr/share/desktop-directories, one for a Development menu the other Favorites menu.
At the moment there are no icons in the Desktop icon switcher allocated from these menu entries,
so I've selcted them from the hicolor theme.
The main Gui as also changed slightly, with error messages for all main entries, the categories now has a full list of entries to choose from, new layout cleaner look.
I will call this more of a version for testing to get some feedback on it's functionality and any bugs, though it should be bug free.
I would suggest at the lest to backup your applications directory.
Or try this with a new save file, I'd hate for anyone to wreck their installation.
At present there is no list for the hidden menu entries, I will add a button to list them in the next version.
Updated to version 2.6.9
The inbuilt editor is now disabled if there is no locale with UFT-8 support.
Added a reset to default for the inbuilt editors color and font settings.
Please test, as before it should be ok, I've tested numerous times.
Here is my latest attempt with xmenumaker, this version has a number of new features and a renewed text editor built with yad.
To begin with this version relies on locale settings to enable the text editor to function correctly.
if you generally don't use .UFT-8 then you will have to enable it once then you can disable it again,
this will be listed in /usr/lib/locale.
Typing locale -a in the terminal will list the locale types, there should be two for your locale one having .UFT-8
Code: Select all
# locale -a
C
en_AU
en_AU.utf8
en_US
POSIX
features of the text editor are the ability to change background and text color as well as the font.
I tried a different approach with this by saving the configuration settings back to xmenumaker thus no separate config file, this appears to work fine.
If you wish you can opt to use the system default text editor and bypass the yad editor by selecting the checkbox.
Added a undo button, this will allow for either the delete or edit's last action to be restored.
On the side menu are buttons to copy to desktop, hide or show a menu entry and add or remove from the Favorites menu.
To use these features a custom-xfce-applications.menu is used, which can be placed anywhere that you wish.
To switch to the custom menu, right-click the Saluki icon on the taskbar and select Properties, Use custom menu file,
then navigate to the custom-xfce-applications.menu where ever you have placed it, I keep mine in /root/.config
Extract the two .directory files, place them in /usr/share/desktop-directories, one for a Development menu the other Favorites menu.
At the moment there are no icons in the Desktop icon switcher allocated from these menu entries,
so I've selcted them from the hicolor theme.
The main Gui as also changed slightly, with error messages for all main entries, the categories now has a full list of entries to choose from, new layout cleaner look.
I will call this more of a version for testing to get some feedback on it's functionality and any bugs, though it should be bug free.
I would suggest at the lest to backup your applications directory.
Or try this with a new save file, I'd hate for anyone to wreck their installation.
At present there is no list for the hidden menu entries, I will add a button to list them in the next version.
- Attachments
-
- xmenumaker-2.6.9.tar.gz
- extract and place in /usr/sbin
backup the original - (8.39 KiB) Downloaded 358 times
-
- xmenumaker-2.6.7.tar.gz
- extract and place in /usr/sbin
backup the original - (8.17 KiB) Downloaded 328 times
-
- xmenumaker.jpg
- (76.26 KiB) Downloaded 1575 times
-
- custom-xfce-applications.menu.gz
- In the panel right-click the applications menu go to
properties select Use custom menu file navigate to the
custom-xfce-applications.menu, I keep mine in /root/.config - (1.07 KiB) Downloaded 291 times
-
- Puppy-Development.directory.gz
- extract and place in /usr/share/desktop-directories
- (125 Bytes) Downloaded 335 times
-
- Puppy-Favorites.directory.gz
- extract and place in /usr/share/desktop-directories
- (125 Bytes) Downloaded 375 times
Last edited by Geoffrey on Thu 06 Sep 2012, 06:02, edited 1 time in total.
[b]Carolina:[/b] [url=http://smokey01.com/carolina/pages/recent-repo.html]Recent Repository Additions[/url]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
-
- Posts: 597
- Joined: Thu 13 Nov 2008, 13:45
I am currently testing 23 on an Asus eeePC 701, booting from sD card. Seems to work for the most part, but there is a possible bug.
It will not unmount this USB stick I have. Tried about 5 or 7 times, sometimes it even crashes the o.s. altogether.
I'll eventually test with another USB stick, but I would like to say that there is nothing wrong with the one that is making Saluki crash, it works in any and every other o.s., including Windows, MacOS, Ubuntu, several Puppies, Slax, etc.
Strangely enough, my USB hard drive unmounts properly.
It will not unmount this USB stick I have. Tried about 5 or 7 times, sometimes it even crashes the o.s. altogether.
I'll eventually test with another USB stick, but I would like to say that there is nothing wrong with the one that is making Saluki crash, it works in any and every other o.s., including Windows, MacOS, Ubuntu, several Puppies, Slax, etc.
Strangely enough, my USB hard drive unmounts properly.
Sometimes when I try to change directory to /mnt/home, no file shows up. It seems to be unmounted, but when I quit Saluki, the pupsave file can be saved properly.
I am using Saluki on an Eeepc 900
I am using Saluki on an Eeepc 900
Last edited by songzi on Mon 03 Sep 2012, 21:30, edited 1 time in total.
Puppy Linux | Arch | antiX
Does it make any difference which usb port you use? I have an Acer netbook which behaves differently on one of the ports. Also, what method do you use for the unmount?mini-jaguar wrote:It will not unmount this USB stick I have. Tried about 5 or 7 times, sometimes it even crashes the o.s. altogether.
Default xfce4 menu categories are here /etc/xdg/menus/xfce-applications.menusakamoto wrote:where are the default xfce4 menu categories defined? i understood that no custom categories were defined as i cannot find anything in the ./config folder
thanks
The corresponding .directory files here /usr/share/desktop-directories
cheers
[b]Carolina:[/b] [url=http://smokey01.com/carolina/pages/recent-repo.html]Recent Repository Additions[/url]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
hello every one:
I am facing a little bit problem in setting a screen resolution:
When ever I set a screen resolution as 1024x768, it will reset automatically
to 1280x960 when I restart my system. Means I have to set screen resolution on every boot.
Note: I m using FRUGAL Installation:
Thnx in advance.
UMAIR
I am facing a little bit problem in setting a screen resolution:
When ever I set a screen resolution as 1024x768, it will reset automatically
to 1280x960 when I restart my system. Means I have to set screen resolution on every boot.
Note: I m using FRUGAL Installation:
Thnx in advance.
UMAIR
Last edited by umair on Tue 04 Sep 2012, 08:26, edited 1 time in total.
I'm not quite sure what you are wanting here, you need to use a text editor, use geany text editor in Saluki or the inbuilt editor with xmenumaker posted here, though that does require that uft-8 for your locale is in /usr/lib/locale.sakamoto wrote:briefly explained - i want to know where i can edit menu items like
about xfce
partview
pmount
...
which are note available with a .desktop file under /usr/share/applications
There is no GUI editor for .desktop files, though I will be looking into that soon.
[b]Carolina:[/b] [url=http://smokey01.com/carolina/pages/recent-repo.html]Recent Repository Additions[/url]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
[img]https://dl.dropboxusercontent.com/s/ahfade8q4def1lq/signbot.gif[/img]
non-persistent screen resolution
Hi umair,
You can force a screen resolution that you know to already work by editing the /etc/X11/xorg.conf file. Probably a good idea to back up your savefile first before doing this.
At the bottom of the file should be a “Screen
You can force a screen resolution that you know to already work by editing the /etc/X11/xorg.conf file. Probably a good idea to back up your savefile first before doing this.
At the bottom of the file should be a “Screen
-
- Posts: 597
- Joined: Thu 13 Nov 2008, 13:45
No, makes absolutely no difference. I tried all three ports and it bugs every time.greengeek wrote:Does it make any difference which usb port you use? I have an Acer netbook which behaves differently on one of the ports. Also, what method do you use for the unmount?mini-jaguar wrote:It will not unmount this USB stick I have. Tried about 5 or 7 times, sometimes it even crashes the o.s. altogether.
On the other hand, if I use the same eeePC and boot another o.s., for example Puppeee, it works fine, so there is nothing really wrong with the stick which is malfunctioning in Saluki.
Strangely enough, I tried another USB stick in Saluki, a bigger one, I think 2 giga or something and it works. The only possible reason I can think of for the stick which isn't working is that it's only 500Mb and older and there's something missing in Saluki, because it works fine in other distros.
First attachment shows what it does if I try to unmount it.
If I press "EXIT" it shows the second screenshot. (Never mind that it's not a Saluki 23 wallpaper, it IS 23)
Pressing "KILL" goes to the command line, but sometimes reboots the whole computer altogether, even if not asked to do so. Typing "xwin" will get back in, if not shutting down, but the USB stick will still bug.
Also, one time I had the malfunctioning stick in, and stuck the stick which is working properly in Saluki in another USB slot, and Saluki didn't even recognise it's there.
Another time with the malfunctioning stick I tried shutting down, Saluki displayed "Saluki is now shutting down..." for a long time but wouldn't shut down.
Not in Saluki atm but the kill screen in such cases is not a very good idea at all . If PID nr ' 1 ' shows then it does the same when i do a
kill 1 `pidof whateverprogram`
accidentally forgetting the ' - ' dash before the ' 1 ' .
PID nr 1 is busybox init and killing that would normally result in immediate reboot .
*
Problem : If i mount a filesystem on the sdc1 like an old pup-safe.2fs file, i often get that kill-xmessage when i forget to unmount that first prior . Attached screenshot shows my implementation .
*
Problem : Programs that keep the filesystem busy like acpid or desktop-window-manager special sub-programs ( like e17 for example has a temperature module that runs a sub-program ) which prevents the umount -ar of '/' to read-only mode at the end of rc.shutdown if the wmexit,wmreboot,wmpoweroff,restartwm scripts are not adapted for that to kill that process . I can also think of unforeseen additional installed features by the user .
kill 1 `pidof whateverprogram`
accidentally forgetting the ' - ' dash before the ' 1 ' .
PID nr 1 is busybox init and killing that would normally result in immediate reboot .
*
Problem : If i mount a filesystem on the sdc1 like an old pup-safe.2fs file, i often get that kill-xmessage when i forget to unmount that first prior . Attached screenshot shows my implementation .
*
Problem : Programs that keep the filesystem busy like acpid or desktop-window-manager special sub-programs ( like e17 for example has a temperature module that runs a sub-program ) which prevents the umount -ar of '/' to read-only mode at the end of rc.shutdown if the wmexit,wmreboot,wmpoweroff,restartwm scripts are not adapted for that to kill that process . I can also think of unforeseen additional installed features by the user .
- Attachments
-
- simple_unmount_gui.jpg
- (74.14 KiB) Downloaded 829 times
Just a couple of thoughts:mini-jaguar wrote:The only possible reason I can think of for the stick which isn't working is that it's only 500Mb and older and there's something missing in Saluki, because it works fine in other distros.
1) Is the behaviour the same when you unmount by rightclicking the desktop icon for that stick, or by using pmount from the menu? (rather than doing it with the file manager open...)
2) Do you have access to a usb hub that you could put between the stick and the eeepc usb port? Maybe there is some oddity about how Saluki drives the hardware of the usb port and a separate hub might "insulate" the stick. I have seen some slow sticks confuse the booting of Saluki so maybe Saluki code is "too fast" for some hardware, or less tolerant of read/write delays at some times.
3) Just noticed that your sdc1 icon is labelled as a "usb disk" where the others are not, The usb sticks on my Saluki 23 install dont show as "usb disk" either. Maybe that stick is formatted in a different way somehow? Maybe the mbr structure is different? Was it created with something like bootflash or mbr.bin originally? I guess you could try changing the format of the mbr, although that might change the symptom and lose the opportunity of identifying what Saluki is doing differently.
Re: non-persistent screen resolution
Hello:Elroy : Thnx for reply:
I checked the xorg file as u mentioned. The Screen resolution is already set as 1024x768. Here is my the screen section:
Section "Screen"
Identifier "Screen0"
# Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
#Option "metamodes" "1280x960_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24
Modes "1024x768x16" #screen0modes
EndSubsection
EndSection
Any Idea ?????
UMAIR
The Screen resolution issue has been solved. I ran xorgwizard and selected the desired resolution manually. restarted the X, and now the screen resolution is set according to my needs (1024x768).
Thnx Elroy n Every One.
Regards
UMAIR
USB un-mount problems
mini-jaguar ... Saluki 23 correctly mounts and un-mounts an old Sandisk 128 MB and a Laxar 256 MB USB flash drive for me so i doubt that age of the flash is the problem. I have only had a flash drive fail to unmount if I have mounted a .sfs file on a drive and failed to un-mount that file before I tried to un-mount the flash drive. In addition, the flash drive that is running your OS or an active save file can not be un-mounted. KJ
-
- Posts: 597
- Joined: Thu 13 Nov 2008, 13:45
Karl, I don't understand most of your post, if it is in fact an answer to mine, but I do agree that installing programs and widgets can make a system unstable. However, the only thing I installed in mine is a single wallpaper, no programs, widgets or packages.
KJ, I am trying to unmount a USB stick which has no o.s. or save file on it. In fact, I usually plug it in after Saluki is already booted.
If I press exit, it does something completely different. It crashes to a black screen, the only thing on the screen being the cursor, which I cannot move with the touchpad.
2) Does absolutely nothing except maybe for the computer working a little slower when dealing with the USB stick. Bugs in the same manner.
3) That is because sdc1 is the only USB stick, sdb1 is an sD card.
edit: hmm, you may be on to something here, my other USB stick, which unmounts correctly, doesn't show this.
I think the one with problems was reformatted at one time. It's FAT32 I think, but the mbr may have been redone. I have read somewhere that factory USB sticks have this special anti-pirating thing in the mbr against purchased mp3s being copied. I didn't have any on the stick, but laying out a new table will have a different type of mbr. Still very weird that the same USB stick works fine on every other o.s.
KJ, I am trying to unmount a USB stick which has no o.s. or save file on it. In fact, I usually plug it in after Saluki is already booted.
1) This is interesting. If I use pmount it goes to that pink screen I posted earlier. However, if I press exit, it simply goes back to the pmount screen (instead of saying it can't unmount, like in the file manager)greengeek wrote:Just a couple of thoughts:mini-jaguar wrote:The only possible reason I can think of for the stick which isn't working is that it's only 500Mb and older and there's something missing in Saluki, because it works fine in other distros.
1) Is the behaviour the same when you unmount by rightclicking the desktop icon for that stick, or by using pmount from the menu? (rather than doing it with the file manager open...)
2) Do you have access to a usb hub that you could put between the stick and the eeepc usb port? Maybe there is some oddity about how Saluki drives the hardware of the usb port and a separate hub might "insulate" the stick. I have seen some slow sticks confuse the booting of Saluki so maybe Saluki code is "too fast" for some hardware, or less tolerant of read/write delays at some times.
3) Just noticed that your sdc1 icon is labelled as a "usb disk" where the others are not, The usb sticks on my Saluki 23 install dont show as "usb disk" either. Maybe that stick is formatted in a different way somehow? Maybe the mbr structure is different? Was it created with something like bootflash or mbr.bin originally? I guess you could try changing the format of the mbr, although that might change the symptom and lose the opportunity of identifying what Saluki is doing differently.
If I press exit, it does something completely different. It crashes to a black screen, the only thing on the screen being the cursor, which I cannot move with the touchpad.
2) Does absolutely nothing except maybe for the computer working a little slower when dealing with the USB stick. Bugs in the same manner.
3) That is because sdc1 is the only USB stick, sdb1 is an sD card.
edit: hmm, you may be on to something here, my other USB stick, which unmounts correctly, doesn't show this.
I think the one with problems was reformatted at one time. It's FAT32 I think, but the mbr may have been redone. I have read somewhere that factory USB sticks have this special anti-pirating thing in the mbr against purchased mp3s being copied. I didn't have any on the stick, but laying out a new table will have a different type of mbr. Still very weird that the same USB stick works fine on every other o.s.
I thought that this anti-pirating thing (and U3 / Startkey code) only occurred with more recent sticks but I could be wrong.mini-jaguar wrote:I think the one with problems was reformatted at one time. It's FAT32 I think, but the mbr may have been redone. I have read somewhere that factory USB sticks have this special anti-pirating thing in the mbr against purchased mp3s being copied
I believe that changing the partition table will not necessarily change the mbr structure. (I used to think that Gparted would write a new mbr during a puppy installation, but I found out when troubleshooting Saluki boot problems that programs like Gparted only write the partition table but don't change the rest of the mbr. I had been accepting the "use existing mbr" option instead of the "use mbr.bin package" option).laying out a new table will have a different type of mbr.
Yeah, I think Saluki does some slightly different things when it comes to usb handling. I'd be interested to know how that stick behaves if you installed Wary53 or RacyNOP522 on the same hardware in exactly the same way that you installed Saluki. I have seen some odd things happen when certain puppies installed on a usb bus (which the sd card interface is...) try to handle data/control functions on another usb device. I definitely found that the mbr structure affects the timing of events on the usb bus (I have no idea why....)Still very weird that the same USB stick works fine on every other o.s.
Just as a sidenote - if I have any problems with a usb stick I now use puppy 431 to reformat the stick, install puppy 431 to it, then scrap the 431 files and just use it for whatever. After months of having boot problems with sticks formatted by other versions of Puppy it just seemed that there was something "special" about the particular combination of Puppy 431's versions of gparted and extlinux (and/or universal installer). There are other ways to "prepare" the stick but using 431 is my current favourite method.
There are various ways to save the mbr or list it's contents - I think it would be interesting to save a copy of the mbr of your problematic stick in case it offered some clues as to why Saluki is struggling with it.
Almost Geoffrey These files explaines the categories layout = but i want to modify the specific icons and descriptions used for the Thunar File Manager, Thunar Bulk Rename, Pmount shortcuts as example which are shown under category Filesystem.Geoffrey wrote:Default xfce4 menu categories are here /etc/xdg/menus/xfce-applications.menusakamoto wrote:where are the default xfce4 menu categories defined? i understood that no custom categories were defined as i cannot find anything in the ./config folder
thanks
The corresponding .directory files here /usr/share/desktop-directories
cheers
So i dont want to edit the categories but those special shortcuts in the specific categories like the example above. Thanks