Porteus-v1_beta-i486 ready for testing

[Hamza]

This is the autoexec commands.

[Blaze]

Hamza, and? plz try it.

[wread]

@Hamza

I have an issue with my graphics card : Intel 82845G/GL/GE/PE/GV Graphics Controller

When , I starting KDE Trinity , the X.Org crash , and I cannot see any window decoration and the mouse is freezed.After some seconds , I have a black screen.

What filesystem are you using? I had several crashes with xfs, then changed to ext3 and have no more crashes!
I think the new kernel doesn't like xfs...

Posted after 11 minutes 55 seconds:
For those interested in printing with HP printers, this link contains 13 xzm files for Porteus V1.0-beta. Download them to modules and reboot. The "KMenu>System>Manage Printing" desktop file must be corrected by adding "admin" to the call.



http://www.mediafire.com/?f1vrqwkcbxavb

Enjoy! (THE PORTEUS COMMUNITY NEVER SLEEPS!)

[Ahau]

I know, I know...it's getting old. Ahau found more things that extpkg is missing...

empty directories. for example, the package dbus has a bunch of empty directories, and if they aren't there, things fail because they don't have directories they are expecting.

**back to my corner**

Posted after 2 days 17 hours 12 minutes 39 seconds:

"After checking, no it doesn't copy symlinks"
this is a weird think about slackware's 'pkgtools' as symlinks are removed during 'makepkg' stage and restored when you do 'installpkg'.
Info about them is kept in /var/log/scripts/* files. i used to delete them with my 'cleanup' script but can keep them for 'extpkg' purpose.
maybe extpkg could check /var/log/scripts/* and get required info about symlinks from there?

OTOH - activate script runs 'ldconfig' at each insertion now so broken/missing symlinks are not a problem anymore. still - more elegant way would be to have them included in the module.

For what it's worth, I recently discovered a good reason to incorporate symlink copying in extpkg, rather than relying on ldconfig. If the extracted packages are used for any activity going on while the system is starting up (e.g. libfontconfig, some of the gtk stuff, and others), you can wind up with major errors. I wound up with an "always fresh" system that sometimes started with gtk errors (no fbpanel) and sometimes gtk and font errors -- other times, the same system would start up without an issue--as if sometimes ldconfig didn't get the symlinks placed before they were called by other processes. Simple solution, really -- I copied the contents out of /mnt/live/memory/changes/lib and ../usr/lib and made a symlinks module...but it did take me a while to figure out what the hell was going on!

[fanthom]

you are right. i have used '&' which sends ldconfig process to the background to not slow down the boot time too much. i assume that 95% of symlinks are in place while booting Porteus.
extpkg must support symlinks recreation.

[wread]

@brokenman
When you strart Games>Card Games>Patience Card Game, you get an error message "couldn't find wallpaper". To correct that you must add the default wallpaper file No-Ones-Laughing-3.jpg in folder /usr/share/wallpapers.

I copied the file from slax 6.1.2 and added to 004-kde.xzm by the normal procedure. Solved

Cheers!

[Hamza]

Or , you can define the default wallpaper in /root/.kde/share/config/****

Thanks for suggestions.

[Burninbush]

Clock/time setting issue ... HOPE THIS IS THE RIGHT PLACE, HAMZA.

This is a major annoyance that seems to be in all recent Porteus distros:

-- I boot my computer, stopping in cmos setup to fix the time; I want it to show local time, currently PDT, which I think is GMT -7. I live in Pacific time zone, currently home to ~56 million people.

-- bring up any Porteus, and let's pretend it's the first time I've booted, so I right-click on the kde time display and choose Adjust Date & Time. Run down the list of zones to Los Angeles (Pacific) and click on that, then Apply on the form.

-- what now shows near the bottom of the kde clock display is "Current Local Timezone: America/Los Angeles (UTC)" but the time in the clock display in the system tray is off by 7 hours, presumably UTC.

-- if I change the clock to fix the tray time display, then on exit or reboot Porteus rewrites the cmos time, so the next time I boot something it's off again!

-- at this moment, just booted up v09-32, the analog clock in the adjust display is showing the cmos time -- 12:00:35 (pm), but the digital display in the system tray sez it's 5 am -- offset by 7 hours. It's hard for me to imagine the situation where someone would want their clock to display like this. Am I making myself clear? The time in the tray is offset from the time on the screen where you set it.

How can I get a divorce from this UTC offset? I don't have this problem with any other distro, and for what it's worth, they also report differently: "Timezone: America/Los Angeles (PDT)" with no reference to (UTC). There must be some place in kde setup to change that, but I can't find it.

[Hamza]

Normally , the localtime of Porteus is set with hardware clock.

[Ahau]

I'll take a look at this tonight. I'm in PDT too. Porteus auto-detects my time from my hardware, and shows the correct time in KDE. What I haven't been checking is my location, according to Porteus. It sounds like maybe it's assuming your cmos time is correct, but your location is UTC, wherever you happen to be. When you change your location, it assumes the clock needs to change too, even though it doesn't.

Posted after 3 hours 45 minutes 6 seconds:
in 64 bit, I just get an error if I try to change my location to something other than UTC.

Here's the section from /etc/rc.S that sets the clock:

Code: Select all

# Set the system time from the hardware clock using hwclock --hctosys.
# Check for a broken motherboard RTC clock (where ioports for rtc are
# unknown) to prevent hwclock causing a hang:
if ! grep -q -w rtc /proc/ioports; then
  CLOCK_OPT="--directisa"
fi
if grep -wq "^UTC" /etc/hardwareclock; then
   echo "Setting system time from the hardware clock (UTC)."
   /sbin/hwclock $CLOCK_OPT --utc --hctosys &
else
   echo "Setting system time from the hardware clock (localtime)."
   /sbin/hwclock $CLOCK_OPT --localtime --hctosys &
fi

Posted after 10 minutes 16 seconds:
in 32 bit, I see what you mean. my clock shows the current time, and when I set my timezone to Pacific, it goes back by 7 hours. I switched to LXDE to see what's going on there, and the clock configuration has no settings for timezones, and after logging out of KDE and into LXDE, the clock shows the correct current time...so it does seem like a KDE issue.

EDIT: I went back into KDE, went to adjust date and time, and manually moved the clock forward and back by seven hours. At first, it had an offset, but after I played with it a few more times, it synced up with the clock in the panel, and I was able to set it so that my timezone was pacific, and the correct time is displayed. Pretty odd behaviour.

[francois]

@burningbush: Maybe you can try this one from:
http://www.slax.org/forum.php?action=vi ... ostid65067

In the KDE panel, the time indicated by the clock does not change though I have set it according to the adequate time zone and though I have modified the clock time thru the adjust date and time clock device. Here is what I did, from:
http://lists.kde.org/?l=kde-linux&m=113579888606118&w=2

All I had to do was to use the command dcopserver in cli mode and reboot to resolve the issue permanently.

root@slax:~# dcopserver

[ponce]

I prepared some new lxde packages on slackware 13.37

http://ponce.cc/slackware/slackware-13.37/lxde/

substitute the pcmanfm package with this one for not having the warning during use as root
pcmanfm-20110422_3f899d1-i486-1ponce.txz

be aware that the following packages shouldn't be needed anymore (gvfs, that should have no dependencies, is used instead of gnome-vfs)

Code: Select all

gnome-mime-data
ORBit2
GConf
libbonobo
gnome-vfs

also, configuration files in /etc are changed, so I suggest to start from the new ones and customize them accordingly (or something may break ).

[francois]

1) @burningbush and others:
If the dcopserver command works for you. I would appreciate to get some explanation. It would be appreciated.

Thanks.

Posted after 5 hours 13 minutes 24 seconds:
2) Is there a way in addition to autoexec=toroot cheatcode, to boot all the way winthin X without giving the password?

[fanthom]

@francois
it's 'toroot' and not 'autoexec=toroot' - please read cheatcodes.txt

[francois]

Thanks, I will do it.

Posted after 1 hour 41 minute 59 seconds:
1) Has the /root /.kde/autostart folder been removed temporarily, or has it been moved somewhere else^ I used to drop scripts in there (including my dual display script).

2) toroot does not seem to function in menu.lst always fresh

Salutations distinguees.