Porteus-v1.0-beta-x86_64 is ready :)

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
Burninbush
Power user
Power user
Posts: 49
Joined: 29 Dec 2010, 01:46
Location: Near SF, CA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#31 by Burninbush » 13 Mar 2011, 18:03

rava, do not run startx to get LXDE running. startx is configured to run KDE. >ahau

+++++++++++++++++

Ahhh ... but isn't xwmconfig still there and working?

It isn't necessary to go all the way back to a reboot to run a different gui. Startx starts X with whatever gui you have told it to run in xwmconfig.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#32 by Ahau » 13 Mar 2011, 21:11

yes, bb, you are right. What I meant to say is that the default configuration for startx in porteus is to start KDE, and it will do so unless configured otherwise. I haven't tried in a while, but I believe it will start LXDE if KDE has been removed from the system.

Thus, if you have KDE and LXDE both installed, and run startx from the append line (without configuring it to run LXDE first), and you also have 'lxde' in the append line, porteus will have commands to start both desktop environments. (KDE through startx and LXDE via lxdm through /etc/rc.d/rc.4). I believe that is what is happening in Rava's setup, but we'll need more information from Rava to determine that for sure.

btw Rava-- I was able to get the nVidia driver to run instead of nouveau in v1 beta, by either adding the 'nomodeset' cheatcode per fanthom's instructions, or by blacklisting nouveau in /etc/modeprobe.d/blacklist.conf.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#33 by fanthom » 13 Mar 2011, 21:50

@all
you have 3 ways of starting GUI in Porteus:
1) through 'startx' command
2) through display managers (kdm, lxdm)
3) through runlevels (4 in our case).

First case base on /etc/X11/xinit/xinitrc symlink. when this file is linked with xinitrc.kde then kde is started, when is linked with xinitrc.lxde then lxde. you can change symlinks by using 'xwmconfig' utility or just do it manually - same effect.
003-lxde has this symlink set to xinitrc.lxde so when no KDE is present - this desktop is started. if 004-kde is there, then xinitrc form 003 is overrided with xinitrc from 004 (which obviously point to xinitrc.kde) and KDE is started by default.

why i dont like 'startx' way of initializing X11 environment?
- you need to be logged in to issue this command
- kde is short of 'reboot, shutdown, hibarnate, etc..' functions - only 'logout' is present
- when GUI is started by guest then there is no way to reboot or shutdown without 'su'

Second case is better than 'startx' as:
- you have configuration (/etc/lxdm/lxdm.conf and /usr/share/config/kdm/kdmrc) files where you can set plenty of things like who: should be logged in by default, what to do with numlock, etc.
- when logged in as guest, you still have possibility to do a reboot, shutdown, hibernate, etc....

Third case is the best as it gives you flexibility how to start GUI (startx or display managers) but also starts/stops all scripts while switching between runlevels (S* and K* scripts in /etc/rc.d/rc3.d and /etc/rc.d/rc4.d). Just have a look on /etc/rc.d/rc.4 for more info.

Porteus uses runlevel 4 by default to start GUI (telinit~4) and kdm/lxdm to manage X11 session.

Trust me - it's the best way :wink:

Cheers
Please add [Solved] to your thread title if the solution was found.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#34 by Rava » 14 Mar 2011, 14:47

@fanthom
I get it now. I wrote a script that changed the /etc/X11/xinit/xinitrc symlink either to start KDE or LXDE.

I think I will just put the wanted symlink in my 100-local. module then, just like with remix. :D

