X-Slacko-4.4 with Xfce

[Sage]

2.2.1 n : boosted the mem. to 2G on XP2400+. Pacman screensaver interception after boot during setup up even more intrusive.

[rg66]

Marv, Iooks like I used some files from slacko-5.9.3 but original rc.shutdown doesn't seem to work either and slacko-2.2 used the one from pupsaveconfig. I've got gyro's patched rc.shutdown working with never=0 and ask at shutdown=+0

2.2.1 was just for testing save to folder anyway.

[rg66]

Starhawk, it might be better to ask in the slacko thread about the volume keys as I've found nothing to help.

[rg66]

Sage, not sure what to say. I can't reproduce this on my XP-2400 box and no one else has said they've had this issue.

[rg66]

@ Marv

Just tried the slacko 5.7.0 files (patched by gyro for save to folder) and although it doesn't ask to save at shutdown it saves even though it's set to never save.

To get it to work properly as is, you need to add /etc/eventmanager and /usr/sbin/eventmanager from slacko-5.9.3

I'm going to pull the 2.2.1 delta's but the question is, mod the original files or use the ones from 5.9.3 and maybe run into other issues?

[Marv]

@ Marv

Just tried the slacko 5.7.0 files (patched by gyro for save to folder) and although it doesn't ask to save at shutdown it saves even though it's set to never save.

To get it to work properly as is, you need to add /etc/eventmanager and /usr/sbin/eventmanager from slacko-5.9.3

I'm going to pull the 2.2.1 delta's but the question is, mod the original files or use the ones from 5.9.3 and maybe run into other issues?

mavrothal pointed me at those eventmanagers. I may swap them in and have a go but frankly the extra tick box seems just a complication to me. Patch I'm using at line 99 in rc.shutdown is now 1 line:

Code: Select all

[ "$RAMSAVEINTERVAL" -eq "0" ] && ASKTOSAVE="true" || ASKTOSAVE="false"

My next headbanging is tweaking Carolina xorg and intel KMS video with the 3.14.20 kernel on the Bay-Trail boxes. Pure OCD as X-slacko and LxPupTahr are perfectly happy there.

[rg66]

I've decided to go with the originals to avoid further issues. I've got -0=Never, 0=At shutdown +0=Ask at shutdown working. Files are below, remove fake .gz

[rg66]

Apparently never doesn't mean never in puppy land, it means save at shutdown. I've re-uploaded eventmanager and rc.shutdown with: -0=Never, 0=At shutdown +0=Ask at shutdown. see above post.

[starhawk]

Starhawk, it might be better to ask in the slacko thread about the volume keys as I've found nothing to help.

Just saw this -- sorry -- I'll just live with them not working. I don't really need them, it would just be kinda nifty. Bonus material, you know?

[rg66]

Fix to rc.shutdown for not saving with any value other than *0. See 3 posts above.

[Sage]

2.2.1 PAE: Pacman also showed up after setup and before xwin restartX, until mouse moves or k/b pressed. At first ask, xwin crashed after setup. Second hard reset came up OK but mouse froze requiring a USB override. Seems OK subsequently.
If you want to see the Pacman feature probably would need to reduce mem. and slow cpu? But it's reproducibly present.

[rg66]

2.2.1 PAE: Pacman also showed up after setup and before xwin restartX, until mouse moves or k/b pressed. At first ask, xwin crashed after setup. Second hard reset came up OK but mouse froze requiring a USB override. Seems OK subsequently.
If you want to see the Pacman feature probably would need to reduce mem. and slow cpu? But it's reproducibly present.

Again, doesn't do it on my XP2400 or any of my others. Does this happen only on your AMD XP box or on other comps as well?

[Jasper]

Sage,

Do you still juggle dozens of distros and rather more machines simultaneously daily?

[Sage]

Does this happen only on your AMD XP box or on other comps as well?

Will put up something older on the bench tomorrow. Did we establish minimum memory for this one? How about minimum cpu? Might also slow the XP2400+ down to 133FSB to see if Pacman sticks around a bit longer.

[rg66]

Will put up something older on the bench tomorrow. Did we establish minimum memory for this one? How about minimum cpu? Might also slow the XP2400+ down to 133FSB to see if Pacman sticks around a bit longer.

Should be about the same requirements as slacko plus a bit more for xfce. I'm posting this from the Athlon comp, XP2500 - 1GB RAM, and no screensaver issues. It's definitely usable but would not like to use it on a slower machine. At idle 10% CPU and 90MB RAM, CPU can jump up to 60% using firefox.

Not sure why it's happening so often. Are you running without a save file and doing setup every time you boot?

[starhawk]

One more annoyance. I tend to navigate with a keyboard, and whenever I press Backspace within Thunar it beeps at me. I could ignore that on a desktop, but on my new laptop it pipes that to the speakers.

Is there an easy way to tell Thunar to "shut the #@@!$@#!! up!" /without/ unloading/blacklisting the driver module for that sound?

[rg66]

One more annoyance. I tend to navigate with a keyboard, and whenever I press Backspace within Thunar it beeps at me. I could ignore that on a desktop, but on my new laptop it pipes that to the speakers.

Is there an easy way to tell Thunar to "shut the #@@!$@#!! up!" /without/ unloading/blacklisting the driver module for that sound?

"xset -b" from command line, but it will turn off the beep for everything. "xset b" to turn it back on.

[starhawk]

That's the thing, I don't want to turn it off for /everything/ -- just Thunar.

[Geoffrey]

One more annoyance. I tend to navigate with a keyboard, and whenever I press Backspace within Thunar it beeps at me. I could ignore that on a desktop, but on my new laptop it pipes that to the speakers.

Is there an easy way to tell Thunar to "shut the #@@!$@#!! up!" /without/ unloading/blacklisting the driver module for that sound?

Look in the mixer, select the beep and mute it, that works for me in carolina, should be the same.

[starhawk]

Tried that. That's the weird thing -- X-Slacko thinks it /is/ muted. It gets louder when I "unmute" it!