apps crash on startup, framebuffer login not possible

If none of the more specific forums is the right place to ask

apps crash on startup, framebuffer login not possible

Postby debian_forums » 2018-08-26 20:32

I'm trying to get my head around the troubles I'm having today. Things weren't too bad yesterday...

It's on a computer running debian testing.

Some of the symptoms are:


  1. Launching a terminal is not possible. Terminals crash on start up. I have installed, and tested several terminals: xterm, xfce4-terminal, mlterm, qterminal, rxvt-unicode.
  2. Login from a framebuffer console is not possible. We provide login credentials. We are logged in for a split second. We are automatically logged out.

IIRC for 2-3 weeks, I had had some problems with Firefox-esr. It would also crash on startup. As I'm only ocassionally using it, I didn't pay much attention.

Does anyone have any idea as to what could be happening?

TIA.
debian_forums
 
Posts: 11
Joined: 2013-09-08 20:33

Re: apps crash on startup, framebuffer login not possible

Postby Head_on_a_Stick » 2018-08-26 20:45

debian_forums wrote:Launching a terminal is not possible. Terminals crash on start up. I have installed, and tested several terminals: xterm, xfce4-terminal, mlterm, qterminal, rxvt-unicode

What shows up in ~/.xsession-errors after the terminals fail?

Does the problem still occur if you switch shell?

I like mksh:
Code: Select all
# apt install mksh
cp /etc/skel.mkshrc ~
chsh -s /bin/mksh-static

Then log out & back in again to check.

Perhaps also (re)move ~/.profile to eliminate that as the cause (the original file is at /etc/skel/.profile).
User avatar
Head_on_a_Stick
 
Posts: 7906
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: apps crash on startup, framebuffer login not possible

Postby debian_forums » 2018-08-27 00:39

Thanks for your reply, Head_on_a_Stick.

Head_on_a_Stick wrote:
debian_forums wrote:Launching a terminal is not possible. Terminals crash on start up. I have installed, and tested several terminals: xterm, xfce4-terminal, mlterm, qterminal, rxvt-unicode

What shows up in ~/.xsession-errors after the terminals fail?


The following is written to ~/.xsession-errors when failing to launch xterm via XFCE's Applications > System > XTerm:

Code: Select all
xterm: error while loading shared libraries: /lib/x86_64-linux-gnu/libtinfo.so.6: unexpected reloc type 0x02000007


Head_on_a_Stick wrote:Does the problem still occur if you switch shell?

I like mksh:
Code: Select all
# apt install mksh
cp /etc/skel.mkshrc ~
chsh -s /bin/mksh-static

Then log out & back in again to check.

Perhaps also (re)move ~/.profile to eliminate that as the cause (the original file is at /etc/skel/.profile).


Switching shells feels like a good idea.

However, for some reason it seems to not like login shells.

The only way I've been able to launch a terminal is by typing either of the following into the Applications > Run Program... dialog of XFCE:

  • mlterm -e mksh
  • stterm -e mksh

Both of the following fail at launching a terminal:

  • mlterm -e -mksh
  • stterm -e -mksh
debian_forums
 
Posts: 11
Joined: 2013-09-08 20:33

Re: apps crash on startup, framebuffer login not possible

Postby Head_on_a_Stick » 2018-08-27 05:14

debian_forums wrote:
Code: Select all
xterm: error while loading shared libraries: /lib/x86_64-linux-gnu/libtinfo.so.6: unexpected reloc type 0x02000007

^ I don't like that, please show
Code: Select all
apt policy

debian_forums wrote:for some reason it seems to not like login shells

^ What does this mean?

What actually happens if you run
Code: Select all
chsh -s /bin/mksh-static

and then log out & back in again?
User avatar
Head_on_a_Stick
 
Posts: 7906
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: apps crash on startup, framebuffer login not possible

Postby debian_forums » 2018-08-27 08:18

Head_on_a_Stick wrote:
debian_forums wrote:
Code: Select all
xterm: error while loading shared libraries: /lib/x86_64-linux-gnu/libtinfo.so.6: unexpected reloc type 0x02000007

^ I don't like that, please show
Code: Select all
apt policy


