Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #173126 > unrolled thread

Problems with upgrade from Wheezy to Jessie

Back to article view | Back to linux.debian.user

Contents

  Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-02 18:30 +0200
    Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-02 19:00 +0200
      Re: Problems with upgrade from Wheezy to Jessie err404@free.fr - 2016-10-02 19:40 +0200
        Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-02 20:30 +0200
          Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-03 07:00 +0200
            Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-03 09:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-02 20:40 +0200
      Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-02 21:10 +0200
        Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-03 19:40 +0200
      Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-03 19:10 +0200
        Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-03 19:30 +0200
          Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-03 21:10 +0200
            Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-03 21:50 +0200
              Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-04 20:50 +0200
                Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-04 22:00 +0200
                  Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-05 12:00 +0200
                    Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-05 20:10 +0200
                      Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-05 21:00 +0200
                        Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 20:00 +0200
                          Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-06 20:50 +0200
                            Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-07 19:30 +0200
                              Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-07 22:30 +0200
                            Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Hans Kraus <hans@hanswkraus.com> - 2016-10-08 14:00 +0200
                              Re: Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Brian <ad44@cityscape.co.uk> - 2016-10-09 23:50 +0200
                                Re: Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-17 19:20 +0200
              Re: Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-05 18:20 +0200
                Re: Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-06 20:00 +0200
                  Re:: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 21:00 +0200
                    Re: : Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-06 21:40 +0200
              Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 20:00 +0200
        Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-03 19:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-02 20:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Eike Lantzsch <zp6cge@gmx.net> - 2016-10-02 22:10 +0200
    Re: Problems with upgrade from Wheezy to Jessie David Christensen <dpchrist@holgerdanske.com> - 2016-10-02 23:50 +0200
      Re: Problems with upgrade from Wheezy to Jessie David Christensen <dpchrist@holgerdanske.com> - 2016-11-06 00:00 +0100
    Re: Problems with upgrade from Wheezy to Jessie Patrick Bartek <nemommxiv@gmail.com> - 2016-10-03 02:10 +0200
      Re: Problems with upgrade from Wheezy to Jessie songbird <songbird@anthive.com> - 2016-10-05 17:20 +0200
    Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-07 03:30 +0200

Page 1 of 2  [1] 2  Next page →

#173126 — Problems with upgrade from Wheezy to Jessie

Hi,

I upgraded my Debian server about a week ago from Wheezy to Jessie.
After that the GUI stopped, I see only  the grey screen with the sad
computer telling me " Oh no, Something is Wrong" and the only option is
to log out.

I'm using Gnome as my desktop. I installed the package again with:
apt-get install task-gnome-desktop
I did not get any error message, but that didn't cure my problem.

Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
error message but  that didn't cure my problem.

I rebooted the system several times but with no avail.

Which info should I provide and/or where should I check my system for
errors? The text based login via ssh (I use Putty from Win 8.1)
functions without problems.

Kind regards, Hans

[toc] | [next] | [standalone]

#173127

On Sun, 2 Oct 2016 17:59:48 +0200, Hans Kraus wrote:

>Hi,
>
>I upgraded my Debian server about a week ago from Wheezy to Jessie.
>After that the GUI stopped, I see only  the grey screen with the sad
>computer telling me " Oh no, Something is Wrong" and the only option is
>to log out.
>
>I'm using Gnome as my desktop. I installed the package again with:
>apt-get install task-gnome-desktop
>I did not get any error message, but that didn't cure my problem.
>
>Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
>error message but  that didn't cure my problem.
>
>I rebooted the system several times but with no avail.
>
>Which info should I provide and/or where should I check my system for
>errors? The text based login via ssh (I use Putty from Win 8.1)
>functions without problems.
>

Sorry, Hans, not a solution, just a "Me too", My wife has an eMachines
PC bought from Wal-Mart, and each time I have tried to move her from
Wheezy to Jessie, the upgrade reports no errors, you can log in and
the GUI is there, but the moment you touch the mouse the screen breaks
up into a whole series of short horizontal lines, and there is no way
out of it but to reboot. This is totally reproducible, and I've seen
exactly the same effect with a recent Linux Mint (not LMDE, the
Ubuntu-based version) live disk. 

If anyone had this problem and managed to sort it, I'd be very
grateful for the solution, because at the moment my wife's PC is stuck
at Wheezy, and cannot be upgraded. 

Thanks, 

Brian. 

[toc] | [prev] | [next] | [standalone]

#173128

[Multipart message — attachments visible in raw view] — view raw

what is your hadware?
graphic card?
and did you have any drivers or firmware for this? like firmware free or non-free, or drivers for nvidia, or amd etc.

[toc] | [prev] | [next] | [standalone]

#173130

On Sun, 2 Oct 2016 19:29:12 +0200, you wrote:

>what is your hadware?
>graphic card?
>and did you have any drivers or firmware for this? like firmware free or non-free, or drivers for nvidia, or amd etc.

