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

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

Debian Stretch broken !

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

Contents

  Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-03 20:50 +0200
    Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-03 21:10 +0200
      Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-04 01:20 +0200
        Partition unreadable [was: Re: Debian Stretch broken !] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-04 08:30 +0200
          Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-04 11:10 +0200
            Re: Partition unreadable Felix Miata <mrmazda@earthlink.net> - 2020-04-04 12:00 +0200
            Re: Partition unreadable [was: Re: Debian Stretch broken !] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-04 18:20 +0200
              Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-04 20:00 +0200
                Re: Partition unreadable [was: Re: Debian Stretch broken !] David Christensen <dpchrist@holgerdanske.com> - 2020-04-05 01:10 +0200
                Re: Partition unreadable [was: Re: Debian Stretch broken !] Tom Dial <tddial@comcast.net> - 2020-04-05 03:50 +0200
                  Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 15:30 +0200
                    Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 15:40 +0200
                    Re: Partition unreadable [was: Re: Debian Stretch broken !] Kent West <westk@acu.edu> - 2020-04-09 15:50 +0200
                      Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 16:40 +0200
                        Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 16:50 +0200
                          Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 20:10 +0200
                            Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 20:20 +0200
                              [SOLVED]Re: Partition unreadable [was: Re: Debian Stretch broken  !] Bernard <bdebreil@free.fr> - 2020-04-10 14:50 +0200
                        Re: Partition unreadable [was: Re: Debian Stretch broken !] Kent West <westk@acu.edu> - 2020-04-09 17:00 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:30 +0200
          Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:40 +0200
            Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 13:30 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:30 +0200
        Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-06 09:10 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 14:00 +0200
    Re: Debian Stretch broken ! Default User <hunguponcontent@gmail.com> - 2020-04-03 21:10 +0200
    Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-03 21:30 +0200
    Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-05 08:30 +0200
      Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-05 23:40 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-06 02:10 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 13:40 +0200
        Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 09:50 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 12:40 +0200
            Re: Debian Stretch broken ! Daniel Harris <mail.dharris@googlemail.com> - 2020-04-06 13:10 +0200
            Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 14:00 +0200
              Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 14:20 +0200
                Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-06 14:30 +0200

Page 2 of 2 — ← Prev page 1 [2]

#220929

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

On Sun, Apr 5, 2020 at 9:28 AM Kent West <westk@acu.edu> wrote:

>
>
> On Sun, Apr 5, 2020 at 9:23 AM Kent West <westk@acu.edu> wrote:
>
>>
>> Next I typed 'journalctl -xb' to view system logs : a dozen of pages
>>> which I will shoot later, one thing I have noticed in it all, printed in
>>> red characters :
>>>
>>> EXT4-fs (sda2): unable to read superblock
>>>
>>> this repeated three times !
>>>
>>>
>> This looks a bit worrisome, but it may not actually be; it depends on
>> what device is at sda2 (it might be a second (unformatted, unused) hard
>> drive, or a USB thumb drive, or a CD/DVD drive, or ...).
>>
>
> No it can't be; I wasn't thinking straight. This is a second partition,
> not a second drive.
>
> This is almost certainly your problem. The next question is if it's a
> hardware, formatting, or mounting problem. I'd run "cfdisk" and see what
> that shows me.
>
>
> No, again, I think I've been mistaken. Seeing a different thread dealing
with this same problem, I realize that /dev/sda2 is likely the "container"
for extended partitions; trying to mount it would likely result in an
error; so I'm back to thinking I'd put my worry about this error message
aside for now, and see what "cfdisk" or some equivalent, like "fdisk -l
/dev/sda", says.


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

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

#220984

Le 05/04/2020 16:35, Kent West a écrit :
>
>

>
> No, again, I think I've been mistaken. Seeing a different thread dealing
> with this same problem, I realize that /dev/sda2 is likely the
> "container" for extended partitions; trying to mount it would likely
> result in an error; so I'm back to thinking I'd put my worry about this
> error message aside for now, and see what "cfdisk" or some equivalent,
> like "fdisk -l /dev/sda", says.
>

The screen results of

# fdisk -l /dev/sda

and

# cfdisk

are on the follong screenshots :

http://bdebreil.free.fr/IMG_0927.jpg

and

http://bdebreil.free.fr/IMG_0928.jpg

Bernard

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

