OpenBOX [solved] can't connect to LXDE anymore with a standard user

bortzy

Member


Messages: 27

Hello everybody.

Since Wednesday, I can't login to LXDE anymore with a standard user: a black screen is shown: "starting openbox session".
With the root user, the connection is possible.

In /var/log/messages the message is:
Code:
Apr  8 12:45:22 bortzy ntpd[891]: ntpd 4.2.8p12-a (1): Starting
Apr  8 12:45:22 bortzy ntpd[892]: pid file /var/db/ntp/ntpd.pid: Permission denied
Apr  8 12:45:22 bortzy ntpd[892]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature
Apr  8 12:45:22 bortzy ntpd[892]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2017-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Apr  8 12:45:22 bortzy ntpd[892]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired less than 467 days ago
Apr  8 12:45:23 bortzy dbus[805]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Apr  8 12:45:29 bortzy dbus[805]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
Apr  8 12:45:29 bortzy dbus[805]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Apr  8 12:45:31 bortzy root[1006]: /etc/rc: WARNING: failed precmd routine for sshd
Apr  8 12:45:56 bortzy console-kit-daemon[826]: WARNING: Error waiting for native console 9 activation: Inappropriate ioctl for device
It is not a hardware issue as:
- using another VGA cable has the same effect
- using another screen has the same effect

Is there a lxsession maximum number of session or something like this?