It's an eMachines desktop which was originally supplied with Windows
7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
GeForce 6150 SE nForce 430 rev a2. Looking at the output from a 
dpkg -l there's no mention of any of the packages you list above. When
I installed Wheezy for my wife, I basically just accepted defaults, so
anything which has been loaded was loaded by the installer. 

I can send you the full output from dpkg -l if you wish, just ask. 


Brian. 

[toc] | [prev] | [next] | [standalone]

#173142

brian composed on 2016-10-02 14:23 (UTC-0400):

> On Sun, 2 Oct 2016 19:29:12 +0200, err404@free.fr wrote:

>>what is your hadware?
>>graphic card?
>>and did you have any drivers or firmware for this? like firmware free or non-free, or drivers for nvidia, or amd etc.

> It's an eMachines desktop which was originally supplied with Windows
> 7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
> Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
> GeForce 6150 SE nForce 430 rev a2.

This has been a problematic gfxchip for more than one user over the years. 
Try adding this to the kernel cmdline:

	nouveau.config=NvMSI=0

I have a machine with the same gfxchip on its motherboard,
https://us.msi.com/Motherboard/K9N6PGM2V.html
but currently it doesn't have any Debian installed on it to check which if 
any releases are helped by it. It does have openSUSE 13.1 (kernel 3.12, 
server 1.14.3), 13.2 (kernel 3.16, server 1.16.1), 42.1 (kernel 4.1, server 
1.17.2) and Tumbleweed (kernel 4.7.4, server 1.18.4) installed. All four 
suffer random brief video corruption running X. Tumbleweed seems to have 
almost eliminated the corruption that is excessive and unacceptable in the 
others. IIRC, last Debian tried on it was Wheezy with Gnome or Mate or 
Cinnamon, and too much trouble or impossible at that time to actually use X.

Something else to try is ensuring xserver-xorg-video-modesetting is 
installed, then purging xserver-xorg-video-nouveau and all traces of NVidia's 
proprietary driver bits. The modesetting driver has been getting quite some 
attention from the devs:
http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX

The original owner of this motherboard suffered to the extent he installed a 
PCI gfxcard as a workaround when the motherboard was rather young. I got the 
motherboard free when when he bought a new one that I installed after its 
original RAM went bad.

> Looking at the output from a
> dpkg -l there's no mention of any of the packages you list above. When
> I installed Wheezy for my wife, I basically just accepted defaults, so
> anything which has been loaded was loaded by the installer.

> I can send you the full output from dpkg -l if you wish, just ask.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#173143

On Mon, 3 Oct 2016 00:55:37 -0400, Felix Miata wrote:

>brian composed on 2016-10-02 14:23 (UTC-0400):
>
>> On Sun, 2 Oct 2016 19:29:12 +0200, err404@free.fr wrote:
>
>>>what is your hadware?
>>>graphic card?
>>>and did you have any drivers or firmware for this? like firmware free or non-free, or drivers for nvidia, or amd etc.
>
>> It's an eMachines desktop which was originally supplied with Windows
>> 7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
>> Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
>> GeForce 6150 SE nForce 430 rev a2.
>
>This has been a problematic gfxchip for more than one user over the years. 
>Try adding this to the kernel cmdline:
>
>	nouveau.config=NvMSI=0
>
>I have a machine with the same gfxchip on its motherboard,
>https://us.msi.com/Motherboard/K9N6PGM2V.html
>but currently it doesn't have any Debian installed on it to check which if 
>any releases are helped by it. It does have openSUSE 13.1 (kernel 3.12, 
>server 1.14.3), 13.2 (kernel 3.16, server 1.16.1), 42.1 (kernel 4.1, server 
>1.17.2) and Tumbleweed (kernel 4.7.4, server 1.18.4) installed. All four 
>suffer random brief video corruption running X. Tumbleweed seems to have 
>almost eliminated the corruption that is excessive and unacceptable in the 
>others. IIRC, last Debian tried on it was Wheezy with Gnome or Mate or 
>Cinnamon, and too much trouble or impossible at that time to actually use X.
>
>Something else to try is ensuring xserver-xorg-video-modesetting is 
>installed, then purging xserver-xorg-video-nouveau and all traces of NVidia's 
>proprietary driver bits. The modesetting driver has been getting quite some 
>attention from the devs:
>http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX
>
>The original owner of this motherboard suffered to the extent he installed a 
>PCI gfxcard as a workaround when the motherboard was rather young. I got the 
>motherboard free when when he bought a new one that I installed after its 
>original RAM went bad.
>

Thanks Felix, I'll give it a try as soon as I can persuade my wife to
stay off the PC for a while, and report back. It will be a week or so
though, as I've got a couple of chapters of a book to deliver with a
deadline of next weekend. 

Brian. 