Verfasst after 2 minutes 34 seconds:
Ahau,
I want telinit~3 for a reason, since I need to log in into console at the beginning prior starting X so that some kind of backed up data is copied into the union (but I could stop that when some reason exist to not want that)
I use the "Always Fresh" mode but back up some program by myself, and with the above technique it gets resored (like I said, unless I don't want it restored)
It also keeps the most resent "store" and also 3 backups of that data that I could restore instead of the recent one that is done by just pressing enter or waiting 4 seconds...

I tweaked startx with Remix V08, and I just can do the same now, like putting a symlink to startlxde or what's it called (I again run remix right now since at the beginning there is more to integrate when having a new system since I run it with "always fresh"...)

I am just weird like that, but I prefer it and to me it is a more secure system that way... *shrug*


///EDIT

The forum is acting weird right now.
I wanted to answer to a post by Ahau that I got reminded of by email with the URL of viewtopic.php?f=53&t=348&p=2020#p2020 and the text of
rava, do not run startx to get LXDE running. startx is configured to run KDE. remove startx from your APPEND line in porteus.conf. /etc/rc.d/rc.4 searches for lxde in the APPEND line and runs lxdm instead of kdm if 'lxde' is present. should be 'autoexec=lxde;xconf;telinit~4'.
But for some reason phpBB messes up this thread... and instead the post by Ahau disappears (unless I use the above link) and instead my new post got added to my old reply...
:no: Just letting you know, maybe it is the result of yet another hacking attempt?
Last edited by Rava on 01 Apr 2011, 22:34, edited 1 time in total.
Cheers!
Yours Rava

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#35 by Ahau » 14 Mar 2011, 14:53

Sorry rava -- that was my fault. I didn't see that you were trying to boot into telinit 3. Sorry for the confusion!
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#36 by Rava » 14 Mar 2011, 14:55

It's okay Ahau...

But why is the forum acting weird? I cannot see your above quoted post unless I use the provided link... strange.
Ahau, are you kinda hidden at times in here? =@

Oh, and that is quite off topic in here.
Cheers!
Yours Rava

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#37 by Ahau » 14 Mar 2011, 15:05

I'm not sure why you can't see that post--I can see it when I open the thread and move through to page 3. That is strange.

I do tend to log in and out here (often from my phone) but I should not be hidden.

I posted that message (about startx and lxde) because the day before, I had tried getting xfce to run by adding 'autoexec=startxfce4;xconf;telinit~4', and got a black screen, with the KDE music starting up on my speakers--so I realized that both were running at the same time. Some edits to /etc/rc.d/rc4.d allowed me to get into xfce.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#38 by Rava » 14 Mar 2011, 19:57

Ahau wrote:Some edits to /etc/rc.d/rc4.d allowed me to get into xfce.
What edits have that been?
Cheers!
Yours Rava

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#39 by Ahau » 14 Mar 2011, 22:06

I changed everything from 'lxde' to 'xfce', and 'lxdm' to 'startxfce4'. This disabled starting lxde, and I've been meaning to go back in and edit the script to allow all three to start up, but haven't found the time or the willpower.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#40 by Rava » 15 Mar 2011, 02:00

Ahau wrote:I changed everything from 'lxde' to 'xfce', and 'lxdm' to 'startxfce4'. This disabled starting lxde, and I've been meaning to go back in and edit the script to allow all three to start up, but haven't found the time or the willpower.
Do you have the XFCe 64 module already ready for Porteus 1.0? URL then, pwease... Image
And I wanted to ask: when I did tweak old Slax 6.1.2 to be without KDE, this popup info bubble when loading and activating or deactivating info in XWindows also was gone; I tried to find out what there is needed to have that in an NON KDE Slax (and now: in an NON KDE Porteus) but so far have not managed doing so.
Does anyone of you guys have some hints for me?


I forgot to answer this:
Ahau wrote:btw Rava-- I was able to get the nVidia driver to run instead of nouveau in v1 beta, by either adding the 'nomodeset' cheatcode per fanthom's instructions, or by blacklisting nouveau in /etc/modeprobe.d/blacklist.conf.
But... does the 'nomodeset' not do more than just kicking out nouveau?
I tried to check the cheatcodes txt of Porteus 1.0b for that but even than I did copy the stuff from the ISO to the filesystem, for some reason the cheatcodes txt misses... :wall:

And about /etc/modeprobe.d/blacklist.conf ... that's not available in Remix as it seems... I wanted to check for the syntax. Do I just put in the full path of the to-be-blacklisted driver in there?
Or just

Code: Select all

nouveau
?
Cheers!
Yours Rava

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#41 by Ahau » 15 Mar 2011, 02:19

fanthom will have to answer about the specifics of 'nomodeset' cheatcode. This is what the FAQ says:
"
6. How to disable Kernel Mode Setting on amd/ati, nvidia and intel GPU's? Since v08 Kernel Mode Setting (high resolution in console mode) is enabled by default on all modern GPU's. If you wish to disable it - just add: 'nomodeset' cheatcode to /boot/porteus.cfg file. Be aware that intel, opensource radeon and nouveau drivers wont work without KMS in Graphical User Interface mode"

to blacklist nouveau, add 'blacklist nouveau' on a new line in the blacklist.conf file and save it.

I have a working xfce 4.6 64-bit module that runs in V1-beta, but it needs a lot of cleaning up. icons don't work in thunar, it could use a new theme, etc. I can post a link if you would like it (in a new thread. we're pretty far OT here).
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#42 by fanthom » 15 Mar 2011, 22:19

