Tiny Core Base > Release Candidate Testing
tinycore_v2.11rc2
jur:
To make upgrading from previous versions smoother, may I suggest /.X.d also be included in xsetup if it does not exist?
meanpt:
Hi,
1. installed applications are not shown under the Applications heading menu
2. midori did not installed correctly, despite the icon being shown in the dock
3. shiretoko installed on the third attempt
4. Vboxadditions is not working - when trying file sharing with the Windows system with the shared vbox folder with "mount .-t vboxsf -rw windowsSystemFileFolder TCDirectory, keeps responding "No such device". Currently using VBox 3.1.4
Regards,
Mean
roberts:
--- Quote from: meanpt on April 24, 2010, 08:37:46 PM ---
Hi,
1. installed applications are not shown under the Applications heading menu
2. midori did not installed correctly, despite the icon being shown in the dock
3. shiretoko installed on the third attempt
4. Vboxadditions is not working - when trying file sharing with the Windows system with the shared vbox folder with "mount .-t vboxsf -rw windowsSystemFileFolder TCDirectory, keeps responding "No such device". Currently using VBox 3.1.4
Regards,
Mean
--- End quote ---
What does showbootcodes display?
maro:
As I was surprised to read
--- Quote ---4. Vboxadditions is not working
--- End quote ---
I did a re-test with TC 2.11rc2 along the lines of what I did here and have to report that all mounting attempts appeared to have worked without an issue for me. Could it be that the required module was not loaded (with sudo modprobe vboxvfs) as mentioned in the .info file?
I'm also not quite sure what is supposed to be wrong with 'midori': The installation works fine for me and the application is usable. The only (in my view entirely cosmetic) issue might be the fact that at the very first start a bit a garbled message might appear ("Error - %u The page '%u' couldn't be loaded. URL cannot be shown"). It appears that this happens when midori gets started via the wbar icon, and does not happen when started from the command line. A quick look into '/usr/local/tce.wbar' shows that indeed 'c: exec midori %u' appears to be the "culprit" here. I guess that OTOH might be a consequence of the 'Exec=midori %u' entry in '/usr/local/share/applications/midori.desktop'.
Likewise 'shiretoko' worked OK for my test. It's "just" fairly memory-hungry (ca. 23M downloaded extensions lead to ca. 50M extracted extensions). So running it on a system with only 128M would be pretty much pointless. But I fail to see what could be the issue re. TC 2.11rc2.
What I can confirm is the reported issue about applications not "showing up" via '~/.wmx/Applications'
I believe I've spotted one yet un-reported issue: the ownership of the files in '/home/tc/.wmx/SystemTools' is 'root:staff' even though a command in '/usr/bin/flwm_topside_initmenu' (i.e. chown tc.staff -R /home/"$USER"/.wmx) tries to change this. I guess that command might have to be moved after the loop over the files in '/usr/share/applications/tinycore-*' to have the desired effect.
roberts:
--- Quote ---I believe I've spotted one yet un-reported issue: the ownership of the files in '/home/tc/.wmx/SystemTools' is 'root:staff' even though a command in '/usr/bin/flwm_topside_initmenu' (i.e. chown tc.staff -R /home/"$USER"/.wmx) tries to change this. I guess that command might have to be moved after the loop over the files in '/usr/share/applications/tinycore-*' to have the desired effect.
--- End quote ---
I am curious how you are getting root.staff on System Tools.
Using base norestore the permissions are OK. In fact I now recommend, as posted in the announcement, that .xfiletool.lst contain home/tc/.wmx therefore my .wmx is recreated upon each boot. I cannot reproduce the permission issue. System Tools should have no effect on Applications. I have tested with typically home in ram (base norestore) and with persistent home on ext2 filesystem.
Have you changed .xfiletool.lst to include home/tc/.wmx ?
What happens if you exit X and
rm -rf .wmx and then startx
Check permissions.
What filesystem is hosting /home ?
For user, meanpt, I again ask to see the output of showbootcodes, as I would like to know what window manager you are using and what persistent options if any.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version