[toc] | [prev] | [next] | [standalone]

#173131

On 10/02/2016 05:59 PM, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped,

This is a bit vague, so a better explanation would be good. What
exactly do you mean "gui stopped"? Did that happen during the
update? Or at boot? Does the login screen show up? Does this
message show up after login?

> I see only  the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.

Could you transcribe the precise error message?

> I installed the package again with:
> apt-get install task-gnome-desktop
> I did not get any error message, but that didn't cure my problem.
> 
> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
> error message but  that didn't cure my problem.

That means your packages are in a state that dpkg assumes to be
consistent. However, since you upgraded recently, and apparently
still have access to your shell, could you tell us what the
contents of /etc/apt/sources.list is?

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#173133

On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:

> On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > After that the GUI stopped,
> 
> This is a bit vague, so a better explanation would be good. What
> exactly do you mean "gui stopped"? Did that happen during the
> update? Or at boot? Does the login screen show up? Does this
> message show up after login?
> 
> > I see only  the grey screen with the sad
> > computer telling me " Oh no, Something is Wrong" and the only option is
> > to log out.
> 
> Could you transcribe the precise error message?

He has.

[toc] | [prev] | [next] | [standalone]

#173156

On Sun 02 Oct 2016 at 20:02:39 +0100, Brian wrote:

> On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:
> 
> > On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > > After that the GUI stopped,
> > 
> > This is a bit vague, so a better explanation would be good. What
> > exactly do you mean "gui stopped"? Did that happen during the
> > update? Or at boot? Does the login screen show up? Does this
> > message show up after login?
> > 
> > > I see only  the grey screen with the sad
> > > computer telling me " Oh no, Something is Wrong" and the only option is
> > > to log out.
> > 
> > Could you transcribe the precise error message?
> 
> He has.

Apologies; my remark was made too hastily. Firstly, it was not the
complete message (as we have seen). Secondly, there can be two
differently worded messages depending on whether gnome-session or
gnome-shell is involved.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173153

Hi, thank's for your sppedy reaction.

With "gui stopped" I mean the following:
After the boot process, instead of the graphical login screen where
one can select the user, enter the password and do some selections,
the following screen appears:

A pic of a sad computer with the text (the first line is in bold):
===================================================================
        Oh no! Something has gone wrong.
A problem occurred and the system can't recover.
         Please log out and try again.
                -----------
                | Log Out |
                -----------
===================================================================
I get the same screen when I choose another shell (via Ctrl-Alt-F2),
log in as root and enter: startx.

The /etc/apt/sources.list:
===================================================================
root@robbe:~# cat /etc/apt/sources.list
# deb http://ftp.at.debian.org/debian/ wheezy main

# deb http://backports.debian.org/debian-backports wheezy-backports non-free
deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free

deb http://ftp.at.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.at.debian.org/debian/ jessie main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

# wheezy-updates, previously known as 'volatile'
deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib 
non-free

deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
===================================================================
The parts "main contrib non-free" are on the same line; Thundebird
insists on line breaks ...

Kind regards,
Hans

Am 02.10.2016 um 20:31 schrieb Christian Seiler:
> On 10/02/2016 05:59 PM, Hans Kraus wrote:
>> I upgraded my Debian server about a week ago from Wheezy to Jessie.
>> After that the GUI stopped,
>
> This is a bit vague, so a better explanation would be good. What
> exactly do you mean "gui stopped"? Did that happen during the
> update? Or at boot? Does the login screen show up? Does this
> message show up after login?
>
>> I see only  the grey screen with the sad
>> computer telling me " Oh no, Something is Wrong" and the only option is
>> to log out.
>
> Could you transcribe the precise error message?
>
>> I installed the package again with:
>> apt-get install task-gnome-desktop
>> I did not get any error message, but that didn't cure my problem.
>>
>> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
>> error message but  that didn't cure my problem.
>
> That means your packages are in a state that dpkg assumes to be
> consistent. However, since you upgraded recently, and apparently
> still have access to your shell, could you tell us what the
> contents of /etc/apt/sources.list is?
>
> Regards,
> Christian
>

[toc] | [prev] | [next] | [standalone]

#173154

On 10/03/2016 06:50 PM, Hans Kraus wrote:
> With "gui stopped" I mean the following:
> After the boot process, instead of the graphical login screen where
> one can select the user, enter the password and do some selections,
> the following screen appears:
> 
> A pic of a sad computer with the text (the first line is in bold):
> ===================================================================
>        Oh no! Something has gone wrong.
> A problem occurred and the system can't recover.
>         Please log out and try again.
>                -----------
>                | Log Out |
>                -----------
> ===================================================================
> I get the same screen when I choose another shell (via Ctrl-Alt-F2),
> log in as root and enter: startx.

Ok, this appears to be a GNOME-specific error message.