@Rava
1) posts gets merged automatically as i hate double posters :evil:
2) since 1.0 BETA we have done our best to rewrite all tools for xdialog (xpns-tool, porteusmodman, xactivate/xdeactivate, etc..) so you are able to activate modules by double click on lxde and all other desktops (all files required for this are in 002-xorg module now).
3) cheatcodes.txt is placed now in /boot/docs (among with other txt files).
4) yes - 'nomodeset' cheatcode prevents of loading nouveau drm kernel module. nouveau must be not loaded in time of building nvidia binary driver.
---------------------------------------------------------
some good news:
- kernel 2.6.38 final is ready :) unfortunately - no aufs update this Monday, maybe next?
- one of most annoying KDE-4.6.x bugs seems to be resolved (there is still a hope for 4.6.x line for porteus 1.0 Final):
https://bugs.kde.org/show_bug.cgi?id=209962
- first RC of Slackware-13.37 was released 6 days ago :)

Aufs 'deactivate modules on the fly' bug is holding us at the moment. We can't do much about it - just wait till it's fixed upstream.
I think we can wait a bit and base Porteus-1.0 on Slackware-13.37 Final (hopefully aufs matures on 2.6.38 kernel then).

I would say that Porteus-v1.0 will be released on 3rd week of April so please be patient and keep posting bugs/suggestions as usual :)

Regards,
fanthom
Please add [Solved] to your thread title if the solution was found.

att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#43 by att » 17 Mar 2011, 13:31

Hi,

I converted all my "old" Slax-Remix/Porteus-Alpha modules to xzm, by using ' lzm2xzm "*.lzm" ' :

