KDE4-apps just dissappear

[mr_hero]

Hi there,

just installed newest porteus and have some trouble I can't solve myself. First of all: Porteus is just gorgeous and installation incredible easy. Most things are really easy to set-up. Package Manager, Vbox-Builder, firewall-setup and all the other selfmade-scripts are extremely helpfull. Printer and wifi work out of the box! Never saw something like this on other distros.

Here my problems:

1) Some programs need KDE-libs to run. For some reason all applications just dissapear when kdelibs-4.10.5-x86_64-2.xzm gets activated. Start menu is just empty then. Same with the package aaa_elflibs-14.1-x86_64-bundle.xzm. I downloaded both with the USM-Tool. aaa_elflibs-14.1-x86_64-bundle can't be extracted in addition and when I try to mount it, nothing happens.

2) Nvidia-driver is not working. I have a geforce 7600 GT and user the driver nVidia-304.119-porteus-v3.0-x86_64-1ftm. At bootup porteus says something like: "Xorg didn't start, deactivating proprietary drivers". Tried forum-search already - it seems I chose the correct driver. Glxgears is working, desktop-effects don't work (I'm on KDE4). How can I track down the problem?

3) KDE doesn't remember the root password when I hit the checkbox to do so. Very annoying. Just activated 10 packaged - KDE asked for password 10 times.

[fanthom]

hi mr_hero,

For some reason all applications just dissapear when kdelibs-4.10.5-x86_64-2.xzm gets activated.

our KDE4 is never than the one from slackweare-14.1 and you cant use whole kdelibs i'm afraid. i'll try to prepare compatibility module with extracted single libs, drop it to /extras and will post here when done.

Nvidia-driver is not working. I have a geforce 7600 GT and user the driver nVidia-304.119-porteus-v3.0-x86_64-1ftm

please recreate the issue -> generate 'psinfo' report -> upload to pastebin.ca -> link here.

KDE doesn't remember the root password when I hit the checkbox to do so.

afair kdesu remembers password for certain action only (if you activate the same module twice it shouldn't ask for a password). will try to find if it can remember the password for the whole session (or say - 10 mins).

thanks for your feedback.

[mr_hero]

Hey amigo, you know what? I red the snowden-book. I don't place a whole system-report on the web! Give me a public-key or some SSL-upload-site and I'll send you the file. Pastebin...no chance!

Isn't there some logfile reporting an error when xorg fails to start? I can copy and paste that message here.

[donald]

@mr_hero
wow...and I thought I'm the one with paranoia.
now it seems that I'm only the number 2 in the Ranking... 8)

[mr_hero]

LOL Guess since this book was published we'll get a lot of friends. Over 90.000.000.000 E-Mails are filtered by NSA worldwide per month. 120.000.000.000 phone-connections get protocolled. The program listening to our conversation right here right now is called xkeyscore, caching the whole world-wide web-activity for five days. On request it combines phone-numbers, e-mail-adresses, log-ins and user-activity for every single user on the globe. This book really gives reason to every paranoia someone could have.

[mr_hero]

BTW, which logfile gives me the error-output of failed xorg-start?

Edit:

Guess I found something: /var/log/Xorg.0.log reads this error:

Code: Select all

[    29.511] (II) LoadModule: "nv"
[    29.527] (WW) Warning, couldn't open module nv
[    29.527] (II) UnloadModule: "nv"
[    29.528] (II) Unloading nv
[    29.528] (EE) Failed to load module "nv" (module does not exist, 0)

a bit later another error occurs:

Code: Select all

[    29.561] (II) Module modesetting: vendor="X.Org Foundation"
[    29.561] 	compiled for 1.14.4, module version = 0.8.1
[    29.561] 	Module class: X.Org Video Driver
[    29.561] 	ABI class: X.Org Video Driver, version 14.1
[    29.561] (II) LoadModule: "fbdev"
[    29.576] (WW) Warning, couldn't open module fbdev
[    29.576] (II) UnloadModule: "fbdev"
[    29.576] (II) Unloading fbdev
[    29.576] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    29.576] (II) NOUVEAU driver 
[    29.577] (II) NOUVEAU driver for NVIDIA chipset families :
[    29.577] 	RIVA TNT        (NV04)
[    29.577] 	RIVA TNT2       (NV05)
[    29.577] 	GeForce 256     (NV10)
[    29.577] 	GeForce 2       (NV11, NV15)
[    29.577] 	GeForce 4MX     (NV17, NV18)
[    29.577] 	GeForce 3       (NV20)
[    29.577] 	GeForce 4Ti     (NV25, NV28)
[    29.577] 	GeForce FX      (NV3x)
[    29.577] 	GeForce 6       (NV4x)
[    29.577] 	GeForce 7       (G7x)
[    29.577] 	GeForce 8       (G8x)
[    29.577] 	GeForce GTX 200 (NVA0)
[    29.577] 	GeForce GTX 400 (NVC0)
[    29.577] (II) VESA: driver for VESA chipsets: vesa
[    29.577] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    29.577] (++) using VT number 7

Since I didn't remove nVidia-304.119-porteus-v3.0-x86_64-1ftm.xzm from my modules-folder I think the same the error occurs at every boot.

[fanthom]

i really need to get the log files to debug this so (if you can) please send them to fanthom@porteus.org otherwise i wont be able to help.

[mr_hero]

Please understand that I don't do this to bug you. I know it is usual not caring about data-security. However, what is usual or not depends on behavior. Just imagine sending personal data unencrypted was very unusual. This assumption actually copes very much with the present situation. For some reason hardly anybody is realizing that, even though the problem got public a year ago already.

I'll try to track down the nvidia-problem myself. I will post here if I found something.

[fanthom]

just realized that this problem has been resolved already:
http://forum.porteus.org/viewtopic.php? ... 937#p25928

please download the driver for 64bit arch.

[mr_hero]

I downloaded the newer 304.121-drivers for 64Bit here and ran nvidia-xconfig. I did a reboot and...problem persists. Same error-messages in the xorg-logfile as before.

Is there any other logfile that could provide more information on this problem?

Edit:

In meantime, I activated nVidia-package manually (porteus seems to deactivate it because of the error) and tried this:

Code: Select all

root@porteus:/# find /lib -name "nvidia.ko"
/lib/modules/3.13.6-porteus/kernel/drivers/video/nvidia.ko
root@porteus:/# modprobe nvidia
modprobe: FATAL: Module nvidia not found.

[fanthom]

your changes must have /lib/modules/3.13.6-porteus/modules.dep never than nvidia.ko from 304.121 -drivers.

please reboot -> highlight 'Always Fresh' mode -> press 'TAB' button -> remove 'base_only' cheatcode -> press enter and check if that gives you nVidia driver loaded and working.

[mr_hero]

This works. I booted with this commandline:

Code: Select all

nomagic norootcopy zram=30% fsck noauto timezone=Europe/Berlin volume=50% kmap=de,us

Of course I got a fresh porteus - all my settings were gone and soundcard didn't work again.

I don't understand this sentence:

your changes must have /lib/modules/3.13.6-porteus/modules.dep never than nvidia.ko from 304.121 -drivers.

The file /lib/modules/3.13.6-porteus/modules.dep does exist on my system. It doesn't contain nvidia.ko. Didn't check when driver was working though.

Regarding to soundcard: I have Sound Blaster X-Fi and installed alsa-plugins to make it work. However it works only now and then. After a reboot it may work or not. KDE is notyfying me of unused soundcard-entries after reboot and is removing them. Found out that X-Fi drivers are included in alsa since creative made them opensource a few years ago.

[fanthom]

so there is something in your changes which prevents nVidia working correctly.
i recommend starting everything from a scratch since you do not want to cooperate in regards to providing the log files.
(i'm sorry but i have no time for guessing what may be wrong with your setup).

[mr_hero]

i'm sorry but i have no time for guessing what may be wrong with your setup

...well, me too.

My changes-folder should have no entries at all - since I used modules only. How about just erasing it? - Or at least all nvidia-related stuff.

I'll report back on success.

A bit earlier you wrote this:

our KDE4 is never than the one from slackweare-14.1 and you cant use whole kdelibs i'm afraid. i'll try to prepare compatibility module with extracted single libs, drop it to /extras and will post here when done.

and this:

afair kdesu remembers password for certain action only (if you activate the same module twice it shouldn't ask for a password). will try to find if it can remember the password for the whole session (or say - 10 mins).

Any progress with this? Please correct me if I'm wrong - but I think language-selection-tool is using the libs. Can't switch KDE to german, even though I made use of the tool.

[mr_hero]

Graphics is working!

Thank you!

I just removed all *modules*-files in /changes/lib/modules/3.13.6-porteus/ and did a reboot. The files got re-created by the system and the newer nvidia-driver finally is doing it's job! My windows are wobbling when I move them now! LOL what an awesome crap!