Could you restart the computer, try to log in, wait until that
message pops up, don't close the message, switch to another console
(Ctrl+Alt+F2) and run the following command as root?

journalctl -b1 -n40 _UID=1000

(Replace 1000 with your user id, you can look it via running id in
the console as your normal user; 1000 is the default for the first
user created by the Debian installer.)

See if there's anything in that output that might be relevant here.

> The /etc/apt/sources.list:
> ===================================================================
> root@robbe:~# cat /etc/apt/sources.list
> # deb http://ftp.at.debian.org/debian/ wheezy main
> 
> # deb http://backports.debian.org/debian-backports wheezy-backports non-free
> deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free
> 
> deb http://ftp.at.debian.org/debian/ jessie main contrib non-free
> deb-src http://ftp.at.debian.org/debian/ jessie main contrib non-free
> 
> deb http://security.debian.org/ jessie/updates main contrib non-free
> deb-src http://security.debian.org/ jessie/updates main contrib non-free
> 
> # wheezy-updates, previously known as 'volatile'
> deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
> deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
> 
> deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
> ===================================================================

Side note: you have jessie-backports in there twice (first and last
uncommented line), but that's completely harmless. Otherwise, looks
fine.

Could you run

apt-get update
apt-get dist-upgrade

and see if it still wants to upgrade additional software?

Also, what kernel version are you running? (Find that out via the
command "uname -a".)

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#173160

Hi,