amaya-11.3.1-x86_64.xzm 14.331.904 15.03.2011 15:02 -a--
aria2-1.5.2-x86_64.xzm 2.240.512 15.03.2011 15:02 -a--
attbins.xzm 815.104 15.03.2011 15:02 -a--
binbot_teamviewer.xzm 15.347.712 15.03.2011 15:03 -a--
bluefish-2.0.2-x86_64.xzm 2.568.192 15.03.2011 15:03 -a--
boa-0.94.14rc21.xzm 65.536 15.03.2011 15:03 -a--
cabextract-1.2-i486.xzm 32.768 15.03.2011 15:03 -a--
chntpw-0.99.6-x86_64.xzm 106.496 15.03.2011 15:03 -a--
chromium-7.0.520.0-x86_64.xzm 18.714.624 15.03.2011 15:03 -a--
chttpd-1.3-x86_64.xzm 12.288 15.03.2011 15:03 -a--
cksfv.xzm 12.288 15.03.2011 15:03 -a--
cli-ftp-pack.xzm 692.224 15.03.2011 15:03 -a--
compat32.xzm 51.953.664 15.03.2011 15:04 -a--
ctorrent-1.3.4.xzm 94.208 15.03.2011 15:04 -a--
curl-7.19.4.xzm 450.560 15.03.2011 15:04 -a--
db44-4.4.20-2.xzm 1.699.840 15.03.2011 15:04 -a--
dillo-2-0-all.xzm 1.740.800 15.03.2011 15:04 -a--
emesene-1.6.3-x86_64.xzm 1.069.056 15.03.2011 15:04 -a--
etherape-0.9.7-i686-1.xzm 376.832 15.03.2011 15:04 -a--
ettercap-ng-0.7.3-i486-1tb.xzm 442.368 15.03.2011 15:04 -a--
filezilla-3.3.4.1-x86_64-1ponce.xzm 3.309.568 15.03.2011 15:04 -a--
fontsdir.xzm 94.208 15.03.2011 15:04 -a--
fping-2.4b2_to-i486-1sl.xzm 16.384 15.03.2011 15:04 -a--
german.xzm 2.850.816 15.03.2011 15:04 -a--
gftp-2.0.19-x86_64.xzm 241.664 15.03.2011 15:04 -a--
glibc-i18n-x86_64-1ftm.xzm 11.923.456 15.03.2011 15:04 -a--
gnutls-2.10.1-x86_64.xzm 1.200.128 15.03.2011 15:04 -a--
hping2.xzm 36.864 15.03.2011 15:04 -a--
JDownloader-2-x86_64.xzm 37.543.936 15.03.2011 15:02 -a--
jre-6u23-x86_64.xzm 22.827.008 15.03.2011 15:04 -a--
kde-l10n-de-4.5.4-x86_64-1ftm.xzm 1.978.368 15.03.2011 15:05 -a--
kftpgrabber-0.8.1-i686-1.xzm 774.144 15.03.2011 15:05 -a--
kismet-2008-05-r1-i686.xzm 663.552 15.03.2011 15:05 -a--
klibido-0.2.5-i486-1bj.xzm 290.816 15.03.2011 15:05 -a--
kompozer-0.8-0.5.b3-x86_64.xzm 7.933.952 15.03.2011 15:05 -a--
kphone-4.2-6.xzm 290.816 15.03.2011 15:05 -a--
krusader-2.0.0-x86_64.xzm 1.716.224 15.03.2011 15:05 -a--
ktorrent-2.2.8.xzm 2.252.800 15.03.2011 15:05 -a--
kvirc-4.0.2-x86_64.xzm 4.362.240 15.03.2011 15:05 -a--
kvpnc-0.9.6.xzm 1.679.360 15.03.2011 15:05 -a--
libiconv--1.13.1--0.1.3.xzm 1.081.344 15.03.2011 15:05 -a--
libmspack-0.0.20060920alpha-x86_64-1ponce.xzm 106.496 15.03.2011 15:05 -a--
libtasn1--1.8--0.1.3.xzm 90.112 15.03.2011 15:05 -a--
locales-slax-remix-x86_64-1ftm.xzm 27.013.120 15.03.2011 15:05 -a--
locate.xzm 1.576.960 15.03.2011 15:05 -a--
lua-5.1.3.xzm 233.472 15.03.2011 15:05 -a--
lynx-cur-2.8.8dev.1-1.xzm 1.695.744 15.03.2011 15:05 -a--
multilib-v09-B2.xzm 29.745.152 15.03.2011 15:06 -a--
mysql-5.0.67-1.xzm 13.897.728 15.03.2011 15:06 -a--
nano-2.0.7-i486-1.xzm 315.392 15.03.2011 15:06 -a--
nasm-2.07.xzm 200.704 15.03.2011 15:06 -a--
nc-1.10.xzm 45.056 15.03.2011 15:06 -a--
newspost.xzm 32.768 15.03.2011 15:06 -a--
nmap-5.21-x86_64.xzm 1.527.808 15.03.2011 15:06 -a--
ntfs_progs-x86_64.xzm 278.528 15.03.2011 15:06 -a--
ntfsprogs.2.0.0.xzm 278.528 15.03.2011 15:06 -a--
ntp-4.2.4p0-i486-1.xzm 1.290.240 15.03.2011 15:06 -a--
nzb-0.1.9.xzm 5.345.280 15.03.2011 15:06 -a--
nzbperl_SSL.xzm 729.088 15.03.2011 15:06 -a--
opera-11.00-1156-x86_64.xzm 8.994.816 15.03.2011 15:06 -a--
p7zip-9.04-x86_64.xzm 1.626.112 15.03.2011 15:06 -a--
pidgin-2.7.7-x86_64.xzm 6.635.520 15.03.2011 15:06 -a--
portmap-5-0.xzm 24.576 15.03.2011 15:06 -a--
pppoe-knemo.xzm 4.096 15.03.2011 15:06 -a--
python-2.5.2-i486-1.xzm 5.373.952 15.03.2011 15:06 -a--
qt-4.5.2.xzm 124.825.600 15.03.2011 15:08 -a--
rar-3.71.xzm 311.296 15.03.2011 15:08 -a--
ruby-1.9.1_p378-x86_64.xzm 4.038.656 15.03.2011 15:08 -a--
Screen_4_0_2.xzm 32.768 15.03.2011 15:02 -a--
seamonkey-2.1b1-x86_64.xzm 19.787.776 15.03.2011 15:08 -a--
sniffit_0_3_5.xzm 28.672 15.03.2011 15:08 -a--
sqlite-3.5.8.xzm 1.003.520 15.03.2011 15:08 -a--
squid-3.1.4-x86_64.xzm 958.464 15.03.2011 15:08 -a--
sshd-activate.xzm 4.096 15.03.2011 15:08 -a--
stunnel_3_26.xzm 81.920 15.03.2011 15:08 -a--
tar-1.23.xzm 1.327.104 15.03.2011 15:08 -a--
tcc-0.9.25.xzm 241.664 15.03.2011 15:08 -a--
tcl8.4.19.xzm 966.656 15.03.2011 15:08 -a--
telnet-1.5.xzm 36.864 15.03.2011 15:08 -a--
thttpd.xzm 45.056 15.03.2011 15:08 -a--
tigervnc-r4126-x86_64.xzm 2.719.744 15.03.2011 15:08 -a--
tinyproxy.xzm 32.768 15.03.2011 15:08 -a--
truecrypt-6.1a.xzm 1.916.928 15.03.2011 15:08 -a--
unrar-3-7-8.xzm 86.016 15.03.2011 15:08 -a--
upx-3.03.xzm 319.488 15.03.2011 15:08 -a--
uudeview-0.5.20-i486-1as.xzm 212.992 15.03.2011 15:08 -a--
vmware-view-open-client-4.0.1-235010.xzm 1.245.184 15.03.2011 15:08 -a--
vpnc-0.5.3.xzm 114.688 15.03.2011 15:08 -a--
wicd-1.6.2.2-i686-3cca.xzm 376.832 15.03.2011 15:08 -a--
wifi-radar-1.9.9-1.1.xzm 36.864 15.03.2011 15:08 -a--
wine-1.3.5-x86_64.xzm 26.058.752 15.03.2011 15:09 -a--
wireless-tools-29-1.1.xzm 106.496 15.03.2011 15:09 -a--
wlassistant-0-5-7.xzm 118.784 15.03.2011 15:09 -a--
wxPython-2.8.11.0-x86_64-1ponce.xzm 15.122.432 15.03.2011 15:09 -a--
xchat.xzm 1.847.296 15.03.2011 15:09 -a--
xchat-2.8.8-x86_64.xzm 1.298.432 15.03.2011 15:09 -a--
xfce-4.6.1-x86_64.xzm 8.110.080 15.03.2011 15:09 -a--
yakuake-2.9.7-x86_64.xzm 188.416 15.03.2011 15:09 -a--
yasm-1.1.xzm 2.310.144 15.03.2011 15:09 -a--
youtube-dl-2010.12.09-x86_64.xzm 20.480 15.03.2011 15:09 -a--

