LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 01-02-2015, 05:11 PM   #1
APott
LQ Newbie
 
Registered: Jan 2015
Distribution: Debian Wheezy
Posts: 5

Rep: Reputation: Disabled
Debian Wheezy booting into TTY1


Hello! Last week I installed Debian Wheezy on my Desktop computer with Gnome 3, it's been working wonderfully. On Wednesday night I was using the computer fine, as usual, performed no updates or anything, and when I was finished I shut down as usual. I didn't use the computer at all on Thursday but upon booting up my computer today (Friday) I was faced with an issue. Debian boots straight into TTY1 and I am never met with the friendly login screen as I was previously.

So the first thing I did was ALT + F7 to try to get into a graphical session if it existed, that didn't work. Second thing I did was log into the TTY and then run `startx`. So the screen flashes as everything starts up then I am met with a screen that says: "Oh no! Something has gone wrong.", an image of a desktop computer with a frowny face and "A problem has occurred and the system can't recover. Please log out and try again." [logout button].

So I press the logout button and I have returned to my TTY session. What does this mean? What happened to cause this to happen seemingly randomly? Any help is very much appreciated because I don't want to have to reinstall...
 
Old 01-02-2015, 05:13 PM   #2
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Debian stable (and OpenBSD-current)
Posts: 1,187

Rep: Reputation: 285Reputation: 285Reputation: 285
What is the output of:
Code:
grep EE /var/log/Xorg.0.log
 
1 members found this post helpful.
Old 01-02-2015, 05:18 PM   #3
APott
LQ Newbie
 
Registered: Jan 2015
Distribution: Debian Wheezy
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Head_on_a_Stick View Post
What is the output of:
Code:
grep EE /var/log/Xorg.0.log
Code:
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  295.667] (EE) Server terminated successfully (0). Closing log file.
That's about what I got. I typed it by hand so hopefully there aren't any typos, but that's what I got.

Thanks for the help.

Last edited by APott; 01-02-2015 at 05:20 PM. Reason: Formatting
 
Old 01-02-2015, 05:39 PM   #4
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Debian stable (and OpenBSD-current)
Posts: 1,187

Rep: Reputation: 285Reputation: 285Reputation: 285
The logs are clear then.

I had that error message myself recently when trying to start GNOME-classic without Nautilus (Caja) installed.

Had you removed or installed any programs before your system started misbehaving?

Have you added any PPAs or Testing/Unstable sources?
 
Old 01-02-2015, 05:41 PM   #5
APott
LQ Newbie
 
Registered: Jan 2015
Distribution: Debian Wheezy
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Head_on_a_Stick View Post
The logs are clear then.

I had that error message myself recently when trying to start GNOME-classic without Nautilus (Caja) installed.

Had you removed or installed any programs before your system started misbehaving?

Have you added any PPAs or Testing/Unstable sources?
I did add a Debian Jessie non-free source and installed Steam. Do you think this caused the issue?

Thanks for the help.
 
Old 01-02-2015, 05:45 PM   #6
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Debian stable (and OpenBSD-current)
Posts: 1,187

Rep: Reputation: 285Reputation: 285Reputation: 285
Quote:
Originally Posted by APott View Post
I did add a Debian Jessie non-free source and installed Steam. Do you think this caused the issue?
Yes, yes and thrice yes.

Please read this link:
https://wiki.debian.org/DontBreakDebian

EDIT: You will have to re-install from scratch, sorry.

Last edited by Head_on_a_Stick; 01-02-2015 at 05:46 PM. Reason: Breaking the bad news
 
1 members found this post helpful.
Old 01-02-2015, 05:53 PM   #7
APott
LQ Newbie
 
Registered: Jan 2015
Distribution: Debian Wheezy
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Head_on_a_Stick View Post
Yes, yes and thrice yes.

Please read this link:
https://wiki.debian.org/DontBreakDebian

EDIT: You will have to re-install from scratch, sorry.
Ahhhhhhhhhhhhhh....

Alright, thanks for the help then.
 
Old 01-02-2015, 05:54 PM   #8
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Debian stable (and OpenBSD-current)
Posts: 1,187

Rep: Reputation: 285Reputation: 285Reputation: 285
You're welcome.
 
1 members found this post helpful.
Old 01-06-2015, 04:29 PM   #9
froosh
LQ Newbie
 
Registered: Jan 2015
Posts: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by Head_on_a_Stick View Post
Yes, yes and thrice yes.