my results:
===================================================================
root@robbe:~# uname -a
Linux robbe 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) 
x86_64 GNU/Linux
===================================================================
root@robbe:~# apt-get update
Get:1 http://ftp.at.debian.org jessie-backports InRelease [166 kB]
Hit http://ftp.de.debian.org jessie-backports InRelease
Hit http://security.debian.org jessie/updates InRelease
Ign http://ftp.at.debian.org jessie InRelease
Get:2 http://ftp.at.debian.org jessie-updates InRelease [142 kB]
Ign http://linux.dropbox.com wheezy InRelease
Get:3 http://ftp.de.debian.org jessie-backports/main amd64 
Packages/DiffIndex [27.8 kB]
Hit http://linux.dropbox.com wheezy Release.gpg
Hit http://ftp.at.debian.org jessie Release.gpg
Get:4 http://ftp.at.debian.org jessie-backports/main amd64 
Packages/DiffIndex [27.8 kB]
Get:5 http://ftp.at.debian.org jessie-backports/contrib amd64 
Packages/DiffIndex [16.4 kB]
Get:6 http://ftp.at.debian.org jessie-backports/non-free amd64 
Packages/DiffIndex [12.0 kB]
Get:7 http://ftp.at.debian.org jessie-backports/main i386 
Packages/DiffIndex [27.8 kB]
Hit http://linux.dropbox.com wheezy Release
Get:8 http://ftp.at.debian.org jessie-backports/contrib i386 
Packages/DiffIndex [17.4 kB]
Hit http://security.debian.org jessie/updates/main Sources
Get:9 http://ftp.at.debian.org jessie-backports/non-free i386 
Packages/DiffIndex [11.9 kB]
Get:10 http://ftp.at.debian.org jessie-backports/contrib 
Translation-en/DiffIndex [5,500 B]
Get:11 http://ftp.de.debian.org jessie-backports/contrib amd64 
Packages/DiffIndex [16.4 kB]
Get:12 http://ftp.at.debian.org jessie-backports/main 
Translation-en/DiffIndex [27.8 kB]
Get:13 http://ftp.at.debian.org jessie-backports/non-free 
Translation-en/DiffIndex [8,806 B]
Hit http://ftp.at.debian.org jessie Release
Hit http://security.debian.org jessie/updates/contrib Sources
Hit http://security.debian.org jessie/updates/non-free Sources
Get:14 http://ftp.de.debian.org jessie-backports/non-free amd64 
Packages/DiffIndex [12.0 kB]
Get:15 http://ftp.at.debian.org jessie-backports/main i386 
2016-10-03-1508.04.pdiff [1,925 B]
Get:16 http://ftp.at.debian.org jessie-updates/main Sources [15.5 kB]
Get:17 http://ftp.at.debian.org jessie-updates/contrib Sources [32 B]
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/non-free amd64 Packages
Get:18 http://ftp.de.debian.org jessie-backports/main i386 
Packages/DiffIndex [27.8 kB]
Get:19 http://ftp.de.debian.org jessie-backports/contrib i386 
Packages/DiffIndex [17.4 kB]
Hit http://linux.dropbox.com wheezy/main amd64 Packages
Get:20 http://ftp.at.debian.org jessie-backports/main i386 
2016-10-03-1508.04.pdiff [1,925 B]
Get:21 http://ftp.at.debian.org jessie-updates/non-free Sources [920 B]
Get:22 http://ftp.at.debian.org jessie-updates/main amd64 
Packages/DiffIndex [5,440 B]
Get:23 http://ftp.at.debian.org jessie-updates/contrib amd64 Packages [32 B]
Get:24 http://ftp.at.debian.org jessie-updates/non-free amd64 
Packages/DiffIndex [736 B]
Get:25 http://ftp.at.debian.org jessie-updates/main i386 
Packages/DiffIndex [5,440 B]
Get:26 http://ftp.at.debian.org jessie-updates/contrib i386 Packages [32 B]
Hit http://security.debian.org jessie/updates/main i386 Packages
Hit http://security.debian.org jessie/updates/contrib i386 Packages
Hit http://security.debian.org jessie/updates/non-free i386 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Get:27 http://ftp.de.debian.org jessie-backports/non-free i386 
Packages/DiffIndex [11.9 kB]
Get:28 http://ftp.de.debian.org jessie-backports/contrib 
Translation-en/DiffIndex [5,500 B]
Get:29 http://ftp.at.debian.org jessie-updates/non-free i386 
Packages/DiffIndex [736 B]
Hit http://security.debian.org jessie/updates/main Translation-en
Get:30 http://ftp.de.debian.org jessie-backports/main 
Translation-en/DiffIndex [27.8 kB]
Get:31 http://ftp.at.debian.org jessie-updates/contrib Translation-en [14 B]
Get:32 http://ftp.at.debian.org jessie-updates/main 
Translation-en/DiffIndex [2,704 B]
Get:33 http://ftp.at.debian.org jessie-updates/non-free 
Translation-en/DiffIndex [736 B]
Hit http://ftp.at.debian.org jessie/main Sources
Hit http://security.debian.org jessie/updates/non-free Translation-en
Get:34 http://ftp.de.debian.org jessie-backports/non-free 
Translation-en/DiffIndex [8,806 B]
Hit http://ftp.at.debian.org jessie/contrib Sources
Hit http://ftp.at.debian.org jessie/non-free Sources
Hit http://ftp.at.debian.org jessie/main amd64 Packages
Hit http://ftp.at.debian.org jessie/contrib amd64 Packages
Hit http://linux.dropbox.com wheezy/main i386 Packages
Hit http://ftp.at.debian.org jessie/non-free amd64 Packages
Hit http://ftp.at.debian.org jessie/main i386 Packages
Hit http://ftp.at.debian.org jessie/contrib i386 Packages
Hit http://ftp.at.debian.org jessie/non-free i386 Packages
Hit http://ftp.at.debian.org jessie/contrib Translation-en
Hit http://ftp.at.debian.org jessie/main Translation-en
Hit http://ftp.at.debian.org jessie/non-free Translation-en
Ign http://linux.dropbox.com wheezy/main Translation-en_US
Ign http://linux.dropbox.com wheezy/main Translation-en
Fetched 653 kB in 3s (206 kB/s)
Reading package lists... Done
root@robbe:~#
===================================================================
root@robbe:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   libdbd-mysql-perl
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 119 kB of archives.
After this operation, 3,072 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://security.debian.org/ jessie/updates/main libdbd-mysql-perl 
amd64 4.028-2+deb8u2 [119 kB]
Fetched 119 kB in 0s (868 kB/s)
Reading changelogs... Done
(Reading database ... 309927 files and directories currently installed.)
Preparing to unpack .../libdbd-mysql-perl_4.028-2+deb8u2_amd64.deb ...
Unpacking libdbd-mysql-perl (4.028-2+deb8u2) over (4.028-2+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libdbd-mysql-perl (4.028-2+deb8u2) ...
-------------------------------------------------------------------
The 'libdbd-mysql-perl' is new, three days ago 'apt-get dist-upgrade'
didn't load anything.
===================================================================
root@robbe:~# journalctl -b1 -n40 _UID=1000
-- Logs begin at Sun 2016-10-02 17:24:21 CEST, end at Mon 2016-10-03 
20:38:04 CEST. --
Oct 02 17:24:35 robbe systemd[2339]: Starting Paths.
Oct 02 17:24:35 robbe systemd[2339]: Reached target Paths.
Oct 02 17:24:35 robbe systemd[2339]: Starting Timers.
Oct 02 17:24:35 robbe systemd[2339]: Reached target Timers.
Oct 02 17:24:35 robbe systemd[2339]: Starting Sockets.
Oct 02 17:24:35 robbe systemd[2339]: Reached target Sockets.
Oct 02 17:24:35 robbe systemd[2339]: Starting Basic System.
Oct 02 17:24:35 robbe systemd[2339]: Reached target Basic System.
Oct 02 17:24:35 robbe systemd[2339]: Starting Default.
Oct 02 17:24:35 robbe systemd[2339]: Reached target Default.
Oct 02 17:24:35 robbe systemd[2339]: Startup finished in 15ms.
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: /etc/gdm3/Xsession: 
Beginning session setup...
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: localuser:kraush being 
added to access control list
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: openConnection: connect: 
No such file or directory
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: cannot connect to brltty 
at :0
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: I: Script for uim 
started at run_im.
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: I: Script for auto 
started at run_im.
Oct 02 17:24:36 robbe /etc/gdm3/Xsession[2351]: I: Script for default 
started at run_im.
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: I: Script for uim 
started at run_im.
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: I: Script for auto 
started at run_im.
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: I: Script for default 
started at run_im.
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: gnome-session-flashback 
(3.8.1): attempting to launch gnome-session at 2016-10-02T17:24:37+0200
Oct 02 17:24:37 robbe org.a11y.Bus[2610]: Activating service 
name='org.a11y.atspi.Registry'
Oct 02 17:24:37 robbe org.a11y.Bus[2610]: Successfully activated service 
'org.a11y.atspi.Registry'
Oct 02 17:24:37 robbe org.a11y.atspi.Registry[2699]: SpiRegistry daemon 
is running with well-known name - org.a11y.atspi.Registry
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: 
gnome-session-is-accelerated: No hardware 3D support.
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: 
gnome-session-check-accelerated: Helper exited with code 256
Oct 02 17:24:38 robbe systemd[2339]: Time has been changed
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: 
gnome-session-is-accelerated: No hardware 3D support.
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
missing on display ":0".
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: 
gnome-session-check-accelerated: Helper exited with code 256
Oct 02 17:24:43 robbe /etc/gdm3/Xsession[2351]: ** (process:2351): 
WARNING **: software acceleration check failed: Child process exited 
with code 1
Oct 03 18:29:00 robbe gnome-session[2351]: ** (gnome-session-quit:2908): 
WARNING **: Failed to call logout: The name org.gnome.SessionManager was 
not provided by any .service files
===================================================================

Thanks & kind regards,
Hans


Am 03.10.2016 um 19:21 schrieb Christian Seiler:
> On 10/03/2016 06:50 PM, Hans Kraus wrote:
>> With "gui stopped" I mean the following:
>> After the boot process, instead of the graphical login screen where
>> one can select the user, enter the password and do some selections,
>> the following screen appears:
>>
>> A pic of a sad computer with the text (the first line is in bold):
>> ===================================================================
>>        Oh no! Something has gone wrong.
>> A problem occurred and the system can't recover.
>>         Please log out and try again.
>>                -----------
>>                | Log Out |
>>                -----------
>> ===================================================================
>> I get the same screen when I choose another shell (via Ctrl-Alt-F2),
>> log in as root and enter: startx.
>
> Ok, this appears to be a GNOME-specific error message.
>
> Could you restart the computer, try to log in, wait until that
> message pops up, don't close the message, switch to another console
> (Ctrl+Alt+F2) and run the following command as root?
>
> journalctl -b1 -n40 _UID=1000
>
> (Replace 1000 with your user id, you can look it via running id in
> the console as your normal user; 1000 is the default for the first
> user created by the Debian installer.)
>
> See if there's anything in that output that might be relevant here.
>
>> The /etc/apt/sources.list:
>> ===================================================================
>> root@robbe:~# cat /etc/apt/sources.list
>> # deb http://ftp.at.debian.org/debian/ wheezy main
>>
>> # deb http://backports.debian.org/debian-backports wheezy-backports non-free
>> deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free
>>
>> deb http://ftp.at.debian.org/debian/ jessie main contrib non-free
>> deb-src http://ftp.at.debian.org/debian/ jessie main contrib non-free
>>
>> deb http://security.debian.org/ jessie/updates main contrib non-free
>> deb-src http://security.debian.org/ jessie/updates main contrib non-free
>>
>> # wheezy-updates, previously known as 'volatile'
>> deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
>> deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
>>
>> deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
>> ===================================================================
>
> Side note: you have jessie-backports in there twice (first and last
> uncommented line), but that's completely harmless. Otherwise, looks
> fine.
>
> Could you run
>
> apt-get update
> apt-get dist-upgrade
>
> and see if it still wants to upgrade additional software?
>
> Also, what kernel version are you running? (Find that out via the
> command "uname -a".)
>
> Regards,
> Christian
>

[toc] | [prev] | [next] | [standalone]

#173161

> [ kernel, dist-upgrade ]

All looks fine, you seem to have an up to date Jessie system and the
only thing that was installed was the security update DSA-3684-1 of
this morning.

On 10/03/2016 08:42 PM, Hans Kraus wrote:
> Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" missing on display ":0".
> Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: gnome-session-is-accelerated: No hardware 3D support.

There's your problem: as far as I know, GNOME under Jessie only works
if you have 3D OpenGL hardware acceleration support. And apparently
your GPU is either not supported (maybe not anymore) or you don't have
the right driver loaded.

Could you post the contents of /var/log/Xorg.0.log? (It may repeat
itself, every time the X server is started, only the last one of
these repeats is sufficient.) Also, what graphics card do you have?
(You can find out via "lspci -v" as root and looking for a device
with "VGA" in the device type.) Do you have any special drivers
installed? (For example, if you have an NVIDIA card, do you have the
proprietary nvidia drivers installed?)

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#173186

Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):

