Haven't been having luck with a new Dell Precision T5500n (2 x dualcore "E5503" and 12 GB RAM).
The problem seems to be the ATI FirePro V7800 card.
I can install Ubuntu Natty on it no problem.
However, when I try to load the preconfigured Trinity/Maverick disc, I get the little "keyboard = human" screen and can escape to the menu, but when I try to "try Kubuntu without installing" I get the Kubuntu logo with the progress dots ... then nothing.
In fact, nothing with the monitor icon indicating that the display lost the signal.
Can I install the Trinity packages onto an Ubuntu Natty installation instead?
Peter
Haven't been having luck with a new Dell Precision T5500n (2 x dualcore "E5503" and 12 GB RAM).
The problem seems to be the ATI FirePro V7800 card.
I can install Ubuntu Natty on it no problem.
However, when I try to load the preconfigured Trinity/Maverick disc, I get the little "keyboard = human" screen and can escape to the menu, but when I try to "try Kubuntu without installing" I get the Kubuntu logo with the progress dots ... then nothing.
In fact, nothing with the monitor icon indicating that the display lost the signal.
Can I install the Trinity packages onto an Ubuntu Natty installation instead?
Peter
You can install the beta test packages from the nightly builds for Natty. At this point they are fairly stable, but if you do run into problems please ask here or file a bug report.
I suggest you start with a default Ubuntu (not Kubuntu) installation. Add these four lines to your /etc/apt/sources.list file:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main
The, from a terminal, execute: sudo apt-get update sudo passwd <enter a temporary root password> sudo apt-get install kubuntu-desktop-trinity sudo passwd -l
Tim
On 09/12/11 12:11, Timothy Pearson wrote:
sudo apt-get update
Almost there - got a GPG key?
On 09/12/11 12:34, Peter Laws wrote:
On 09/12/11 12:11, Timothy Pearson wrote:
sudo apt-get update
Almost there - got a GPG key?
Found the key line on http://www.trinitydesktop.org/installation.php#ubuntu
Thanks!
On my way!
On 09/12/11 12:37, Peter Laws wrote:
On 09/12/11 12:34, Peter Laws wrote:
On 09/12/11 12:11, Timothy Pearson wrote:
sudo apt-get update
Almost there - got a GPG key?
Found the key line on http://www.trinitydesktop.org/installation.php#ubuntu
Spamming the list today. :-)
Key imported OK, but I get this:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity Desktop Environment
On 09/12/2011 10:11 AM, Timothy Pearson wrote:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main ... sudo apt-get update ... sudo apt-get install kubuntu-desktop-trinity
Did that, but after numerous tries over several hours, all I get out of the install command, or a dist-upgrade, is a bunch of "failed to fetch" messages, with the occasional file downloaded. Is the repo down or something?
On 09/12/2011 10:11 AM, Timothy Pearson wrote:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main ... sudo apt-get update ... sudo apt-get install kubuntu-desktop-trinity
Did that, but after numerous tries over several hours, all I get out of the install command, or a dist-upgrade, is a bunch of "failed to fetch" messages, with the occasional file downloaded. Is the repo down or something?
With help from the original poster I tracked the problem down to a failed mirror. That mirror has been disabled until I can contact the site administrator.
Please let me know if you run into any further problems!
Tim
On 09/12/11 12:11, Timothy Pearson wrote:
You can install the beta test packages from the nightly builds for Natty. At this point they are fairly stable, but if you do run into problems please ask here or file a bug report.
I suggest you start with a default Ubuntu (not Kubuntu) installation. Add these four lines to your /etc/apt/sources.list file:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main
The, from a terminal, execute: sudo apt-get update sudo passwd
<enter a temporary root password> sudo apt-get install kubuntu-desktop-trinity sudo passwd -l
Gave up and reinstalled Natty. Did an update/dist-upgrade and rebooted. Added your repos did an update again.
Still get the key errors:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0 W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0
And this from apt-get when I install kubuntu-desktop-trinity
WARNING: The following packages cannot be authenticated!
After all that ... it hung while booting. I power-cycled it and got the KDE^H^H^HTrinity login. Logged in and got a popup that said:
There was an error setting up inter-process communications for KDE. The message returned by the system was:
Could not read network connection list. /tmp/1571417411/.DCOPserver_toto2__0
Please check that the "dcopserver" program is running!
Naturally, I clicked OK. Ended up with a frameless xterm window and no menus, etc, as if I was in a failsafe session (though there was a desktop image). Logout/login and get no popup, but still have a single xterm albeit with frame, menus, etc. Still no icons, menus, etc.
Help?
On 09/28/11 14:48, Peter Laws wrote:
On 09/12/11 12:11, Timothy Pearson wrote:
After all that ... it hung while booting. I power-cycled it and got the KDE^H^H^HTrinity login. Logged in and got a popup that said:
There was an error setting up inter-process communications for KDE. The message returned by the system was:
Could not read network connection list. /tmp/1571417411/.DCOPserver_toto2__0
Please check that the "dcopserver" program is running!
Naturally, I clicked OK. Ended up with a frameless xterm window and no menus, etc, as if I was in a failsafe session (though there was a desktop image). Logout/login and get no popup, but still have a single xterm albeit with frame, menus, etc. Still no icons, menus, etc.
Help?
Looking at it now, dcopserver is running:
root 1502 1 0 14:42 ? 00:00:00 dcopserver [kdeinit] --nosid --suicide
On 09/28/11 14:48, Peter Laws wrote:
On 09/12/11 12:11, Timothy Pearson wrote:
After all that ... it hung while booting. I power-cycled it and got the KDE^H^H^HTrinity login. Logged in and got a popup that said:
There was an error setting up inter-process communications for KDE. The message returned by the system was:
Could not read network connection list. /tmp/1571417411/.DCOPserver_toto2__0
Please check that the "dcopserver" program is running!
Naturally, I clicked OK. Ended up with a frameless xterm window and no menus, etc, as if I was in a failsafe session (though there was a desktop image). Logout/login and get no popup, but still have a single xterm albeit with frame, menus, etc. Still no icons, menus, etc.
Help?
Looking at it now, dcopserver is running:
root 1502 1 0 14:42 ? 00:00:00 dcopserver [kdeinit] --nosid --suicide
This might be related to a feature that was added a couple of weeks ago. Try editing your /etc/trinity/kdm/kdmrc (or kdmdistrc file if it is present) and edit this line: WindowManager=kwin to read WindowManager=
If the WindowManager=<something> line is not present then add it in the [X-*-Greeter] section of the file.
Reboot and try logging in again.
Let me know if this allows you to login--it is a workaround and the real cause of problem will need to be investigated if this works.
Thanks!
Tim
On 09/28/11 15:56, Timothy Pearson wrote:
This might be related to a feature that was added a couple of weeks ago. Try editing your /etc/trinity/kdm/kdmrc (or kdmdistrc file if it is present) and edit this line: WindowManager=kwin to read WindowManager=
If the WindowManager=<something> line is not present then add it in the [X-*-Greeter] section of the file.
Reboot and try logging in again.
Let me know if this allows you to login--it is a workaround and the real cause of problem will need to be investigated if this works.
Welll ... by default, it appears to be commented out in both /etc/trinity/kdm/kdmrc and /etc/trinity/kdm/kdmdistrc and the comments say that kwin is the default ...
# Window manager binary name, if window decorations are desired. "" means no window manager support. # Default is "kwin" #WindowManager=
I can add it anyway and see if that works (meaning something else is broken) but to which file should it be added?
Peter
On 09/28/11 16:33, Peter Laws wrote:
On 09/28/11 15:56, Timothy Pearson wrote:
This might be related to a feature that was added a couple of weeks ago. Try editing your /etc/trinity/kdm/kdmrc (or kdmdistrc file if it is present) and edit this line: WindowManager=kwin to read WindowManager=
If the WindowManager=<something> line is not present then add it in the [X-*-Greeter] section of the file.
Reboot and try logging in again.
Let me know if this allows you to login--it is a workaround and the real cause of problem will need to be investigated if this works.
Let me also reiterate that I can log in, just not wm is running or at least, I only get one xterm.
On 09/28/11 16:33, Peter Laws wrote:
On 09/28/11 15:56, Timothy Pearson wrote:
This might be related to a feature that was added a couple of weeks ago. Try editing your /etc/trinity/kdm/kdmrc (or kdmdistrc file if it is
present) and edit this line:
WindowManager=kwin to read WindowManager=
If the WindowManager=<something> line is not present then add it in
the [X-*-Greeter] section of the file.
Reboot and try logging in again.
Let me know if this allows you to login--it is a workaround and the real cause of problem will need to be investigated if this works.
Let me also reiterate that I can log in, just not wm is running or at
least, I only get one xterm.
You did select TDE as the login session type while you were at the login screen, correct?
If that does not work, then add the line to your kdmdistrc file and try logging in to TDE. I would only consider the workaround successful if you get a full TDE session as a result.
Tim
OK. I've been up about 24 hours. Ubuntu Natty (amd64) on a Dell somethingorother. Install of Ubuntu was smoooth. Did the steps Tim outlined:
On 09/12/11 12:11, Timothy Pearson wrote:
I suggest you start with a default Ubuntu (not Kubuntu) installation. Add these four lines to your /etc/apt/sources.list file:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... natty main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/ub... natty main
The, from a terminal, execute: sudo apt-get update sudo passwd
<enter a temporary root password> sudo apt-get install kubuntu-desktop-trinity sudo passwd -l
Be sure to specifically choose a TDE session on the login screen. If you are untarring an old $HOME onto your new installation simply make a symlink from .kde (if you used Kubuntu previously) or .kde3 if you've used one of Tim's previous kits/distros and all your stuff comes back magically.
Hurray!
Note that there is still an issue with keys and mirrors, so you will likely still see:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0 W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0
Thanks, Tim, for not forcing me (and the rest of us) to have to make a new desktop layout just because KDE4 is "better" in some programmer's mind. I've had mine for *years*, even under Solaris(!) and didn't see the need to change.
Some reports on issues a little later ... :-)
<snip>
Note that there is still an issue with keys and mirrors, so you will likely still see:
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0 W: GPG error: http://ppa.quickbuild.pearsoncomputing.net natty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 43F1DC4F2B8638D0
This issue should only exist with the nightly builds repository, so it is (reasonably) safe to ignore the warning messages. At this point fixing it is a low priority, as the cause of the problem is buried deep within complex auto-signing code that is broken on this repository only. The official release repository works correctly as far as signing is concerned.
Thanks, Tim, for not forcing me (and the rest of us) to have to make a new desktop layout just because KDE4 is "better" in some programmer's mind. I've had mine for *years*, even under Solaris(!) and didn't see the need to change.
You are more than welcome! :-) Of course at this point other members of the Trinity development team deserve some of the credit as well, especially Serghei Amelian, whose work was instrumental in getting the core system to compile on modern Linux distributions.
Tim
On 09/30/11 14:13, Timothy Pearson wrote:
This issue should only exist with the nightly builds repository, so it is (reasonably) safe to ignore the warning messages. At this point fixing it
OK, then that begs the question: should I be using something different? Or is is the NB stuff all that will work with Natty?
And what is the correct forum for bug reports (kdesktop_lock locks OK, but then I have to ssh in from elsewhere to unlock it ... and by "unlock" I mean "kill" :-).
Thanks, also, to the other TDE developers!
-
Dan Youngquist -
Peter Laws -
Timothy Pearson