-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As part of upgrading from Debian Lenny to Squeeze, I also upgraded from KDE-Trinity 3.5.12 (Lenny version) to 3.5.13 (Squeeze version). After the upgrade finished, I tried to open Konqueror; the result was a hung machine.
- From as virtual terminal (ctrl-alt-F1) I rebooted the machine. On reboot the GUI did not appear; the machine opened with the shell bang. I the logged in as root and ran the command "startx". The result was a solid blue screen at ctrl-alt-F7; further action was impossible.
I am at a loss as to what to do next. Specifically what should I do to get the login screen so that I can log in as a user?
Ken Heard
On Friday 16 December 2011 20:23:32 Ken Heard wrote:
I am at a loss as to what to do next. Specifically what should I do to get the login screen so that I can log in as a user?
I would recommend to create a new user account first (as root: adduser...), then login as that user (shell) and try startx. if that doesnt work, remove all trinity stuff and then install trinity-desktop 'from scratch'
werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Werner Joss wrote:
I would recommend to create a new user account first (as root: adduser...), then login as that user (shell) and try startx. if that doesnt work, remove all trinity stuff and then install trinity-desktop 'from scratch'
I already had two users for the box. After booting the computer I logged in as the other user and ran startx. This time the splash screen appeared and after ostensibly loading KDE-trinity the result was the same unworkable totally blue screen.
However, the virtual terminal showed several lines of text, ending with the following two:
FATAL: Module fbcon not found. SELinux: Disabled on system, not enabling in X server
Does the forgoing provide a clue as to what to do next?
If I need to reinstall completely KDE-trinity 3.5.13 is there a single command, or are there two (or more) commands which will purge all of it and then reinstall it?
Ken Heard
On Friday 16 December 2011 21:11:34 Ken Heard wrote:
FATAL: Module fbcon not found. SELinux: Disabled on system, not enabling in X server
Does the forgoing provide a clue as to what to do next?
hm, looks like some problem with xorg, not trinity. can you try to install/test with another WM, e.g. icewm - does that work/start ? (put the alternate wm in your ~/.xinitrc file, then startx)
werner
As part of upgrading from Debian Lenny to Squeeze, I also upgraded from KDE-Trinity 3.5.12 (Lenny version) to 3.5.13 (Squeeze version). After the upgrade finished, I tried to open Konqueror; the result was a hung machine.
when you upgraded within TDE, than the upgrade was not complete. redo the upgrade from a text console (<ctrl>+<alt>+<f1>).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mag. Dr. Nikolaus Klepp wrote:
when you upgraded within TDE, then the upgrade was not complete. redo the upgrade from a text console (<ctrl>+<alt>+<f1>).
Aha! I remembered when I did the first upgrade by running command "apt-get upgrade" 225 packages were upgraded, but 47 packages were kept back. Of these 47, all but four had either "trinity" or "kde" in its name. The other four were "lib" packages. At the time the first 225 packages were upgraded, it occurred to me that I should as a second step upgrade the other 47 packages; but I neglected to do so.
Now, taking my cue from Mag. Dr. Klepp did so. Once again I ran the command "apt-get upgrade". Apt-get however identified the 47 packages but refused to upgrade them.
I next decided to try the "aptitude upgrade" command instead. The response from that command stated that 46 of the 47 packages that apt-get refused to install aptitude would install. I addition, aptitude would remove nine more packages and install five new ones. It recommended one more package but would not install it.
After all of the forgoing was finished, ctrl-alt-F7 revealed the login screen ready for entry of user name and password. I logged on and was able to open Konqueror without difficulty. (There was however a problem with Konqueror which will be the subject of another post to the list.)
I am consequently quite curious as to why aptitude would install the missing packages; whereas apt-get would not. I could not find anything in the release notes or the Debian installation instructions to indicate that in upgrading to 3.5.13 aptitude should be used instead of apt-get. I initially used apt-get because the release notes and instructions for the Lenny to Squeeze upgrade specifically recommended using apt-get instead of aptitude.
Ken Heard, Toronto, Canada
On 19/12/11 15:43, Ken Heard wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mag. Dr. Nikolaus Klepp wrote:
when you upgraded within TDE, then the upgrade was not complete. redo the upgrade from a text console (<ctrl>+<alt>+<f1>).
Aha! I remembered when I did the first upgrade by running command "apt-get upgrade" 225 packages were upgraded, but 47 packages were kept back. Of these 47, all but four had either "trinity" or "kde" in its name. The other four were "lib" packages. At the time the first 225 packages were upgraded, it occurred to me that I should as a second step upgrade the other 47 packages; but I neglected to do so.
Now, taking my cue from Mag. Dr. Klepp did so. Once again I ran the command "apt-get upgrade". Apt-get however identified the 47 packages but refused to upgrade them.
I next decided to try the "aptitude upgrade" command instead. The response from that command stated that 46 of the 47 packages that apt-get refused to install aptitude would install. I addition, aptitude would remove nine more packages and install five new ones. It recommended one more package but would not install it.
After all of the forgoing was finished, ctrl-alt-F7 revealed the login screen ready for entry of user name and password. I logged on and was able to open Konqueror without difficulty. (There was however a problem with Konqueror which will be the subject of another post to the list.)
I am consequently quite curious as to why aptitude would install the missing packages; whereas apt-get would not. I could not find anything in the release notes or the Debian installation instructions to indicate that in upgrading to 3.5.13 aptitude should be used instead of apt-get. I initially used apt-get because the release notes and instructions for the Lenny to Squeeze upgrade specifically recommended using apt-get instead of aptitude.
Ken Heard, Toronto, Canada
I don't use aptitude myself so can't help much with that.
What I do know is, <apt-get upgrade> is a "safe upgrade" command which upgrades only those packages (or libs) which do not affect other packages. That's where you got into difficulty.
What you needed was actually <apt-get dist-upgrade> (see <man apt-get>)
For everyday use, you should stick to one or the other as their package-tracking databases may differ
David
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Hare wrote:
<snip>
I am consequently quite curious as to why aptitude would install the missing packages; whereas apt-get would not. I could not find anything in the release notes or the Debian installation instructions to indicate that in upgrading to 3.5.13 aptitude should be used instead of apt-get. I initially used apt-get because the release notes and instructions for the Lenny to Squeeze upgrade specifically recommended using apt-get instead of aptitude.
Ken Heard, Toronto, Canada
I don't use aptitude myself so can't help much with that.
What I do know is, <apt-get upgrade> is a "safe upgrade" command which upgrades only those packages (or libs) which do not affect other packages. That's where you got into difficulty.
What you needed was actually <apt-get dist-upgrade> (see <man apt-get>)
Hadn't thought of using the apt-get dist-upgrade option to upgrade to kde-trinity 3.5.13, although I did use it as instructed to upgrade from Lenny to Squeeze. It is too late now to find out whether using apt-get dist-upgrade for the first attempt to upgrade to 3.5.13 would have avoided the problem I encountered.
For everyday use, you should stick to one or the other as their package-tracking databases may differ
They do differ; so one should indeed stick to one or the other. In fact the upgrade option in aptitude has been deprecated; aptitude now insists on either safe-upgrade or full-upgrade, but for the latter will for historical reasons accept dist-upgrade.
Apt-get upgrade option seems to be the same as the safe-upgrade option in aptitude, but the dist-upgrade in apt-get does not seem to be the same as the aptitude full-upgrade option. Apt-get also has a deselect-upgrade option.
Chapter 4.4 of the Squeeze release notes (1) states: "In previous releases aptitude was recommend, but recent versions of apt-get provide equivalent functionality and also have show to give *more consistently* the desired upgrade results." (Emphasis mine)
1. http://www.debian.org/releases/stable/i386/release-notes/index-en.html
Ken
On 19/12/11 17:11, Ken Heard wrote:
Hadn't thought of using the apt-get dist-upgrade option to upgrade to kde-trinity 3.5.13, although I did use it as instructed to upgrade from Lenny to Squeeze. It is too late now to find out whether using apt-get dist-upgrade for the first attempt to upgrade to 3.5.13 would have avoided the problem I encountered.
Probably yes.
<man apt-get>
upgrade upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available.
dist-upgrade dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. So, dist-upgrade command may remove some packages. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. See also apt_preferences(5) for a mechanism for overriding the general settings for individual packages.
On 16/12/11 19:23, Ken Heard wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As part of upgrading from Debian Lenny to Squeeze, I also upgraded from KDE-Trinity 3.5.12 (Lenny version) to 3.5.13 (Squeeze version). After the upgrade finished, I tried to open Konqueror; the result was a hung machine.
- From as virtual terminal (ctrl-alt-F1) I rebooted the machine. On
reboot the GUI did not appear; the machine opened with the shell bang. I the logged in as root and ran the command "startx". The result was a solid blue screen at ctrl-alt-F7; further action was impossible.
I am at a loss as to what to do next. Specifically what should I do to get the login screen so that I can log in as a user?
Ken Heard
No experience of lenny+TDE>squeeze+TDE myself.
It might help if you say how this upgrade was done. I've written here before that major upgrades without closing X is asking for trouble. Maybe some things did not complete leaving mismatches. It would have been better to upgrade only Debian stuff first, using the recommended Debian method.
Other possible solutions now (with X closed, i.e. /etc/init.d/kdm-trinity stop))
Purge all TDE packages (your ~ stuff will remain):
for i in $(dpkg -l|grep ii|grep "trinity"|awk '{print $2}'); do apt-get purge $i; done
Disable TDE mirrors temporarily
apt-get update && apt-get dist-upgrade
Re-enable (current Squeeze) TDE mirrors, apt-get update and install TDE again (it's all still in your apt-cache)
No guarantees any of that is correct, I'm only a TDE user with some Debian experience.
More possibilities to try
Disable xorg.conf (Squeeze doesn't normally need it) mv /etc/X11/xorg.conf /etc/X11/xorg.conf.renamed
apt-get update apt-get -f install
dpkg-reconfigure xserver-xorg
If you use a proprietary graphics driver, have you reinstalled it?
"KDE-Trinity 3.5.13 hung my machine" might not be quite correct, maybe more to do with a xorg/graphics related issue in the Debian upgrade
-
David Hare -
Ken Heard -
Mag. Dr. Nikolaus Klepp -
Werner Joss