~/.cache/openbox/openbox.log is empty
./.cache/lxsession/LXDE/run.log has errors:
Code:
cat ./.cache/lxsession/LXDE/run.log
** Message: 12:45:44.686: environement.vala:58: Exporting primary_variable
** Message: 12:45:44.686: environement.vala:59: desktop_environnement XDG_CURRENT_DESKTOP
** Message: 12:45:44.686: environement.vala:150: confir_dirs is null, export : /usr/local/etc/xdg
** Message: 12:45:44.686: environement.vala:184: Exporting XDG_CONFIG_DIRS
** Message: 12:45:44.686: environement.vala:191: data_dirs is null, export : /usr/local/share
** Message: 12:45:44.686: environement.vala:225: Exporting XDG_DATA_DIRS
** Message: 12:45:44.705: utils.vala:68: User config used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.705: utils.vala:89: Final file used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����iGtk/ColorScheme���� dans le groupe ����GTK����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����windows_manager/session���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����windows_manager/extras���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����panel/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����dock/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����file_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����desktop_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����launcher_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����composite_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����im1/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����im2/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����widget1/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����notification/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����keybindings/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����im_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����screensaver/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����power_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����audio_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����workspace_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����screenshot_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����message_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����upgrade_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����updates_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����updates_manager/timeout���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����crash_manager/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����crash_manager/dev_mode���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����crash_manager/timeout���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����upstart_user_session���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����proxy_manager/http���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����a11y/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����xrandr/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����network_gui/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����webbrowser/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����email/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����pdf_reader/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����video_player/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����audio_player/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����images_display/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����text_editor/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����archive/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����charmap/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����calculator/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����spreadsheet/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����bittorent/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����document/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����webcam/command���� dans le groupe ����Session����
** Message: 12:45:44.767: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����burn/command���� dans le groupe ����Session����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����notes/command���� dans le groupe ����Session����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����disk_utility/command���� dans le groupe ����Session����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����tasks/command���� dans le groupe ����Session����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s n���a pas de groupe ����Keymap����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����laptop_mode���� dans le groupe ����State����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����gnome���� dans le groupe ����Dbus����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����type���� dans le groupe ����Environment����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����ubuntu_menuproxy���� dans le groupe ����Environment����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����toolkit_integration���� dans le groupe ����Environment����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����gtk/overlay_scrollbar_disable���� dans le groupe ����Environment����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����qt/force_theme���� dans le groupe ����Environment����
** Message: 12:45:44.768: settings.vala:540: Le fichier de cl��s ne contient pas de cl�� ����qt/platform���� dans le groupe ����Environment����
** Message: 12:45:44.783: settings.vala:462: Monitoring: /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.783: settings.vala:466: Desktop file is already in config home, do nothing
** Message: 12:45:44.783: settings.vala:373: Settings default for Session, launcher_manager, command : lxpanelctl
** Message: 12:45:44.783: environement.vala:79: Exporting variable
** Message: 12:45:44.783: environement.vala:80: desktop_environnement XDG_CURRENT_DESKTOP
** Message: 12:45:44.783: environement.vala:177: custom_config :
** Message: 12:45:44.783: environement.vala:178: config_dirs :/usr/local/etc/xdg
** Message: 12:45:44.783: environement.vala:179: confir_dirs not null, export : /usr/local/etc/xdg
** Message: 12:45:44.783: environement.vala:184: Exporting XDG_CONFIG_DIRS
** Message: 12:45:44.783: environement.vala:218: custom_data :
** Message: 12:45:44.783: environement.vala:219: data_dirs :/usr/local/share
** Message: 12:45:44.783: environement.vala:220: data_dirs not null, export : /usr/local/share
** Message: 12:45:44.783: environement.vala:225: Exporting XDG_DATA_DIRS
** Message: 12:45:44.783: utils.vala:68: User config used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.783: utils.vala:89: Final file used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.783: environement.vala:254: No entry in [Environment_variable]. Le fichier de cl��s n���a pas de groupe ����Environment_variable����
** Message: 12:45:44.813: utils.vala:79: Config system location : /usr/local/etc/xdg/lxsession/LXDE
xprop:  no such property "_NET_NUMBER_OF_DESKTOPS"
xprop:  no such property "_NET_DESKTOP_NAMES"
** Message: 12:45:44.862: utils.vala:85: System system path location : /usr/local/etc/xdg/lxsession/LXDE/conffiles.conf
** Message: 12:45:44.862: utils.vala:89: Final file used : /usr/local/etc/xdg/lxsession/LXDE/conffiles.conf
** Message: 12:45:44.863: options.vala:164: Activate xsettings_manager build-in
** Message: 12:45:44.863: utils.vala:68: User config used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:44.863: utils.vala:89: Final file used : /home/cyril/.config/lxsession/LXDE/desktop.conf
** Message: 12:45:45.293: app.vala:721: polkit separate
** Message: 12:45:45.294: app.vala:721: polkit separate
** Message: 12:45:45.359: app.vala:76: Launching lxpolkit
** Message: 12:45:45.359: utils.vala:68: User config used : /home/cyril/.config/lxsession/LXDE/autostart
** Message: 12:45:45.359: utils.vala:89: Final file used : /home/cyril/.config/lxsession/LXDE/autostart
** Message: 12:45:45.359: autostart.vala:42: Autostart path : /home/cyril/.config/lxsession/LXDE/autostart
** Message: 12:45:45.529: app.vala:76: Launching lxpanel
** Message: 12:45:45.678: app.vala:76: Launching pcmanfm
** Message: 12:45:45.785: app.vala:76: Launching xscreensaver
** Message: 12:45:45.867: options.vala:110: Create Option Clipboard
** Message: 12:45:45.867: options.vala:44: Options - Launch command lxclipboard
** Message: 12:45:46.013: main.vala:442: Check keymap_mode (null)
** Message: 12:45:46.115: app.vala:76: Launching /usr/bin/ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-Mh5FRDxNcI52/agent.1156; export SSH_AUTH_SOCK;
SSH_AGENT_PID=1157; export SSH_AGENT_PID;
echo Agent pid 1157;
xrandr: Failed to get size of gamma for output default
pcmanfm: Fatal IO error 4 (Interrupted system call) on X server unix:0.0.
The last message is not very sympatic... It seems that pcmanfm wants to start automatically.

My FreeBSD version: Kernel: 12.0-RELEASE-p3