I'm now in the process of trying out all these modules.

So far "JDownloader" does not start up, which is a pity. He worked fine when he was a SQ4-lzm-module.
The console says that JDownloader is about to start, but even after a couple of minutes nothing happens.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4547
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#44 by fanthom » 18 Mar 2011, 15:25

@att
i'm sorry to say that but you have a nice mess over there:
1) doubled packages (packages which currently exist in a ISO - all in newer version than yours):
tar-1.23.xzm 1.327.104 15.03.2011 15:08 -a--
unrar-3-7-8.xzm 86.016 15.03.2011 15:08 -a--
telnet-1.5.xzm 36.864 15.03.2011 15:08 -a--
sqlite-3.5.8.xzm 1.003.520 15.03.2011 15:08 -a--
wireless-tools-29-1.1.xzm 106.496 15.03.2011 15:09 -a--
and many more....
2) duplicated packages (2 version of the same package in your set)
ntfs_progs-x86_64.xzm 278.528 15.03.2011 15:06 -a--
ntfsprogs.2.0.0.xzm 278.528 15.03.2011 15:06 -a--
xchat.xzm 1.847.296 15.03.2011 15:09 -a--
xchat-2.8.8-x86_64.xzm 1.298.432 15.03.2011 15:09 -a--

3) those 2 are the worst in your set:
python-2.5.2-i486-1.xzm 5.373.952 15.03.2011 15:06 -a--
qt-4.5.2.xzm 124.825.600 15.03.2011 15:08 -a--

