topic title: [antiX M12] several little bugs
Posts: 96
melodie
Joined: 15 Feb 2008
#16
anticapitalista wrote:Good catch there melodie!

You know, I must have commented out icewmtray for a reason, but for the life of me cannot remember why.

I'll add this to the bug fix.

thanks
I am very happy that you appreciate and I am most happy too that I could find someone to bring me to the solution. __{{emoticon}}__

One more for the road __{{emoticon}}__
→
I have found why in the"menu Applications > Preferences" the entry menus"Gparted" and"Synaptic Package Manager" were repeated twice. The reason is that the gparted.desktop file and the synaptic.desktop files are once in the directory /usr/share/applicatiions and once more in the directory /usr/share/applications/antix

I have moved the ones which are in /usr/share/applications respectively to"gparted.desktop-backup" and"synaptic.desktop-backup" and left alone the ones in the sub-directory antix, and now they appear once only instead of twice.

While I am here, I would like to suggest to rather put the synaptic.desktop file in a category related to system rather than preferences.

Thank you for all.
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#17
icewm-session starts icewmtray automatically.
So this is some workaround you found but the problem must be elsewhere.
Posts: 96
melodie
Joined: 15 Feb 2008
#18
secipolla wrote:icewm-session starts icewmtray automatically.
So this is some workaround you found but the problem must be elsewhere.
If you are right it might mean that icewm-session does not do it's work well because the icewmtray was not started (which triggered the"ghost window"). What is icewm-session ? Is it a script ? Do you have a few minutes to look at it ?
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#19
If icewm-session is started in .xinitrc you can be sure that icewmtray is running (it runs icewm, icewmbg and icewmtray) and you can check that.

So for some reason volumeicon was starting before icewmtray for you. But I don't use antiX and that's all I can say.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#20
Bad bug #2 : Midori crashes with message"illegal instruction", as well in a session using the antiX i486 kernel as one using the liquorix i686 kernel // SOLVED by uninstalling flashplugin-nonfree, not compiled with the set of instructions fit for that CPU
I had problems with latest flash 11.2 on my p3 boxes. Flash has gotten bloated needing Pentium 4 or Atom processors to work. Using a static install of a older libflashplayer.so from Adobe fixed that for me. You might have to go with a flash version 10 instead of 11.1 though as your mileage may vary from mine.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/viewtopic.php?f=4&t=3300"
linktext was:"antix.freeforu ms.org/viewtopic.php?f=4&t=3300"
====================================


I mention this problem in my last post in that thread.

Edit: Also. Back when I ran AntiX 7.5 on some Pentium 2 boxes with 128MB of ram. I used to use


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://sourceforge.jp/projects/kazehakase/releases/?release_id=2211"
linktext was:"http://sourceforge.jp/projects/kazehaka ... se_id=2211"
====================================


instead of Midori. It worked OK for me in flash back then also. Flash was a older version then though. Kazehakase should show up in

Code: Select all

apt-cache show kazehakase
in terminal in AntiX. Just mentioning this for grins. __{{emoticon}}__
Posts: 96
melodie
Joined: 15 Feb 2008
#21
Hi,

Midori crashed today, for other reasons. I'll try to take time to explore and bring messages from gdb back here tomorrow. In the meanwhile I failed to install a printer which is on the network and succeeded installing another one on USB.

Else, I added 2 bugs solved in the list, in the first post.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#22
melodie wrote:... the screen flickers several times before staying still.
When using antiX-12-Base, I also experienced similar screen flickering which settled after 1-2 seconds. My fix was to amend the boot codes to

Code: Select all

ro noxorg vga=788
Posts: 96
melodie
Joined: 15 Feb 2008
#23
secipolla wrote:If icewm-session is started in .xinitrc you can be sure that icewmtray is running (it runs icewm, icewmbg and icewmtray) and you can check that.

So for some reason volumeicon was starting before icewmtray for you. But I don't use antiX and that's all I can say.
Here is the file ~/.xinitrc:

Code: Select all

