| Re: Re: kate not opening in dolphin kf5
Mar 17 2016 on content Root Actions Servicemenu |
Not sure what happened to my previous reply but it did not appear in this board :\
Looking a little deeper the first problem is that kdesu is not in $PATH in Mageia as it is not a user command. It is in /usr/libexec/kf5/.
I patched the script with an extra elseif to check for executable kdesu on full path and use the full path in the command, however the script just hangs after spewing out the full usage text about 'which', which of course fails in the two previous tests.
The command reported in the kdesu password dialog is:
/bin/rootactions-servicemenu.pl 'do_open_with 'kate''/home/baz/zmdiff'
Using my own servicemenu independantly works (except as described below) if it is any help. It was using rootactions-servicemenu.pl in the Exec= until it failed in kf5, so I have changed it to:
[Desktop Entry]
Type=Service
Icon=folder-red
Actions=EditAsRoot
X-KDE-Priority=TopLevel
ServiceTypes=KonqPopupMenu/Plugin,all/allfiles
MimeType=application/octet-stream;
[Desktop Action EditAsRoot]
Exec=/usr/libexec/kf5/kdesu kate %U
Icon=folder-red
Name=Edit as Root
It fails for some reason on files in /usr/bin
(e.g. rootactions-servicemenu.pl) even though they have the same permissions as other files that do open (in e.g. /etc) - the error is just "su returned with an error". Strange. |
|  | | kate not opening in dolphin kf5
Mar 15 2016 on content Root Actions Servicemenu |
rootactions-servicemenu-2.8.7
Dolphin 15.12.2
KDE Frameworks 5.20.0
Qt 5.6.0 (built against 5.6.0)
In Mageia 6 (dev) x86_64 (Linux)
Kate refuses to open after the root login dialog.
Other root actions do work.
We are trying to update our package for Plasma5 which was always fine in KDE4.
Any help will be much appreciated by Mageia users.
|
| | | Re: Bug in simulation
Jul 15 2009 on content luckyBackup |
I just noticed changelog and it shows that this was fixed in 0.31 however I am using 0.32
Quote from About:-
luckyBackup 0.32 (using Qt4) |
| |
| | | File extensions
Jul 3 2009 on content Simple Root Actions Menu |
Using SRAM to view /var/log/dmesg does not work as the "Edit as root" context menu option is missing, however if a copy is made of the file with the same owner/permissions and an extension (e.g. dmesg.log) then SRAM does display the edit option.
This seems to be a bug.
|
| | | Re: Re: Thanks! and couple of bugs
Jun 9 2009 on content luckyBackup |
Thanks for your prompt reply.
The delay in abort must have been when I had three very large mount points in the task (which I was trying to exclude). Re-testing now with just one of them included, the maximum delay is around two seconds - so not a problem.
Regarding the syncing of deletions.
If the backup has been created by a machine with LB then the special trigger file (e.g. @@LBdel) would be copied over to the backup. Any other machine using the backup to sync from (restore) would see the file and know not to delete files in the corresponding destination folder. From that point the trigger file would be on both machines and synced like any other. The trigger file need not be empty - it could contain a list of specific file patterns to exclude from deletion in that folder. I know it's not nice to add extra files to the system, but it does give great flexibility and control. I do not see why this would need a daemon or be a problem for flash etc.
Just food for thought. :-)
Barry |
| | | Thanks! and couple of bugs
Jun 9 2009 on content luckyBackup |
Hi Luckyb - thanks for a really good program - I just installed it in Mandriva Linux 2009.1 and ran my first backup with it a few minutes ago.
Just a couple of snags I found.
1. The Abort NOW button does not abort immediately - it eventually does after clicking many times over maybe 10 seconds. (This was in simulation mode)
2. The file system browser in "Task Properties->Exclude Tab->User Defined->Browse locally" can not be used to select a directory and have it entered in the text box automatically. It has to be typed in. Also there is no warning that the full path will not work here - it took a few test runs to find that only the directory name is needed.
I look forward to seeing how you implement deleted file synchronisation, as having deleted files keep returning can be a real problem when sync'ing two machines.
A program (grbakpro) that I used in Windows worked well in this respect. By placing a specially named file in a folder, deletions in that folder were not sync'ed, otherwise all deletions were echoed on the other machine.
Just a thought.
Cheers, Barry |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