> The VGA output:
> ========================================================================
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
...
> As far as I know I didn't install a special video driver. At least not
> for Jessie, and, to the best of my knowledge, not for Wheezy too.
...

Do you have xserver-xorg-video-ati, amd64-microcode and firmware-linu* 
installed? Xorg.0.log reports using the radeon driver, but your Turks may 
require the AMD driver from the ati package, and/or firmware not included in 
a default installation.

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not 
found) in Xorg.0.log would normally be a bad sign, but as you're using AMD 
video, the appearance of that message should be a logging error, not a real 
error.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#173189

On Tue 04 Oct 2016 at 14:41:11 -0400, Felix Miata wrote:

> Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):
> 
> >The VGA output:
> >========================================================================
> >01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> >[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
> ...
> >As far as I know I didn't install a special video driver. At least not
> >for Jessie, and, to the best of my knowledge, not for Wheezy too.
> ...
> 
> Do you have xserver-xorg-video-ati, amd64-microcode and firmware-linu*
> installed? Xorg.0.log reports using the radeon driver, but your Turks may
> require the AMD driver from the ati package, and/or firmware not included in
> a default installation.
> 
> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
> found) in Xorg.0.log would normally be a bad sign, but as you're using AMD
> video, the appearance of that message should be a logging error, not a real
> error.

You have highlighted

  > (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

This is an interesting line in the log.

Why should using a radeon card give such a message? What has radeon to
do with nvidia? It could be a logging error but why does it occur? xorg
has sorted out which card is present.

Incidentally, we know X comes up for the OP (gnome-session runs. Without
X it wouldn't). So this may not be the problem at all.

  glxinfo | grep render

is a good command for the OP to run. We would be interested in its output.

However, perhaps the OP could look at

  dpkg -l | grep nvidia

and purge any packages if anything nvidia related is in its output.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173201

On Tue 04 Oct 2016 at 20:55:54 +0100, Brian wrote:

> Incidentally, we know X comes up for the OP (gnome-session runs. Without
> X it wouldn't). So this may not be the problem at all.
> 
>   glxinfo | grep render
> 
> is a good command for the OP to run. We would be interested in its output.

The Radeon HD 6670/7670 appeared in 2011. It would be highly unlikely
for the output of this command not to show

  direct-rendering: Yes

As Patrick Bartek cogently asked:

 > What exactly did you do to "upgrade?"  Did you read the Jessie Release
 > Notes regarding distribution upgrading?

Probably not, so I did it for him.

   > Unlike other OpenGL drivers, the AMD FGLRX driver for
   > Radeon adapters does not support the EGL interface. As
   > such, several GNOME applications, including the core of
   > the GNOME desktop, will not start at all when this driver
   > is in use.

   > It is recommended to use the free radeon driver, which is
   > the default in jessie, instead.

(There is a strong chance that Hans Kraus is not subscribed to this list
and is not reading the list archives to monitor replies to his query,
This will be my first and only CC:)

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173211

Hi,

thanks to all. Brian is right with his opinion that I'm not subscribed
to the list. I sent a 'subscribe' to
<mailto: debian-user-REQUEST@lists.debian.org> but didn't get an answer
(or at least I didn't find it).

How do I switch drivers under Debian, especiallay from the "AMD FGLRX 
driver for Radeon adapters" to the "free radeon driver, which is the 
default in jessie"?

Kind regards,
Hans

PS: Please send any mails regarding this with a 'CC' to me.

[toc] | [prev] | [next] | [standalone]

#173214

On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:

> thanks to all. Brian is right with his opinion that I'm not subscribed
> to the list. I sent a 'subscribe' to
> <mailto: debian-user-REQUEST@lists.debian.org> but didn't get an answer
> (or at least I didn't find it).

The reply comes back to the address you subscribed from. Maybe that
wasn't hans@hanswkraus.com. But we will not dwell on that; you can sort
it out at another time.

> How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
> for Radeon adapters" to the "free radeon driver, which is the default in
> jessie"?

I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
output shows

  > Kernel driver in use: radeon

which implies otherwise. But the journalctl output doesn't look happy. 

To answer your question:

  dpkg -l | grep fglrx

Lines with "ii" indicate installed packages. Purge and see what a reboot
does.

(What does the glxinfo command give?)

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173246

Hi,

Am 05.10.2016 um 20:58 schrieb Brian:
> On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
>
>> thanks to all. Brian is right with his opinion that I'm not subscribed
>> to the list. I sent a 'subscribe' to
>> <mailto: debian-user-REQUEST@lists.debian.org> but didn't get an answer
>> (or at least I didn't find it).
>
> The reply comes back to the address you subscribed from. Maybe that
> wasn't hans@hanswkraus.com. But we will not dwell on that; you can sort
> it out at another time.
>
>> How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
>> for Radeon adapters" to the "free radeon driver, which is the default in
>> jessie"?
>
> I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
> output shows
>
>   > Kernel driver in use: radeon
>
> which implies otherwise. But the journalctl output doesn't look happy.
>
> To answer your question:
>
>   dpkg -l | grep fglrx
>
> Lines with "ii" indicate installed packages. Purge and see what a reboot
> does.

root@robbe:~# dpkg -l | grep fglrx
ii  fglrx-atieventsd 
1:15.9-4~deb8u2                      amd64        events daemon for the 
non-free ATI/AMD RadeonHD display driver
ii  fglrx-driver 
1:15.9-4~deb8u2                      amd64        non-free ATI/AMD 
RadeonHD display driver
ii  fglrx-modules-dkms 
1:15.9-4~deb8u2                      amd64        dkms module source for 
the non-free ATI/AMD RadeonHD display driver
ii  glx-alternative-fglrx                                       0.5.1 
                             amd64        allows the selection of FGLRX 
as GLX provider
ii  libfglrx:amd64 
1:15.9-4~deb8u2                      amd64        non-free ATI/AMD 
RadeonHD display driver (runtime libraries)
ii  libfglrx-amdxvba1:amd64 
1:15.9-4~deb8u2                      amd64        AMD XvBA (X-Video 
Bitstream Acceleration) backend for VA API
ii  libgl1-fglrx-glx:amd64 
1:15.9-4~deb8u2                      amd64        proprietary libGL for 
the non-free ATI/AMD RadeonHD display driver

Is it OK to purge all these?

> (What does the glxinfo command give?)
>
root@robbe:~# glxinfo
Error: unable to open display

Thanks,
Hans

[toc] | [prev] | [next] | [standalone]

#173250

On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:

> Hi,
> 
> Am 05.10.2016 um 20:58 schrieb Brian:
> >On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
> >
> >>thanks to all. Brian is right with his opinion that I'm not subscribed
> >>to the list. I sent a 'subscribe' to
> >><mailto: debian-user-REQUEST@lists.debian.org> but didn't get an answer
> >>(or at least I didn't find it).
> >
> >The reply comes back to the address you subscribed from. Maybe that
> >wasn't hans@hanswkraus.com. But we will not dwell on that; you can sort
> >it out at another time.
> >
> >>How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
> >>for Radeon adapters" to the "free radeon driver, which is the default in
> >>jessie"?
> >
> >I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
> >output shows
> >
> >  > Kernel driver in use: radeon
> >
> >which implies otherwise. But the journalctl output doesn't look happy.
> >
> >To answer your question:
> >
> >  dpkg -l | grep fglrx
> >
> >Lines with "ii" indicate installed packages. Purge and see what a reboot
> >does.
> 
> root@robbe:~# dpkg -l | grep fglrx
> ii  fglrx-atieventsd 1:15.9-4~deb8u2                      amd64
> events daemon for the non-free ATI/AMD RadeonHD display driver
> ii  fglrx-driver 1:15.9-4~deb8u2                      amd64        non-free
> ATI/AMD RadeonHD display driver
> ii  fglrx-modules-dkms 1:15.9-4~deb8u2                      amd64
> dkms module source for the non-free ATI/AMD RadeonHD display driver
> ii  glx-alternative-fglrx                                       0.5.1
> amd64        allows the selection of FGLRX as GLX provider
> ii  libfglrx:amd64 1:15.9-4~deb8u2                      amd64
> non-free ATI/AMD RadeonHD display driver (runtime libraries)
> ii  libfglrx-amdxvba1:amd64 1:15.9-4~deb8u2                      amd64
> AMD XvBA (X-Video Bitstream Acceleration) backend for VA API
> ii  libgl1-fglrx-glx:amd64 1:15.9-4~deb8u2                      amd64
> proprietary libGL for the non-free ATI/AMD RadeonHD display driver
> 
> Is it OK to purge all these?

I would say so. Whether it makes any difference or not is a different
matter. I've never used non-free video drivers. If you have an xorg.conf
in /etc/X11 I'd move it out of the way.

> >(What does the glxinfo command give?)
> >
> root@robbe:~# glxinfo
> Error: unable to open display

That is when you used a terminal. Boot into X with

  xinit -- vt$XDG_VTNR

It is not pretty but there is an xterm to type commands into. What is
the output?

-- 
Brian.

  

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web