Can anybody help me please?
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Trying to debug the lxsession to see what is wrong:
Code:
truss -p <lxsession pid>
recvmsg(4,0x7fffffffe6f8,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(4,0x7fffffffe718,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe708,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe728,0)             ERR#35 'Resource temporarily unavailable'
poll({ 4/POLLIN 5/POLLIN 11/POLLIN },3,-1)     = 1 (0x1)
recvmsg(11,{NULL,0,[{"\^P\0\^[\0M\^C\0\0\M-;\^E\240\^A"...,4096}],1,{},0,0},0) = 32 (0x20)
recvmsg(11,0x7fffffffe708,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,{NULL,0,[{"\^V\0\^[\0M\^C\0\0\M-;\^E\240\^A"...,4096}],1,{},0,0},0) = 96 (0x60)
recvmsg(11,0x7fffffffe708,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe728,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe628,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe648,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(4,0x7fffffffe6f8,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(4,0x7fffffffe718,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe708,0)             ERR#35 'Resource temporarily unavailable'
recvmsg(11,0x7fffffffe728,0)             ERR#35 'Resource temporarily unavailable'
poll({ 4/POLLIN 5/POLLIN 11/POLLIN },3,-1)     = 1 (0x1)
...
Same message from the dbus-launch process, lxtoolkit, lxpanel, pcmanfm, etc.

From a text console, I try:
Code:
export DISPLAY=:0.0
startlxde
--> still hangs
/usr/local/bin/lxsession -s LXDE -e LXDE                     

** Message: 16:56:01.235: main.vala:102: Session is LXDE                       
** Message: 16:56:01.235: main.vala:103: DE is LXDE                             
** Message: 16:56:26.278: main.vala:134: log directory: /home/cyril/.cache/lxsession/LXDE             
** Message: 16:56:26.279: main.vala:135: log path: /home/cyril/.cache/lxsession/LXDE/run.log
it works but, as you can see with the timestamps, the start is very very long.

What's wrong with my system?
How can I resolve the 'Resource temporarily unavailable' message and from where it comes?

Thanks for your help.
 

bookwormep

Well-Known Member

Reaction score: 145
Messages: 273

Just a suggestion ( I don't use LXDE) but, have you installed: misc/lxde-common? Reading other articles with similar problems, one solution was this.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Thanks for your help bookwormep.

Yes:
Code:
pkg info lxde*
lxde-common-0.99.2_1
lxde-icon-theme-0.5.1
lxde-meta-1.0_8
What is strange:
- I have installed no new package except gtk-murrine* (trying to remove it, don't solve anything)
- it was working since Wednesday
- it works with a start lxsession from a console text but the start step is long (~30s)
in this case, errors in /var/log/messages is similar but with console 1 instead of 9:
console-kit-daemon[818]: WARNING: Error waiting for native console 1 activation: Inappropriate ioctl for device

I suspect something becoming old (MIT cookie?) or, as truss shown, an unavailable resource (dbus?)
But how to find it?
What resource uses lxsession?
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 7,680
Messages: 30,598

There are more issues:
Code:
Apr  8 12:45:31 bortzy root[1006]: /etc/rc: WARNING: failed precmd routine for sshd
Apr  8 12:45:56 bortzy console-kit-daemon[826]: WARNING: Error waiting for native console 9 activation: Inappropriate ioctl for device
Those don't look good either. I suspect LXDE not working is a symptom of a deeper issue.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

This may indicate some problems to access to /var
I use ZFS.
How can I check integrity of my disk?
And I can write to /var/tmp with my standard user but not in /var because of the permissions (this is normal).

I suspect LXDE not working is a symptom of a deeper issue.
That's true as I can start it manually from a console text.
And that's why I need help from you to find the original reason.

From my last investigations:
- trying to reinstall lxde* packages change nothing
- tying to reinstall slim change nothing
- from a text console, running xprop -root -remove _NET_NUMBER_OF_DESKTOPS -remove _NET_DESKTOP_NAMES -remove _NET_CURRENT_DESKTOP starts the session but with no pcmanfm (so I have no desktop)
This command comes from /usr/local/bin/startlxde.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 7,680
Messages: 30,598

Lets start from the beginning, what's in /etc/rc.conf and /etc/ttys?
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Thanks for your help SirDice.

Code:
cat /etc/rc.conf
hostname="bortzy.freebsd.org"
keymap="fr.acc"
ifconfig_em0=dhcp
defaultrouter=""
sshd_enable=yes

# not needed for an USB mouse
# moused_enable=yes

ntpd_enable=yes
powerd_enable=yes

# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev=auto
zfs_enable=yes
ntpd_sync_on_start=yes
kld_list=smbus
fsck_y_enable=yes

# for slim
dbus_enable=yes
hald_enable=yes
# don't start slim in /etc/ttys!
slim_enable=yes
#lightdm_enable=yes

# enable CUPS
cupsd_enable=yes

# for printers
lpd_enable=yes

# clear /tmp
clear_tmp_enable=yes
Code:
#
<<<<<<< current version
=======
# $FreeBSD: releng/12.0/sbin/init/ttys.amd64 338454 2018-09-04 15:48:13Z brd $
>>>>>>> 12.0-RELEASE
#    @(#)ttys    5.1 (Berkeley) 4/17/89
#
# This file specifies various information about terminals on the system.
# It is used by several different programs.  Common entries for the
# various columns include:
#
# name  The name of the terminal device.
#
# getty The program to start running on the terminal.  Typically a
#       getty program, as the name implies.  Other common entries
#       include none, when no getty is needed, and xdm, to start the
#       X Window System.
#
# type The initial terminal type for this port.  For hardwired
#      terminal lines, this will contain the type of terminal used.
#      For virtual consoles, the correct type is typically xterm.
#      Other common values include dialup for incoming modem ports, and
#      unknown when the terminal type cannot be predetermined.
#
# status Must be on or off.  If on, init will run the getty program on
#        the specified port.  If the word "secure" appears, this tty
#        allows root login.
#
# name    getty                type    status        comments
#
# If console is marked "insecure", then init will ask for the root password
# when going to single-user mode.
console    none                unknown    off secure
#
ttyv0    "/usr/libexec/getty Pc"        xterm    onifexists secure
# Virtual terminals
ttyv1    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv2    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv3    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv4    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv5    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv6    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv7    "/usr/libexec/getty Pc"        xterm    onifexists secure
# don't start slim this way: bug with no-root user
#ttyv8   "/usr/local/bin/slim"        xterm   on  secure
# to use xdm instead of slim
ttyv8    "/usr/local/bin/xdm -nodaemon"    xterm    off secure
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyu0    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu1    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu2    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu3    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
# Dumb console
dcons    "/usr/libexec/getty std.9600"    vt100    off secure
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 7,680
Messages: 30,598

And there's your problem:
Code:
#
<<<<<<< current version
=======
# $FreeBSD: releng/12.0/sbin/init/ttys.amd64 338454 2018-09-04 15:48:13Z brd $
>>>>>>> 12.0-RELEASE
#    @(#)ttys    5.1 (Berkeley) 4/17/89
This is a merge that needs to be fixed by hand. You may want to grep the rest of your rc(8) files, there may be more merges that need to be fixed.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Thanks SirDice.

I'm not a specialist of this file, but where is the problem, please?
What do I fix by hand?
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 7,680
Messages: 30,598

I'm betting you have a few more files with similar merge artifacts. I'd take a look at /etc/ssh/sshd_config first, I'm sure there are similar lines in that file and that's causing sshd(8) to fail. You need to check every file in /etc/.

I commented these lines without any change.
Did you reboot? The ttys(5) file is read by init(8).
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Did you reboot?
Yes, before each test.

When connecting to the console, there was an error with sshd. I saw it this morning.
It was due to the use of an -cbc algorithm needed to access an old HP-UX server.
As I read, new version of ssh rejects it now.
I comment these lines and reboot.
Now, no error with ssh but nothing has change.

I activate the /var/log/console.log and /var/log/all.log as found in the forum.

As you say, I verified all files in /etc. Everything is OK.

New important info:
I verified in /var/log/messages.*:
the message "Error waiting for native console 9 activation: Inappropriate ioctl for device" has always be present even last year... So it not the cause of the problem.
 

Phishfry

Son of Beastie

Reaction score: 1,402
Messages: 4,125

I have an old APC box that took some massaging to get around newer crypto and the cbc error you encountered..
ssh -c blowfish-cbc -oKexAlgorithms=+diffie-hellman-group1-sha1 apc@192.168.1.130
Basically you are telling ssh to use a lower, less secure level of encryption.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Yes, Phishfry, you're right. It was needed to access an old HP-UX 11.11 server. The problem is solve now as the server doesn't exist anymore :) and the lines in /etc/ssh/sshd_config are commented.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

In fact the problem is that the display manager hangs on the theme when the following line is added in $HOME/.gtkrc-2.0:
gtk-modules="gail:atk-bridge"

This problem occurs with slim, lightdm, xdm

I think this lines is added by a software install and the desinstallation step doesn't remove it.
But I don't know what soft adds it.

Post updated for people who can have the same problem one day.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 7,680
Messages: 30,598

I think this lines is added by a software install and the desinstallation step doesn't remove it.
But I don't know what soft adds it.
No port or package install would ever do this.
 
OP
OP
bortzy

bortzy

Member


Messages: 27

Or maybe a manual configuration change with the interface in openbox or LXDE but, in any case, it is not a manual change directly in the file.
 
Top