Code: Select all
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 https://dl.yarnpkg.com/debian stable/main all Packages
     release o=yarn,a=stable,n=stable,l=yarn-stable,c=main,b=all
     origin dl.yarnpkg.com
 500 https://dl.yarnpkg.com/debian stable/main amd64 Packages
     release o=yarn,a=stable,n=stable,l=yarn-stable,c=main,b=amd64
     origin dl.yarnpkg.com
 100 http://http.debian.net/debian stretch-backports/main amd64 Packages
     release o=Debian Backports,a=stretch-backports,n=stretch-backports,l=Debian Backports,c=main,b=amd64
     origin http.debian.net
 500 https://repo.skype.com/deb stable/main amd64 Packages
     release o=. stable,a=stable,n=stable,l=. stable,c=main,b=amd64
     origin repo.skype.com
 500 https://debian.neo4j.org/repo stable/ Packages
     release o=repo,a=stable,n=stable,l=repo,c=
     origin debian.neo4j.org
 500 https://cli-assets.heroku.com/apt ./ Packages
     release o=Heroku,a=stable,c=
     origin cli-assets.heroku.com
 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
     release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
     origin dl.google.com
 500 https://download.docker.com/linux/debian buster/stable amd64 Packages
     release o=Docker,a=buster,l=Docker CE,c=stable,b=amd64
     origin download.docker.com
 500 http://deb.debian.org/debian testing/non-free amd64 Packages
     release o=Debian,a=testing,n=buster,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian testing/contrib amd64 Packages
     release o=Debian,a=testing,n=buster,l=Debian,c=contrib,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian testing/main amd64 Packages
     release o=Debian,a=testing,n=buster,l=Debian,c=main,b=amd64
     origin deb.debian.org
Pinned packages:


Head_on_a_Stick wrote:
debian_forums wrote:for some reason it seems to not like login shells

^ What does this mean?

What actually happens if you run
Code: Select all
chsh -s /bin/mksh-static

and then log out & back in again?


Maybe I should take a step back.

I don't know if mksh has finished installing, or if I'm able to run chsh -s /bin/mksh-static:

Code: Select all
user@x200:~ $ sudo apt-get install mksh
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  mksh
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/587 kB of archives.
After this operation, 1,371 kB of additional disk space will be used.
(Reading database ... 244117 files and directories currently installed.)
Preparing to unpack .../archives/mksh_56c-1_amd64.deb ...
Unpacking mksh (56c-1) ...
Setting up tex-common (6.09) ...
/bin/bash: error while loading shared libraries: /lib/x86_64-linux-gnu/libtinfo.so.6: unexpected reloc type 0x02000007
dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned error exit status 127
Processing triggers for man-db (2.8.4-2) ...
Setting up mksh (56c-1) ...
update-alternatives: using /bin/mksh to provide /bin/ksh (ksh) in auto mode
awk: error while loading shared libraries: /lib/x86_64-linux-gnu/libtinfo.so.6: unexpected reloc type 0x02000007
Either another instance of /usr/sbin/add-shell is running, or it was previously interrupted.
Please examine /etc/shells.tmp to see if it should be moved onto /etc/shells.
dpkg: error processing package mksh (--configure):
 installed mksh package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 tex-common
 mksh
E: Sub-process /usr/bin/dpkg returned an error code (1)
100|user@x200:~ $ chsh -s /bin/mksh-static
Password:
chsh: /bin/mksh-static is an invalid shell
debian_forums
 
Posts: 11
Joined: 2013-09-08 20:33

Re: apps crash on startup, framebuffer login not possible

Postby Head_on_a_Stick » 2018-08-27 08:20

Yeah, so testing isn't working then? :mrgreen:

I would try an "upgrade" to sid, I always found that worked (slightly) better because it gets the bug fixes (and new bugs) first.

EDIT: given that bash & dpkg both seem to be fucked, that may not be possible.

Have you considered running Debian stable instead?
User avatar
Head_on_a_Stick
 
Posts: 7906
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: apps crash on startup, framebuffer login not possible

Postby debian_forums » 2018-08-27 09:50

The libtinfo.so.6 errors seemed to have popped up out of the blue.

Why am I seeing them?
debian_forums
 
Posts: 11
Joined: 2013-09-08 20:33

Re: apps crash on startup, framebuffer login not possible

Postby Head_on_a_Stick » 2018-08-27 10:22

You may have caught a soname bump at the wrong time, do you always pay attention to APT's output? Were there any warning signs?

I don't run testing/unstable so perhaps await the reply of somebody who does.
User avatar
Head_on_a_Stick
 
Posts: 7906
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: apps crash on startup, framebuffer login not possible

Postby None1975 » 2018-08-27 13:27

Man! Don't make a FrankenDebian. Oh no! You already have it.
OS: Debian 9.4 / WM: Xmonad
Debian Wiki | DontBreakDebian, My config files in github
Linux User #607425
User avatar
None1975
 
Posts: 628
Joined: 2015-11-29 18:23
Location: Lithuania, Vilnius


Return to General Questions

Who is online

Users browsing this forum: Tharbad and 4 guests

fashionable