#220928

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

Things are looking a bit more promising now...


On Fri, Apr 3, 2020 at 6:14 PM Bernard <bdebreil@free.fr> wrote:

>
>
> Le 03/04/2020 21:05, Kent West a écrit :
> >
> >
> > On Fri, Apr 3, 2020 at 1:41 PM Bernard <bdebreil@free.fr
> > <mailto:bdebreil@free.fr>> wrote:
> >
> >
> >     Having done some minor resettings on alsamixer with no results, I
> >     thought I had to reboot.
> >
> >     But : "Oh no, something has gone wrong..."
> >
> >     So, I am writing this message from my other laptop running Ubuntu
> 14.04
> >
> >     I tried to reboot in rescue mode, but I don't know what to do from
> >     there. 'startx' says that it doesn't have the proper files to launch
> >     startx as root.
> >
> >     login
> >     bd
> >
> >     says : wrong login (doesn't even ask a pswd)
> >
> >
> > It's unclear how far you're getting.
> >
> > Can you boot normally and get to a login prompt on a text-only screen?
> >
> > --
> > Kent
> >
> Thanks for your reply. To get login prompt and text screen, I had to
> take pictures with a camera, since the caracters are so small. Reading
> back those images, I will say this :
>


The pictures help. I see from the second picture that these are from a
"rescue boot"; what happens with just a normal boot?



> upon booting, a number of screen messages do appear and scroll down
> fast. I could only see that 'OK' was on most or all of them. In the end,
> a screen with smaller characters appear for 2-3 sec, that I have
> photographied.It has two lines as follows :
>
> /dev/sda1: clean, 408719/60530688 files, 116865639/242103552 blocks
> [    8.436046] nouveau 0000:01:00.0: priv: HUB0: 085014 ffffffff (1e70820b)
>
> Those two lines only appear for 2-3 sec, so I had a hard time to
> photography them on the screen, and I am just coping them by hand, Links
> for photos are as follows :
>
> http://bdebreil.free.fr/IMG_0900.jpg
> http://bdebreil.free.fr/IMG_0901.jpg
> http://bdebreil.free.fr/IMG_0902.jpg
> http://bdebreil.free.fr/IMG_0903.jpg
> http://bdebreil.free.fr/IMG_0904.jpg
>
> After those 2-3 sec, another screen appears saying (translated from
> French to English)
>
> "Oops, something went wront. A problem has occured and the system cannot
> recuperate. Please disconnect and try again"
>
> Countless trials have all lead to the same behaviour.
>
> Now, if I reboot on rescue mode, a lot of fast moving messages do
> appear, I only could see that most or all of them bore the mention 'OK',
> as said before. In the end, smaller characters do remain on screen,
> waiting till I submit the root pasword. Then :
>
> You are in rescue mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctlreboot" to reboot, "systemctldefault" or ?D to
> boot into default mode
>
> Give the superuser pswd (or press CTRL-D) to continue : [    9.315865]
> [TTM] Zone kernel: A
>
> Available graphic memory: 2097152 kiB
>
> [   9.316077 [TTM] Initializing DMA pool allocator
> [ nouveau ..... DRM:
> ......
> etc ...
>
> When typing 'ls -l' home directories do not appear (see pictures)
>


Try "ls -l /"


Next I typed 'journalctl -xb' to view system logs : a dozen of pages
> which I will shoot later, one thing I have noticed in it all, printed in
> red characters :
>
> EXT4-fs (sda2): unable to read superblock
>
> this repeated three times !
>
>
This looks a bit worrisome, but it may not actually be; it depends on what
device is at sda2 (it might be a second (unformatted, unused) hard drive,
or a USB thumb drive, or a CD/DVD drive, or ...). Without more context,
it's hard to say much at this point. I'd hold off on worrying about it just
yet. As mentioned above, I'm mostly interesting in knowing what happens
when you do a normal boot.


Thanks in advance for your comments and advises.
>
> Bernard
>
>
>
>
>
>
>

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

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

#220960

Bernard composed on 2020-04-04 01:13 (UTC+0200):

> http://bdebreil.free.fr/IMG_0901.jpg
[quote]
You are in rescue mode. After logging in, type "journalctl -xb" to view
system logs[/quote]

Did you do this? It should provide clues what needs to be done and/or what is
going wrong. If journalctl -xb produces more than one screenful, it's the last
screen or two or three that would be most important.

Please report what video card you have by doing this:

	lspci -nnk | grep -iA4 VGA

The important part of the output fills in these four blanks:

	[10DE:____]
-- 
Evolution as taught in public schools is religion, not science.

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

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

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

#220992

Le 06/04/2020 09:08, Felix Miata a écrit :

> [quote]
> You are in rescue mode. After logging in, type "journalctl -xb" to view
> system logs[/quote]
>
> Did you do this?

I did it a few posts ago ; in the end of it were three identical red 
lines saying that there was a bad block on sda2... But, at this time I 
was in rescue mode, as the normal boot had not gone to its end and that 
I had had to reboot on rescue mode.

Ever since I disabled gdm / gnome as Andrei had suggested, I have been 
able to carry the boot process to its end, even though it is only on 
text mode.

I then ran again the journalctl -xb test, which gave something else than 
before. I was able to copy it to an external drive as a text file, which 
I have put at this url for you to download :

http://bdebreil.free.fr/journalctl.txt

  It should provide clues what needs to be done and/or what is
> going wrong. If journalctl -xb produces more than one screenful, it's the last
> screen or two or three that would be most important.
>
> Please report what video card you have by doing this:
>
> 	lspci -nnk | grep -iA4 VGA
>
> The important part of the output fills in these four blanks:
>
> 	[10DE:____]

Those four blanks are as follows :

(10DE:)128B for the video

(10DE:)0e0F for the audio

The whole output of
lspci -nnk | grep -iA4 VGA

has been saved as a text file and can be downloaded at

http://bdebreil.free.fr/lspcinnkvga.txt

Bernard

>

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

#220839

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

On Fri, Apr 3, 2020, 14:41 Bernard <bdebreil@free.fr> wrote:

> Hi to Everyone,
> Having done some minor resettings on alsamixer with no results, I
> thought I had to reboot.
>
> But : "Oh no, something has gone wrong..."
>
> So, I am writing this message from my other laptop running Ubuntu 14.04
>
> I tried to reboot in rescue mode, but I don't know what to do from
> there. 'startx' says that it doesn't have the proper files to launch
> startx as root.
>
> login
> bd
>
> says : wrong login (doesn't even ask a pswd)
>
> I remember a few years back on older versions, I had used 'System Rescue
> CD', but this said CD, provided that I find it, would probably no work
> on this system
>
>
> Thanks in advance for your help so that I can expect to boot my system
> without loss of data
>
> By the way: not only did I reset alsamixer prior to rebooting, also I
> had accepted an automatic system upgrade this morning.
>
> Bernard
>



Hi, Bernard.

I can't really help you with your specific current problem, but since you
mentioned SystemRescueCD, I just wanted to note that a new version,
SystemRescueCD 6.1.2, just came out a few days ago, 2020-03-29.

It is easy to write the .iso to a usb  thumb drive and run it from there.

The website, including instructions, is:

http://www.system-rescue-cd.org

Good luck!

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

#220840

Bernard composed on 2020-04-03 20:41 (UTC+0200):

> "Oh no, something has gone wrong..."
That message is issued when GDM cannot start. How to fix I don't know, as I never
use GDM, but when that happens you should be able to switch to any of the vttys
GDM doesn't run on to find a text login prompt. If you can, a fix might be as
simple as:

	apt update
	apt install -f

to finish an upgrade that didn't actually.
-- 
Evolution as taught in public schools is religion, not science.

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

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

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

#220906

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

On Vi, 03 apr 20, 20:41:06, Bernard wrote:
> Hi to Everyone,
> Having done some minor resettings on alsamixer with no results, I thought I
> had to reboot.
> 
> But : "Oh no, something has gone wrong..."
> 
> So, I am writing this message from my other laptop running Ubuntu 14.04
> 
> I tried to reboot in rescue mode, but I don't know what to do from there.

Apparently I missed this on first read, and though you are being dropped 
to the rescue console.

> 'startx' says that it doesn't have the proper files to launch startx as
> root.

Starting X as root is not recommended. I would suggest instead you run 
(as root):

    apt install xinit
    systemctl set-default multi-user.target 

and then boot "normally" (this time in text mode).

Log in with your normal user and try running 'startx' from the console. 
In case it stops with some error messages we need those.

To revert to graphical login you must run (as root):

    systemctl set-default graphical.target


Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#220950

Le 05/04/2020 08:24, Andrei POPESCU a écrit :
> On Vi, 03 apr 20, 20:41:06, Bernard wrote:
>> Hi to Everyone,
>> Having done some minor resettings on alsamixer with no results, I thought I
>> had to reboot.
>>
>> But : "Oh no, something has gone wrong..."
>>
....................

> Apparently I missed this on first read, and though you are being dropped
> to the rescue console.
>

> Starting X as root is not recommended. I would suggest instead you run
> (as root):
>
>      apt install xinit
>      systemctl set-default multi-user.target
>
> and then boot "normally" (this time in text mode).
>
> Log in with your normal user and try running 'startx' from the console.
> In case it stops with some error messages we need those.

The on screen results of such trials have been photographied and are 
available at the urls below :

http://bdebreil.free.fr/IMG_0923.jpg

http://bdebreil.free.fr/IMG_0925.jpg

http://bdebreil.free.fr/IMG_0926.jpg

This includes the results of the 'startx' trials.

Doing this, I have been able to login as user, which confirms that 
'/home/user' was still available. A random check confirmed that most or 
  likely all files were still there on /home/bd

a 'df' test still didn't show any

'/dev/sda2'

  partition, but, as mentioned before, I doubt if there was any such 
partition before ; in my other computers I have none, if I except the 
more than ten years old systems. Nice to understand that, without such 
partition, the /home/bd is available

I have been able to access

/var/log/messages

  and other similar files, and to copy them onto an USB External Hard 
drive. These hold tens of thousands of lines, and I don't know which 
keywords to search for, but these said files are available upon request, 
or I can search them if someone suggests keywords.

>
> To revert to graphical login you must run (as root):
>
>      systemctl set-default graphical.target
>



Best regards,

Bernard

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

#220953

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

On Sun, Apr 5, 2020 at 4:36 PM Bernard <bdebreil@free.fr> wrote:

>
>
> Le 05/04/2020 08:24, Andrei POPESCU a écrit :
> > On Vi, 03 apr 20, 20:41:06, Bernard wrote:
>


> >> But : "Oh no, something has gone wrong..."
> >>
> ....................
> >
> > and then boot "normally" (this time in text mode).
> >
> > Log in with your normal user and try running 'startx' from the console.
> > In case it stops with some error messages we need those.
>
> The on screen results of such trials have been photographied and are
> available at the urls below :
>
>
> http://bdebreil.free.fr/IMG_0925.jpg
>
> http://bdebreil.free.fr/IMG_0926.jpg
>

You can log in as a normal user! Excellent!

Can you ping something by address? by name?

e.g.
ping 8.8.8.8
ping google.com

(Just trying to see how "normal" your system is.)

Maybe even install links2 and see if you can web-browse from the terminal.
$ sudo aptitude install links2
$ links2 slashdot.org
'q' to quit

Maybe install a simpler X system, like XFCE:

$ sudo tasksel

then try "startx'.


Any success? Any new errors/symptoms/insights?

-- 
Kent

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

#220987

Le 06/04/2020 02:07, Kent West a écrit :
>
>
>
> You can log in as a normal user! Excellent!
>
> Can you ping something by address? by name?
>
> e.g.
> ping 8.8.8.8
> ping google.com <http://google.com>
>
> (Just trying to see how "normal" your system is.)

ping 8.8.8.8 displays things related to time or something of the sort :

.................
64 bytes from par21s03-in....

ping google.com
seems to work too

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

#220963

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

On Du, 05 apr 20, 23:35:45, Bernard wrote:
> 
> Le 05/04/2020 08:24, Andrei POPESCU a écrit :
> > 
> > Log in with your normal user and try running 'startx' from the console.
> > In case it stops with some error messages we need those.
> 
> The on screen results of such trials have been photographied and are
> available at the urls below :
> 
> http://bdebreil.free.fr/IMG_0923.jpg
> 
> http://bdebreil.free.fr/IMG_0925.jpg
> 
> http://bdebreil.free.fr/IMG_0926.jpg
> 
> This includes the results of the 'startx' trials.

Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should 
be small enough to be accepted by the list.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#220977

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

Le 06/04/2020 09:46, Andrei POPESCU a écrit :
> On Du, 05 apr 20, 23:35:45, Bernard wrote:
>>
>> Le 05/04/2020 08:24, Andrei POPESCU a écrit :
>>>
>>> Log in with your normal user and try running 'startx' from the console.
>>> In case it stops with some error messages we need those.
>>
>> The on screen results of such trials have been photographied and are
>> available at the urls below :
>>
>> http://bdebreil.free.fr/IMG_0923.jpg
>>
>> http://bdebreil.free.fr/IMG_0925.jpg
>>
>> http://bdebreil.free.fr/IMG_0926.jpg
>>
>> This includes the results of the 'startx' trials.
>
> Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should
> be small enough to be accepted by the list.
>
> Kind regards,
> Andrei
>

Here is the file.

Bernard

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

#220983

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

What windows manager are you using.  That has not been removed by mistake
has it?

On Mon, Apr 6, 2020 at 11:30 AM Bernard <bdebreil@free.fr> wrote:

>
>
> Le 06/04/2020 09:46, Andrei POPESCU a écrit :
> > On Du, 05 apr 20, 23:35:45, Bernard wrote:
> >>
> >> Le 05/04/2020 08:24, Andrei POPESCU a écrit :
> >>>
> >>> Log in with your normal user and try running 'startx' from the console.
> >>> In case it stops with some error messages we need those.
> >>
> >> The on screen results of such trials have been photographied and are
> >> available at the urls below :
> >>
> >> http://bdebreil.free.fr/IMG_0923.jpg
> >>
> >> http://bdebreil.free.fr/IMG_0925.jpg
> >>
> >> http://bdebreil.free.fr/IMG_0926.jpg
> >>
> >> This includes the results of the 'startx' trials.
> >
> > Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should
> > be small enough to be accepted by the list.
> >
> > Kind regards,
> > Andrei
> >
>
> Here is the file.
>
> Bernard
>

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

#220993

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

On Lu, 06 apr 20, 12:30:06, Bernard wrote:
> Le 06/04/2020 09:46, Andrei POPESCU a écrit :
> > 
> > Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should
> > be small enough to be accepted by the list.
> 
> Here is the file.
> 
> Bernard

214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object file: file or directory)
214] (EE) AIGLX: reverting to software rendering
214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Nole or directory)
[ 27640.214] (EE) GLX: could not load software renderer

It seems like you are missing libgl1-mesa-dri, possibly other packages 
as well. Try running:

    apt install -f

Do read carefully what it proposes to do. If it tries to remove 
something that seems important stop and post the output here.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#220994

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

On Lu, 06 apr 20, 14:51:18, Andrei POPESCU wrote:
> On Lu, 06 apr 20, 12:30:06, Bernard wrote:
> > Le 06/04/2020 09:46, Andrei POPESCU a écrit :
> > > 
> > > Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should
> > > be small enough to be accepted by the list.
> > 
> > Here is the file.
> > 
> > Bernard
> 
> 214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object file: file or directory)
> 214] (EE) AIGLX: reverting to software rendering
> 214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Nole or directory)
> [ 27640.214] (EE) GLX: could not load software renderer
> 
> It seems like you are missing libgl1-mesa-dri, possibly other packages 
> as well. Try running:
> 
>     apt install -f
> 
> Do read carefully what it proposes to do. If it tries to remove 
> something that seems important stop and post the output here.