python and (especially qt) are provided in the ISO and can't be replaced by older versions.
i'm really surprised that porteus is able to boot with all this cr*p.

Your set is a perfect example how to kill porteus with additional (unnecessary) modules.
Please dont be surprised that "JDownloader" does not start up.

remove all your stuff, then add applications (not libraries) 'one by one' and check if it works. If not then run 'slackyd -d' to find missing deps.

Good luck!
Please add [Solved] to your thread title if the solution was found.

att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

Re: Porteus-v1.0-beta-x86_64 is ready :)

Post#45 by att » 21 Mar 2011, 22:53

Hello Fanthom,

Sorry for the messy modules. I have cut out QT and python, and also wiped the dupes of Xchat and NTFSprogs.

Here are my results so far:

* JDownloader only runs fine when started from a root shell. User "Guest" won't do. -> Icon appears but program does not start.
* Teamviewer6 has the same problem.
* Amaya complains about a missing library:
/opt//Amaya/wx/bin/amaya_bin: error while loading shared libraries: libraptor.so.1: cannot open shared object file: No such file or directory
Note the double slash after opt: "opt//Amaya/..." -> no idea why.
* kftpgrabber: error while loading shared libraries: libkdnssd.so.1: cannot open shared object file: No such file or directory
* VMWare view open client will not display any fonts correctly, but will display squares instead of characters everywhere on the start screen.
* dillo: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
* emesene :
Traceback (most recent call last):
File "/usr/share/emesene/emesene", line 34, in <module>
import Controller
File "/usr/share/emesene/Controller.py", line 22, in <module>
import pygtk
ImportError: No module named pygtk

* etherape: error while loading shared libraries: libglade-2.0.so.0: cannot open shared object file: No such file or directory

* ettercap: Displays squares instead of characters

* ktorrent: error while loading shared libraries: libgmp.so.3: cannot open shared object file: No such file or directory

* wicd:
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-daemon.py", line 44, in <module>
import gobject
ImportError: No module named gobject

* klibido: error while loading shared libraries: libkmdi.so.1: cannot open shared object file: No such file or directory

However, many programs just work great, even as user guest: Kompozer, Opera11, Firefox, TigerVNC Server and Viewer, XChat, GFTPd, Seamonkey, wpa_gui

Hope that helps, more later
ATT

Locked