EDIT: You will have to re-install from scratch, sorry.
Why is a re-install required? I have Steam running on Debian Jessie on another computer working fine. But I tried installing Steam on a new laptop and I get the "Oh no!" message as well. Both are running Testing.
 
Old 01-06-2015, 08:50 PM   #10
APott
LQ Newbie
 
Registered: Jan 2015
Distribution: Debian Wheezy
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by froosh View Post
Why is a re-install required? I have Steam running on Debian Jessie on another computer working fine. But I tried installing Steam on a new laptop and I get the "Oh no!" message as well. Both are running Testing.
I'm running Debian Wheezy and I stupidly added a Jessie source in order to be able to obtain Steam. Apparently it's a really bad idea to mix version sources in Debian, now I know, lol.
 
Old 01-06-2015, 10:06 PM   #11
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628

Rep: Reputation: 497Reputation: 497Reputation: 497Reputation: 497Reputation: 497
Keeping in mind that I am an expert at breaking systems by similar means and ones quite a bit more advanced;

You may get away with adding a package like whatever it takes to install steam if you immediately remove the entry from your sources.list that suplied it.

There are several things that can go wrong when mixing Stable and unstable repos. The main cause is the that Wheezy is basically 3 years old. Jessie is not. Jessie has packages that are not going to work with wheezy packages just do to the difference in package version.

Assuming, however, that steam doesn't upgrade some of your depends so that they no longer work with the packages they were installed to support from the Wheezy repos then installing that and getting rid of the Jessie repo will leave you pretty safe.

If you leave the jessie repo in the sources.list then you are going to be upgrading wheezy partially to jessie and having a totally confused system.

A clean install is not really needed. You can fix this from where you are now. I can attest to that by personal experience and it is a very educational adventure. It will also take you a LOT longer than a clean install. Hours at best.

If you want newer packages install testing or Sid. This testing round I find that Sid actually runs a bit better on my hardware than Jessie does. This was not the case with Wheezy when it was testing.

There really is little harm, except maybe getting a buggy package, in installing Sid packages in testing. They are not that far apart. If you are patient for a little while the Sid packages will show up in testing anyway.

My Wheezy install, for instance, is actually running Thunar 1.6.? which was lifted from the experimental repo when Wheezy was testing. Xfce 4.10 was supposed to be used in Wheezy but was dropped out of the repo and reverted to 4.8 because of problems with the panel way to close to freeze time for Wheezy. That ment that Thunar was reverted too and what ever version 4.8 ran didn't have tabbed file browsing. I like tabs, I put in the newer Thunar which had, along with all of Xfce 4.10 been thrown back to experimental.

This has caused me no problems at all. The package fit fine with Wheezy at the time and it is still the same version so it is still fine.

You couldn't possibly get me to install packages for testing or Sid in that Wheezy install today. Could be altogether too much fun.

I would suggest a dual boot with testing or Sid with any new package you want to have. You wouldn't need a large / partition. And, assuming you have a separate /home for Wheezy, you can share the /home. Only thing you MUST do is use a different user name for each install sharing a /home. This avoids conflicts in your user configuration files (~/.foo). Linux is a multi user system and this really isn't any different than have more users on one install.

Testing and Sid take more management than stable does by far. Ignoring running update/upgrade cycles pretty often, I do it everyday, can cause some grief and, at least, make for really large numbers of packages to be upgraded at one time.

On the other hand if you want the newer packages this is the way to do it.

Keep in mind that Debian uses a different definition of Stable than most distros. Ubuntu bases their LTS versions on Debian testing. Their "regular" versions, all those between the LTS releases, are based on Sid. With a little care it is not hard to keep them ticking along quite nicely.

I was a bit upset with this Sid install the other day. Had to reboot to clear out some problems. Checked my uptime and it was only 9 and a half days. There is a reason it is called unstable. Under Wheezy that would really tick me off.
 
Old 01-06-2015, 10:07 PM   #12
froosh
LQ Newbie
 
Registered: Jan 2015
Posts: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by APott View Post
I'm running Debian Wheezy and I stupidly added a Jessie source in order to be able to obtain Steam. Apparently it's a really bad idea to mix version sources in Debian, now I know, lol.
Oh okay, I mistakenly thought you were running Jessie. I had the exact same error message as you while running Jessie as well, which I think was due to installing the glx-i386 drivers when I don't have an nvidia card.
 
Old 01-07-2015, 07:50 AM   #13
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Debian stable (and OpenBSD-current)
Posts: 1,187

Rep: Reputation: 285Reputation: 285Reputation: 285
@widget -- You would be better off running a pure sid system rather than Testing with some packages from Unstable.