Forgot to mention, if it's successful try

    systemctl isolate graphical

to try to get back to graphical mode.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#220995

Andrei POPESCU composed on 2020-04-06 15:12 (UTC+0300):

>> 214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object file: file or directory)
>> 214] (EE) AIGLX: reverting to software rendering
>> 214] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Nole or directory)
>> [ 27640.214] (EE) GLX: could not load software renderer
 
>> It seems like you are missing libgl1-mesa-dri, possibly other packages 
>> as well. Try running:
 
>>     apt install -f
 
>> Do read carefully what it proposes to do. If it tries to remove 
>> something that seems important stop and post the output here.
 
> Forgot to mention, if it's successful try
 
>     systemctl isolate graphical
 
> to try to get back to graphical mode.

Based upon his journal I doubt that will produce fruit:

-- L'unité (unit) sys-fs-fuse-connections.mount a terminé son démarrage, avec le résultat done.
avril 05 15:23:03 Debian-Stretch gnome-session[1555]: gnome-session-binary[1555]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 15:23:03 Debian-Stretch gnome-session-binary[1555]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 15:23:03 Debian-Stretch gnome-session[1555]: Unable to init server: Could not connect: Connection refused
avril 05 15:23:03 Debian-Stretch org.a11y.atspi.Registry[1603]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
avril 05 15:23:03 Debian-Stretch org.a11y.atspi.Registry[1603]:       after 21 requests (19 known processed) with 0 events remaining.
avril 05 15:23:03 Debian-Stretch kernel: gnome-session-f[1632]: segfault at 0 ip 00007f69bf104e19 sp 00007fff91eb59f0 error 4 in libgtk-3.so.0.2200.11[7f69bee22000+700000]
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done. avril 05 15:25:14 Debian-Stretch gnome-session[1725]: gnome-session-binary[1725]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1 avril 05 15:25:14 Debian-Stretch gnome-session-binary[1725]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1 avril 05 15:25:14 Debian-Stretch gnome-session[1725]: Unable to init server: Could not connect: Connection refused avril 05 15:25:14 Debian-Stretch org.a11y.atspi.Registry[1773]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" avril 05 15:25:14 Debian-Stretch org.a11y.atspi.Registry[1773]: after 21 requests (19 known processed) with 0 events remaining. avril 05 15:25:14 Debian-Stretch kernel: gnome-session-f[1796]: segfault at 0 ip 00007f0ea3bd3e19 sp 00007ffe2ba35d60 error 4 in libgtk-3.so.0.2200.11[7f0ea38f1000+700000] 
avril 05 22:53:50 Debian-Stretch su[5271]: pam_unix(su:session): session closed for user root
avril 05 22:53:54 Debian-Stretch at-spi-bus-launcher[1768]: Activating service name='org.a11y.atspi.Registry'
avril 05 22:53:54 Debian-Stretch at-spi-bus-launcher[1768]: Successfully activated service 'org.a11y.atspi.Registry'
avril 05 22:53:54 Debian-Stretch org.a11y.atspi.Registry[1773]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
avril 05 22:53:54 Debian-Stretch gnome-session[5334]: gnome-session-binary[5334]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 22:53:54 Debian-Stretch gnome-session-binary[5334]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 22:53:54 Debian-Stretch gnome-session[5334]: Unable to init server: Could not connect: Connection refused
avril 05 22:53:54 Debian-Stretch org.a11y.atspi.Registry[1773]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
avril 05 22:53:54 Debian-Stretch org.a11y.atspi.Registry[1773]:       after 21 requests (19 known processed) with 0 events remaining.
avril 05 22:53:54 Debian-Stretch kernel: gnome-session-f[5385]: segfault at 0 ip 00007f2f59e2be19 sp 00007ffd67d841e0 error 4 in libgtk-3.so.0.2200.11[7f2f59b49000+700000]
avril 05 22:58:02 Debian-Stretch at-spi-bus-launcher[1768]: Activating service name='org.a11y.atspi.Registry'
avril 05 22:58:02 Debian-Stretch at-spi-bus-launcher[1768]: Successfully activated service 'org.a11y.atspi.Registry'
avril 05 22:58:02 Debian-Stretch org.a11y.atspi.Registry[1773]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
avril 05 22:58:02 Debian-Stretch gnome-session[5458]: gnome-session-binary[5458]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 22:58:02 Debian-Stretch gnome-session-binary[5458]: WARNING: software acceleration check failed: Le processus fils s'est terminé avec le code 1
avril 05 22:58:02 Debian-Stretch gnome-session[5458]: Unable to init server: Could not connect: Connection refused
avril 05 22:58:02 Debian-Stretch org.a11y.atspi.Registry[1773]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
avril 05 22:58:02 Debian-Stretch org.a11y.atspi.Registry[1773]:       after 21 requests (19 known processed) with 0 events remaining.
avril 05 22:58:02 Debian-Stretch kernel: gnome-session-f[5509]: segfault at 0 ip 00007fe4f8fe6e19 sp 00007ffe051ca140 error 4 in libgtk-3.so.0.2200.11[7fe4f8d04000+700000]
-- 
Evolution as taught in public schools is religion, not science.

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

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

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web