MintBox Mini 2 Pro out of the box with vnc/Xserver issue.

Post Reply
Laszlo
Posts: 1
Joined: Sun Sep 09, 2018 8:08 pm

MintBox Mini 2 Pro out of the box with vnc/Xserver issue.

Post by Laszlo »

Fresh out-of-the-box MintBox Mini 2 pro booted up great, went through setup fine, adjusted colors and background image in the GUI. And then... of course the very first application I tend to install on my linux boxes is vncserver. But it doesn't work. :(

Via the Software Manager GUI searched for tightvncserver (also tried all this with vnc4server), installed it. Clicked on the big green Launch button, and no GUI config dialog appeared.

So I started up vncserver from command line as:

Code: Select all

vncserver :34 -name vnc:34 -geometry 1024x768 -depth 24
Connecting in the usual way with TIght VNC viewer (or TigerVNC viewer), I get a blank screen (no Xsession) and a dialog that simply says:
"Could not acquire name on session bus".
Looking in ~/.xsession-errors, at the moment the vncserver is started, there is a 46-line block of logs that includes these messages:

Code: Select all

Xsession: X session started for laszlo at Sun Sep  9 13:35:40 PDT 2018
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:34
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0x5
  Serial number of failed request:  6
  Current serial number in output stream:  8
localuser:laszlo being added to access control list
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0x5
  Serial number of failed request:  6
  Current serial number in output stream:  8

(...snip...)

cinnamon-session[8720]: WARNING: t+0.02101s: Failed to acquire org.gnome.SessionManager
Gtk-Message: 13:35:40.460: GtkDialog mapped without a transient parent. This is discouraged.
I am using basically the default ~/.vnc/xstartup

Code: Select all

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid black
#x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#x-window-manager &
# Fix to make GNOME work
export XKL_XMODMAP_DISABLE=1
/etc/X11/Xsession
(the block from .xsession-errors is generated during the run of /etc/X11/Xsession)

Based on vaguely (but not entirely) related web posts I've found, I have tried these so far:
  • Added to xstartup lines to unset vars DBUS_SESSION_BUS_ADDRESS and SESSION_MANAGER. No effect.
  • uninstalling/reinstalling the video driver - package xserver-xorg-video-intel. No effect.
  • sudo'ing the vncserver startup. Gave error: vncserver: Wrong type or access mode of /home/laszlo/.vnc (so I chmod 777'ed the entire .vnc dir - no effect).
  • sudo to root first, THEN started vncserver. AHA!! With vncviewer I *AM* able to see a GUI!! However, I also get a dialog saying this:
Cinnamon just crashed. You are currently running in Fallback Mode. Do you want to restart Cinnamon?"
Saying "Yes" just loops through the same message forever. Saying "No" at least I can use the GUI. BUT...what is Fallback Mode, and BTW: the session is logged in as root! Not gonna work out! :)

Can anyone suggest anything? Even suggesting a more appropriate forum? I'm also not emotionally tied to tight vnc, it's just always worked in the past.

Thank you!

Code: Select all

System:    Host: ariadne Kernel: 4.15.0-23-generic x86_64 bits: 64 Desktop: Cinnamon 3.8.6
           Distro: Linux Mint 19 Tara
Machine:   Device: desktop Mobo: Compulab model: fitlet2 v: 1.1 serial: N/A
           UEFI: American Megatrends v: FLT2.MBM2.0.40.01.00 date: 07/05/2018
CPU:       Quad core Intel Celeron J3455 (-MCP-) cache: 1024 KB
           clock speeds: max: 2300 MHz 1: 1009 MHz 2: 948 MHz 3: 1021 MHz 4: 1023 MHz
Graphics:  Card: Intel Device 5a85
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6) version: 4.5 Mesa 18.0.0-rc5
Audio:     Card Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-23-generic
Network:   Card-1: Intel Wireless 8260 driver: iwlwifi
           IF: wlp1s0 state: up mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp2s0 state: down mac: <filter>
           Card-3: Intel I211 Gigabit Network Connection driver: igb
           IF: eno1 state: down mac: <filter>
Drives:    HDD Total Size: 126.7GB (5.1% used)
           ID-1: /dev/sda model: M2SCF size: 126.7GB
Partition: ID-1: / size: 117G used: 6.1G (6%) fs: ext4 dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 41.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 207 Uptime: 9:11 Memory: 875.5/7799.6MB Client: Shell (bash) inxi: 2.3.56

tamir
Site Admin
Posts: 419
Joined: Mon Dec 25, 2017 4:21 pm

Re: MintBox Mini 2 Pro out of the box with vnc/Xserver issue

Post by tamir »

I have forwarded this information to our R&D to help redirect to proper forum or advise.

On any case, it is worth installing the latest Kernel and Mint distribution.
Please visit - http://fit-pc.com/wiki/index.php/Intel: ... ux_Mint_19

Thank you.

tamir
Site Admin
Posts: 419
Joined: Mon Dec 25, 2017 4:21 pm

Re: MintBox Mini 2 Pro out of the box with vnc/Xserver issue

Post by tamir »

Unfortunately there's nothing much our R&D can do to help in this case.
We suggest to contact VNC support/forums to request for help.

Post Reply

Return to “fitlet2 software”