The situation in Debianland has changed somewhat since they introduced the Experimental repository.

While it may have been the case in the past that Testing was more reliable than Unstable, this is no longer true.

The packages in Unstable migrate to Testing after a period of 10-14 days. This delay means that if any packages in Testing have problems, they remain broken for a while.

In sid, newer packages are pushed out very quickly and any borkage is much shorter-lived than that found in Testing.

Have a read of what the Debian developers themselves recommend:
Quote:
Which Debian distribution (stable/testing/unstable) is better for me?

The answer is a bit complicated. It really depends on what you intend to do. One solution would be to ask a friend who runs Debian. But that does not mean that you cannot make an independent decision. In fact, you should be able to decide once you complete reading this chapter.

If security or stability are at all important for you: install stable. period. This is the most preferred way.

If you are a new user installing to a desktop machine, start with stable. Some of the software is quite old, but it's the least buggy environment to work in. You can easily switch to the more modern unstable (or testing) once you are a little more confident.

If you are a desktop user with a lot of experience in the operating system and does not mind facing the odd bug now and then, or even full system breakage, use unstable. It has all the latest and greatest software, and bugs are usually fixed swiftly.

If you are running a server, especially one that has strong stability requirements or is exposed to the Internet, install stable. This is by far the strongest and safest choice.
https://www.debian.org/doc/manuals/d...aq/ch-choosing
As you can see, Testing is not recommended for anyone -- these days it is the pure development version.

IMO there is no point whatsoever running a Testing system with packages from sid -- just run pure sid.
Quote:
Originally Posted by widget
Assuming, however, that steam doesn't upgrade some of your depends so that they no longer work with the packages they were installed to support from the Wheezy repos then installing that and getting rid of the Jessie repo will leave you pretty safe.
The main problem with trying to run Steam in wheezy is that it requires version 2.17 of glibc -- this library is used by almost every program on the system and upgrading it will break wheezy.
 
Old 01-07-2015, 08:14 PM   #14
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628

Rep: Reputation: 497Reputation: 497Reputation: 497Reputation: 497Reputation: 497
What I am on right now is Sid. Sid is my production OS.

There are installs on here of Debian 6, 7, testing and Sid.

There are times in testing when you really are better off to grab a package from Sid. This is due to bugs, when found in testing and then patched, do not go to the testing repo. They go to the Sid repo first to make try to make sure that they are not introducing a new bug. Therefore the bug fixes, if the bug in fact is affecting your testing install, from the Sid repo make life a lot more pleasant.

Currently the only out of version package I have installed is LibreOffice 4.4 in one of my "victim" installs of Sid (not this install). That package is available in the experimental repo. It will not be available to Sid until after Debian 8 (Jessie) is released. This is also going to be installed on my victim testing install.

Those victim installs are used as buffers for package upgrades that for some reason worry me as to their affect on the testing or Sid installs that I actually use. And to try packages that may be interesting from other repos. They are basically ment to be expendable.

Yes I am a serial multi booter. So far I have not found a 12 step program for this afliction.

I do not recommend to people to mix repos. It can be done. With care and a knowlege of what will be added or, apparently in the case of steam on Wheezy, what will be removed.

People should first off have working knowledge of what their system needs and look carefully at what is being done before hitting Y on the install. It would be a great thing to know something about pinning too.

Pinning is something you learn after breaking systems enough times to decide maybe the tools available are there for a reason.

But really if you want the newer packages, instead of mashing them into a version not ment to run them, installing an unstable version is the best way to go.

Hopefully tonight I am going to reboot and switch over to testing for a couple of days. Had some sort of network problem with my main testing install in chroot last night. Need to straighten that out. It is the kind of thing that is supposed to happen, if happen it must, to the VictimT install. A bit peeved with myself about this one.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Dual booting Debian Wheezy 7 and Kali Linux reconrob Linux - Newbie 3 05-09-2014 01:55 AM
[SOLVED] Now I've done it - Debian dual boot (Sid, Wheezy) grub overwritten, lost Wheezy? ShaneRoach Debian 23 02-02-2014 02:28 PM
[SOLVED] debian:switch to tty1, no text, no prompt, only black Leslie-Lau Linux - Newbie 2 11-28-2011 04:14 AM
[SOLVED] NVIDIA driver from debian causes tty1-6 to display wrong radiodee1 Debian 3 08-12-2011 01:08 PM
Booting up with splash image ends in tty1 tallmtt Linux - General 5 09-13-2008 09:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 05:50 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration