Some things "cant communicate with KLaunch"

[Bongo5HH]

I keep getting this error "can't communicate with KLaunch" like when I try to open a document with OOo from the File menu. If I click on a file in a directory it opens fine though.

Other programs are not starting either. Such as K3B, Amarok, Hexter... but Juk works.

Ideas?

Kev

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

When I click on a .iso file to launch K3B I get the error "KDEInit could not launch '/usr/bin/k3b'."

HH won't boot into KDE3 for me.. could that be the problem? that the KDE3 programs aren't working

Kev

[dibl]

Re: Some things "cant communicate with KLaunch"

You're ahead of me Kev, I haven't tried K3b yet. If no one has replied by the time I get home from work tonight, I'll give K3b a try and see what happens.

You say "won't boot into KDE3" -- does that mean you have KDE4 working on it? Is this HH Alpha 3 or 4?

Thanks.

[integr8e]

Re: Some things "cant communicate with KLaunch"

If you are running a KDE4 session, you should be able to fix the problem by logging out, logging into a KDE3 session, logging out again, and logging back into KDE4.

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

Hey integr8e,

I did actually try that but KDE3 on HH won't load for me. The LiveCD works but after an install it gets stuck at "initalizing system resources" or settings.. or something like that. The third icon in (looks like a printer) after KDM. It goes to a completely black screen, no cursor. I've let it sit there for 20 mins with no hope of it getting to the desktop.

So I did an upgrade from my KDE4 desktop on Gutsy to HH and now KDE4 loads in HH and anything that is KDE3 related won't work.

Kev

[dibl]

Re: Some things "cant communicate with KLaunch"

@Bongo, I pretty well destroyed my HH Alpha 4 system last night, trying to get KDE4 to install on it. That never did work.

However, before I trashed it I ran KB3, and it worked fine -- set up an ISO file to burn, it ran the md5sum, and would have burned it if I had put a CD in the drive.

When you get that black screen trying to boot into KDE 4, you might want to try a "Alt-F1" on it, just in case there's some video issue. If you see a login prompt, that's your clue.

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

@Bongo, I pretty well destroyed my HH Alpha 4 system last night, trying to get KDE4 to install on it. That never did work.

Ah ha! I'm not alone. hehe Well at least I have KDE4 running right now.

when you get that black screen trying to boot into KDE 4, you might want to try a "Alt-F1" on it, just in case there's some video issue. If you see a login prompt, that's your clue.

What does Alt-F1 do?

I'll give it a try. I wonder if that's what the problem is. There was someone else wondering if his nV8800GT would work with HH. I have a 8600GT.

It would make sense if it's a video problem. Hrmmm I wonder if I install the official drivers using Envy and try it again. Maybe the supplied drivers aren't working?

Kev

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

Since I actually haven't logged into KDE3 in HH maybe there are user files that haven't been set up yet...

If I install the video drivers in KDE4, and then boot into KDE3 maybe that will allow the KDE3 desktop to be setup properly.

I'm inspired to give it a try.


Kev

[dibl]

Re: Some things "cant communicate with KLaunch"

I'm inspired to give it a try.

Go for it!

Why don't you install a fresh HH Alpha 4 and then install KDE 4, and then tell me how the heck you did it?

I've lost track of the number of ways Kubuntu will misbehave with an Nvidia card -- since I got my 8800GTS I've learned a whole bunch more .... :P

However, there is one mode where it will actually boot to the CLI, but end up hidden behind a black screen that's left from a failed attempt to run KDM. Alt-F1 can take you back to the F1 tty terminal, where you can do a text login and then set up a VESA display, or run Envy in text mode, or whatever you want to do.

For mine, I found that the nvidia-glx-new package does a great job on HH, and then you run the

sudo nvidia-xconfig --add-argb-glx-visuals --composite

command to write a new xorg.conf that will support running compiz.

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

Envy won't install the drivers.. lol

It was missing some dependencies but I got them in.. now it won't work.

Kev

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

Envy Installer Log says that HH is not supported by Envy. doh!

Kev

[dibl]

Re: Some things "cant communicate with KLaunch"

Envy Installer Log says that HH is not supported by Envy. doh!

Kev

Yeah, I tried that on the weekend -- I could have saved you the trouble.

But, can you just grab the "nvidia-glx-new" package? It works fine on mine -- puts in the newest driver (169.09).

[integr8e]

Re: Some things "cant communicate with KLaunch"

@Bongo, I pretty well destroyed my HH Alpha 4 system last night, trying to get KDE4 to install on it. That never did work.

I'm glad to see I'm not the only person having trouble getting KDE4 installed on HH

[Bongo5HH]

Re: Some things "cant communicate with KLaunch"

OK Alt-F1 didn't do anything for me.

So what do you think that means?

I'm going to try the driver package now

Kev

[dibl]

Re: Some things "cant communicate with KLaunch"

I'm glad to see I'm not the only person having trouble getting KDE4 installed on HH

No you aren't alone, Integr8e! Here is tonight's result, on a brand-new, updated HH Alpha 4:

dibl@cville:~$ sudo apt-get install kde4-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kde4-core: Depends: kdebase-workspace (>= 4:4.0.0) but it is not going to be installed
E: Broken packages

It's closer than the other day when the list of unmet dependencies was 5 or 6 packages, but ....