not a support question
mojo
offlineKey Master
gtkonly flavor has a different /etc/lxpanel/slitaz/config than core
http://hg.slitaz.org/flavors/file/8d41f6ff686f/gtkonly/rootfs/etc/lxpanel/slitaz/config
I edited both (/etc,/home/tux/.config) to Terminal=xterm logged out/in to tux but still not working.
Aleksej
offlineCoder-hobbyist
mojo,
Thank you for note about different config.
I'll try tomorrow to run lxpanel in terminal, maybe here will be some errors/tips. Or will use strace.
Now I'm go to sleep (4 a.m. here). See ya. Zzz
Aleksej
offlineCoder-hobbyist
christophe,
I'm not sure what are you asking.
Bug report is a message from user to developer (or maybe, dialog). Here the dialog between two developers.
Or, maybe you want us to pay attention to bugs.slitaz.org? I take a quick look there and not found rolling bugs. Execuse in advance for misunderstanding.
I'll back here in few hours, now I should to go to bank and pay for services/credits...
christophe
offlineMember
Since you are talking about problems appearing in rolling here, I am asking whether rolling is in a state where its problems should be reported here (in this forum) (and will be taken care of), or not.
If yes, I could mention what I found when playing with it, otherwise, or if it is in a too early stage still for that, then it is not necessary or usefull for me (or others) to do so, and waste my and others time (including yours). Nothing more ;)
Aleksej
offlineCoder-hobbyist
christophe,
You can post your problems here, in the forum, as usually. I think this topic is not for global Rolling problems, so better open new topic or pick sticky topic on the top of forum.
mojo,
How fair is your play?
You broke alsamixer,vi,and dialog desktop shortcuts on cooking with your commit:
You made 2 changes either one alone stops vi alsamixer and dialog shortcuts from working.
. . .
+Exec=vi <===Error
+Terminal=true <===Error. . .
+Exec=alsamixer <=====Error
+Terminal=true <=====Error
Aleksej your right,with rolling-core-4in1.iso,core flavor selection vi opens with sakura after editing vi.desktop
Vi doesn't work after editing when booted in gtkonly selection.
So, seems like I broke vi, alsamixer and dialog example for gtkonly flavor.
While all this not broken and worked well on core flavor?
I understand you correctly?
alsamixer doesn't launch,test every menu shortcut.
But, mojo, what is about alsamixer? It not worked? Hmm... Gtkonly flavor have no alsamixer. What you want to tell me? You tried alsamixer on gtkonly or on core? And on core all works? I have a pattern gap. I can't understand.
____________________
I don't want a war, but it worked again for me in gtkonly flawor. What am I doing wrong?
Still using Rolling ISO (from July, 8). Open it in ISOmaster, extract boot/isolinux/isolinux.cfg from ISO and open it in the text editor:
LABEL gtkonly
MENU LABEL SliTaz gtkonly Live
COM32 c32box.c32
append linux /boot/bzImage initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz rw root=/dev/null autologinExtract /boot/rootfs4.gz, /boot/rootfs3.gz, /boot/rootfs2.gz using ISOmaster.
Glue them together (open terminal emulator in folder with extracted files):
cat rootfs4.gz rootfs3.gz rootfs2.gz > gtkonly.gzNow I have kernel (previously extracted bzImage) and rootfs (gtkonly.gz).
Configure Grub4dos menu entry:
title SliTaz Rolling 13-07-08 (gtkonly)
rootnoverify (hd0,1)
kernel (hd0,1)/boot/rolling130708/bzImage rw root=/dev/null lang=ru_RU kmap=ru autologin
initrd (hd0,1)/boot/rolling130708/gtkonly.gzBooting...
OMG! I like this small gtkonly flavor! With Rolling core flavor I've got 800×600 resolution on my 1024×600 display, but here I've saw native resolution. How I like it! ;)
Let's press all the menu items? Ok.
Many of them not working at all! Hmm... But vi works. Open /usr/share/applications/vi.desktop and sure its content:
. . .
Exec=vi
Terminal=true
. . .And it works. Vi opens in the xterm. But, can I configure this behavior? Unfortunately, SpaceFM is too complicated for me and I can't open hard disk partition with the sakura tazpkg. And I don't want to make ppp0 connection work in the gtkonly today ;) Better I write simple fake application:
/usr/bin/faketerm:
#!/bin/sh
echo "Running faketerm..."
echo "Options are: $@"
echo "==================="Make it executable. Test it:
faketerm SliTaz loves You!
Running faketerm...
Options are: SliTaz loves You!
===================Edit /home/tux/.config/lxpanel/slitaz/config and change
Terminal=terminal
to
Teminal=faketerm
Press Vi in the Applications menu. It still opens in the xterm. So we need to lxpanel restart every time we change its settings.
Where we'll see faketerm messages? Close and reopen LXPanel in the terminal:
killall lxpanel
lxpanel -p slitazPress Vi in the menu again, and we'll see message from faketerm:
Running faketerm...
Options are: -e vi
===================Let's back to Terminal=terminal in the config and restart using lxpanelctl restart. Now Vi opens in the xterm. So, we can configure LXPanel behavior, and desktop files with "Terminal=true" are not broken, and they worked in the "core" flavor as they worked in the "gtkonly" flavor. What to fix when it works?
I want to tell you about not working menu items, but It is beyond the scope of the topic.
Aleksej
offlineCoder-hobbyist
mojo,
Are you here? I'm still here waiting for your answers.
If you don't like to read long post, I repeat questions here, in compressed form:
I do not like when I was accused of being vain, what's not my fault.
I did not break the system by my commits.
mojo
offlineKey Master
Aleksej,
I am wrong.
Your commits didn't break anything.
Please accept my apology.
mojo
Aleksej
offlineCoder-hobbyist
mojo,
I accepted your apologies. With pleasure.
But still a question, why it not worked?
And still a question, how good this standard is supported "beyond lxpanel": like in jwm and e17...
I know that ADeskBar have not full standard support, it not show my menu sub-categories. But I not dig deeper, ADeskBar is very raw as for me.
You must log in to post.