$ cat .xinitrc
#----------------------------------------------------------------------
# .xinitrc file
#
# AUTO-GENERATED by antiX-init.sh on Wed Aug  8 08:34:59 EDT 2012
#
# This file was auto-generated.  If you want to customize it you MUST
# DELETE the line above or your changes will be lost on the next boot.
#
# Alternatively, simply put your changes in .xinitrc-custom.
#----------------------------------------------------------------------

[ -x ~/.xinitrc-custom ] && ~/.xinitrc-custom

[ -f ~/.Xmodmap ] && xmodmap ~/.Xmodmap

case"$1" in
    Rox-icewm|rox-icewm)
        export DESKTOP_CODE="rox-icewm"
        echo"rox-icewm" > $HOME/.wallpaper/session
        rox --pinboard=antiX-ice
        exec icewm-session
        ;;
    icewm)
        export DESKTOP_CODE="icewm"
        echo"icewm" > $HOME/.wallpaper/session
        sed -i -e"s/rox --pinboard=antiX-ice &/#rox --pinboard=antiX-ice &/" $HOME/.icewm/startup
        exec icewm-session
        ;;
    Rox-fluxbox|rox-fluxbox)
        export DESKTOP_CODE="rox-fluxbox"
        echo"rox-fluxbox" > $HOME/.wallpaper/session
        rox --pinboard=antiX-fb
        exec startfluxbox
        ;;
    fluxbox)
        export DESKTOP_CODE="fluxbox"
        echo"fluxbox" > $HOME/.wallpaper/session
        sed -i -e"s/rox --pinboard=antiX-fb &/#rox --pinboard=antiX-fb &/" $HOME/.fluxbox/startup
        exec startfluxbox
        ;;
    dwm)
        export DESKTOP_CODE="dwm"
        exec dwm
        ;;
    Rox-jwm|rox-jwm)
        export DESKTOP_CODE="rox-jwm"
        echo"rox-jwm" > $HOME/.wallpaper/session
        rox --pinboard=antiX-jwm
        exec jwm
        ;;
    jwm)
        export DESKTOP_CODE="jwm"
        echo"jwm" > $HOME/.wallpaper/session
        sed -i -e"s/rox --pinboard=antiX-jwm &/#rox --pinboard=antiX-jwm &/" $HOME/.jwm/startup
        exec jwm
        ;;
    wmii)
        export DESKTOP_CODE="wmii"
        exec wmii
        ;;

    # Default: rox-icewm
    *)
        export DESKTOP_CODE="rox-icewm"
        echo"rox-icewm" > $HOME/.wallpaper/session
        rox --pinboard=antiX-ice
        exec icewm-session
        ;;
esac
$
In the icewm section I don't know what the line starting with sed does. I have seen the line containing the chain"--pinboard" in the startup script. All I can say is now the problem is solved, even if it can be considered as a turn around.
Posts: 96
melodie
Joined: 15 Feb 2008
#24
dark-D wrote: bug 6: edit your keys setting from control center for icewm or fluxbox depending on what you are using.
Hi,

I use IceWM and I edit my key settings, but I don't see anything likely to be related to this menu triggered by F10. I don't see F10 at all in the file"key":
##Sample icewm keys for antiX.

key"Alt+Ctrl+r" sudo rox
key"Alt+Ctrl+u" rox
key"Alt+Ctrl+m" rxvt-unicode -tr -sh 65 -fg white -T 'Htop' -e htop
key"Alt+Ctrl+t" rxvt-unicode -tr -sh 65 -fg white -T 'antiX'
key"Alt+Ctrl+b" iceape
key"Alt+Ctrl+i" inxi-gui
key"Alt+Ctrl+p" pcmanfm
key"Alt+Ctrl+s" antixscreenshot.sh
key"Alt+Ctrl+c" antixcc.sh
key"Alt+Ctrl+o" conkytoggleice.sh
key"Alt+Ctrl+k" xkill
key"Alt+F2" gexec

key"Alt+Ctrl+KP_Divide" amixer -c 0 set Master 5-# lower volume
key"Alt+Ctrl+KP_Multiply" amixer -c 0 set Master 5+ # raise volume
key"Alt+Ctrl+KP_Add" amixer sset Master toggle # mute on/off

#dmenu
key"Alt+Ctrl+l" slock
The answer must be somewhere else.

Any other idea ?