You are not logged in.
- Topics: Active | Unanswered
#351 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 21:02:36
I will give slim a try. If problem recurs with slim, then maybe xorg is to blame? I still think ntp is a red herring, but will try disabling it if all else fails.
#352 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 18:58:35
golinux might be on to something. I rebooted several times and it happened again after a handful of boots. This time I saved the entire /var/log directory.
Nothing interesting in the X log for the failed boot:
[ 8.336]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 8.336] X Protocol Version 11, Revision 0
[ 8.336] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[ 8.336] Current Operating System: Linux thinkpad 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64
[ 8.336] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-5-amd64 root=UUID=e0e5929c-fc57-4c5a-9efb-3922571850df ro quiet intremap=off loglevel=3
[ 8.336] Build Date: 16 October 2017 08:19:45AM
[ 8.336] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
[ 8.336] Current version of pixman: 0.34.0
[ 8.336] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 8.336] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8.336] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 29 14:44:50 2018
[ 8.337] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 8.337] (==) No Layout section. Using the first Screen section.
[ 8.337] (==) No screen section available. Using defaults.
[ 8.337] (**) |-->Screen "Default Screen Section" (0)
[ 8.337] (**) | |-->Monitor "<default monitor>"
[ 8.337] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 8.337] (==) Automatically adding devices
[ 8.337] (==) Automatically enabling devices
[ 8.337] (==) Automatically adding GPU devices
[ 8.337] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 8.337] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 8.337] Entry deleted from font path.
[ 8.337] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[ 8.337] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 8.337] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 8.337] (II) Loader magic: 0x55bd9c13de00
[ 8.337] (II) Module ABI versions:
[ 8.337] X.Org ANSI C Emulation: 0.4
[ 8.337] X.Org Video Driver: 23.0
[ 8.337] X.Org XInput driver : 24.1
[ 8.337] X.Org Server Extension : 10.0
[ 8.339] (++) using VT number 7
[ 8.340] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 8.340] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 8.342] (--) PCI:*(0:0:2:0) 8086:2a42:17aa:20e4 rev 7, Mem @ 0xe1400000/4194304, 0xd0000000/268435456, I/O @ 0x00005400/8
[ 8.342] (--) PCI: (0:0:2:1) 8086:2a43:17aa:20e4 rev 7, Mem @ 0xe5900000/1048576
[ 8.342] (II) LoadModule: "glx"
[ 8.342] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8.344] (II) Module glx: vendor="X.Org Foundation"
[ 8.344] compiled for 1.19.2, module version = 1.0.0
[ 8.344] ABI class: X.Org Server Extension, version 10.0
[ 8.344] (==) Matched modesetting as autoconfigured driver 0
[ 8.344] (==) Matched fbdev as autoconfigured driver 1
[ 8.344] (==) Matched vesa as autoconfigured driver 2
[ 8.344] (==) Assigned the driver to the xf86ConfigLayout
[ 8.344] (II) LoadModule: "modesetting"
[ 8.344] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 8.344] (II) Module modesetting: vendor="X.Org Foundation"
[ 8.344] compiled for 1.19.2, module version = 1.19.2
[ 8.344] Module class: X.Org Video Driver
[ 8.344] ABI class: X.Org Video Driver, version 23.0
[ 8.345] (II) LoadModule: "fbdev"
[ 8.345] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 8.345] (II) Module fbdev: vendor="X.Org Foundation"
[ 8.345] compiled for 1.19.0, module version = 0.4.4
[ 8.345] Module class: X.Org Video Driver
[ 8.345] ABI class: X.Org Video Driver, version 23.0
[ 8.345] (II) LoadModule: "vesa"
[ 8.345] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 8.345] (II) Module vesa: vendor="X.Org Foundation"
[ 8.345] compiled for 1.19.0, module version = 2.3.4
[ 8.345] Module class: X.Org Video Driver
[ 8.345] ABI class: X.Org Video Driver, version 23.0
[ 8.345] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 8.345] (II) FBDEV: driver for framebuffer: fbdev
[ 8.345] (II) VESA: driver for VESA chipsets: vesa
[ 8.345] (II) modeset(0): using drv /dev/dri/card0
[ 8.345] (WW) Falling back to old probe method for fbdev
[ 8.345] (II) Loading sub module "fbdevhw"
[ 8.345] (II) LoadModule: "fbdevhw"
[ 8.345] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 8.346] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 8.346] compiled for 1.19.2, module version = 0.0.2
[ 8.346] ABI class: X.Org Video Driver, version 23.0
[ 8.346] (WW) Falling back to old probe method for vesa
[ 8.346] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 8.346] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 8.346] (==) modeset(0): RGB weight 888
[ 8.346] (==) modeset(0): Default visual is TrueColor
[ 8.346] (II) Loading sub module "glamoregl"
[ 8.346] (II) LoadModule: "glamoregl"
[ 8.346] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 8.351] (II) Module glamoregl: vendor="X.Org Foundation"
[ 8.351] compiled for 1.19.2, module version = 1.0.0
[ 8.351] ABI class: X.Org ANSI C Emulation, version 0.4
[ 8.351] (II) glamor: OpenGL accelerated X.org driver based.
[ 8.365] (II) glamor: EGL version 1.4 (DRI2):
[ 8.369] (II) modeset(0): glamor initialized
[ 8.369] (II) modeset(0): Output LVDS-1 has no monitor section
[ 8.392] (II) modeset(0): Output VGA-1 has no monitor section
[ 8.392] (II) modeset(0): Output DP-1 has no monitor section
[ 8.512] (II) modeset(0): Output SVIDEO-1 has no monitor section
[ 8.512] (II) modeset(0): EDID for output LVDS-1
[ 8.513] (II) modeset(0): Manufacturer: LEN Model: 4035 Serial#: 0
[ 8.513] (II) modeset(0): Year: 2009 Week: 0
[ 8.513] (II) modeset(0): EDID Version: 1.3
[ 8.513] (II) modeset(0): Digital Display Input
[ 8.513] (II) modeset(0): Max Image Size [cm]: horiz.: 30 vert.: 19
[ 8.513] (II) modeset(0): Gamma: 2.20
[ 8.513] (II) modeset(0): DPMS capabilities: StandBy Suspend Off
[ 8.513] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 8.513] (II) modeset(0): First detailed timing is preferred mode
[ 8.513] (II) modeset(0): redX: 0.574 redY: 0.349 greenX: 0.335 greenY: 0.542
[ 8.513] (II) modeset(0): blueX: 0.156 blueY: 0.136 whiteX: 0.313 whiteY: 0.329
[ 8.513] (II) modeset(0): Manufacturer's mask: 0
[ 8.513] (II) modeset(0): Supported detailed timing:
[ 8.513] (II) modeset(0): clock: 69.5 MHz Image Size: 304 x 190 mm
[ 8.513] (II) modeset(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1405 h_border: 0
[ 8.513] (II) modeset(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 822 v_border: 0
[ 8.513] (II) modeset(0): Supported detailed timing:
[ 8.513] (II) modeset(0): clock: 57.7 MHz Image Size: 304 x 190 mm
[ 8.513] (II) modeset(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1405 h_border: 0
[ 8.513] (II) modeset(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 822 v_border: 0
[ 8.513] (II) modeset(0): Unknown vendor-specific block f
[ 8.513] (II) modeset(0): LP141WX5-TLP2
[ 8.513] (II) modeset(0): EDID (in hex):
[ 8.513] (II) modeset(0): 00ffffffffffff0030ae354000000000
[ 8.513] (II) modeset(0): 00130103801e1378ea1f359359558a28
[ 8.513] (II) modeset(0): 22505400000001010101010101010101
[ 8.513] (II) modeset(0): 010101010101261b007d502016303020
[ 8.513] (II) modeset(0): 360030be100000188b16007d50201630
[ 8.513] (II) modeset(0): 3020360030be100000180000000f0081
[ 8.513] (II) modeset(0): 0a32810a2814090030e4ed01000000fe
[ 8.513] (II) modeset(0): 004c503134315758352d544c503200eb
[ 8.513] (II) modeset(0): Printing probed modes for output LVDS-1
[ 8.513] (II) modeset(0): Modeline "1280x800"x60.2 69.50 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (49.5 kHz eP)
[ 8.513] (II) modeset(0): Modeline "1280x800"x50.0 57.71 1280 1328 1360 1405 800 803 809 822 -hsync -vsync (41.1 kHz e)
[ 8.513] (II) modeset(0): Modeline "1024x768"x120.1 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[ 8.513] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 8.513] (II) modeset(0): Modeline "960x720"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "928x696"x120.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[ 8.513] (II) modeset(0): Modeline "896x672"x120.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[ 8.513] (II) modeset(0): Modeline "960x600"x120.0 77.00 960 984 1000 1040 600 601 604 617 doublescan +hsync -vsync (74.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "960x540"x120.0 69.25 960 984 1000 1040 540 541 544 555 doublescan +hsync -vsync (66.6 kHz d)
[ 8.513] (II) modeset(0): Modeline "800x600"x120.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 8.513] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 8.513] (II) modeset(0): Modeline "840x525"x120.0 73.12 840 892 980 1120 525 526 529 544 doublescan -hsync +vsync (65.3 kHz d)
[ 8.513] (II) modeset(0): Modeline "840x525"x119.8 59.50 840 864 880 920 525 526 529 540 doublescan +hsync -vsync (64.7 kHz d)
[ 8.513] (II) modeset(0): Modeline "800x512"x120.3 51.56 800 800 828 832 512 512 514 515 doublescan +hsync +vsync (62.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "700x525"x120.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[ 8.513] (II) modeset(0): Modeline "640x512"x120.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "720x450"x119.8 53.25 720 760 836 952 450 451 454 467 doublescan -hsync +vsync (55.9 kHz d)
[ 8.513] (II) modeset(0): Modeline "640x480"x120.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[ 8.513] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 8.513] (II) modeset(0): Modeline "680x384"x119.6 42.38 680 716 784 888 384 385 390 399 doublescan -hsync +vsync (47.7 kHz d)
[ 8.513] (II) modeset(0): Modeline "680x384"x119.9 36.00 680 704 720 760 384 385 390 395 doublescan +hsync -vsync (47.4 kHz d)
[ 8.513] (II) modeset(0): Modeline "576x432"x120.1 40.81 576 608 668 760 432 432 434 447 doublescan -hsync +vsync (53.7 kHz d)
[ 8.513] (II) modeset(0): Modeline "512x384"x120.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[ 8.513] (II) modeset(0): Modeline "400x300"x120.6 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[ 8.513] (II) modeset(0): Modeline "400x300"x112.7 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[ 8.514] (II) modeset(0): Modeline "320x240"x120.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[ 8.540] (II) modeset(0): EDID for output VGA-1
[ 8.540] (II) modeset(0): EDID for output DP-1
[ 8.660] (II) modeset(0): EDID for output SVIDEO-1
[ 8.660] (II) modeset(0): Output LVDS-1 connected
[ 8.660] (II) modeset(0): Output VGA-1 disconnected
[ 8.660] (II) modeset(0): Output DP-1 disconnected
[ 8.660] (II) modeset(0): Output SVIDEO-1 disconnected
[ 8.660] (II) modeset(0): Using exact sizes for initial modes
[ 8.660] (II) modeset(0): Output LVDS-1 using initial mode 1280x800 +0+0
[ 8.660] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[ 8.660] (==) modeset(0): DPI set to (96, 96)
[ 8.660] (II) Loading sub module "fb"
[ 8.660] (II) LoadModule: "fb"
[ 8.661] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 8.661] (II) Module fb: vendor="X.Org Foundation"
[ 8.661] compiled for 1.19.2, module version = 1.0.0
[ 8.661] ABI class: X.Org ANSI C Emulation, version 0.4
[ 8.661] (II) UnloadModule: "fbdev"
[ 8.661] (II) Unloading fbdev
[ 8.661] (II) UnloadSubModule: "fbdevhw"
[ 8.661] (II) Unloading fbdevhw
[ 8.661] (II) UnloadModule: "vesa"
[ 8.661] (II) Unloading vesa
[ 8.661] (==) Depth 24 pixmap format is 32 bpp
[ 8.801] (==) modeset(0): Backing store enabled
[ 8.801] (==) modeset(0): Silken mouse enabled
[ 8.801] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 8.801] (==) modeset(0): DPMS enabled
[ 8.801] (II) modeset(0): [DRI2] Setup complete
[ 8.801] (II) modeset(0): [DRI2] DRI driver: i965
[ 8.801] (II) modeset(0): [DRI2] VDPAU driver: i965
[ 8.801] (--) RandR disabled
[ 8.805] (II) SELinux: Disabled on system
[ 8.812] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 8.812] (II) AIGLX: enabled GLX_ARB_create_context
[ 8.812] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 8.812] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 8.812] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 8.812] (II) AIGLX: enabled GLX_SGI_swap_control
[ 8.812] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 8.812] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 8.812] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 8.812] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 8.812] (II) AIGLX: Loaded and initialized i965
[ 8.812] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 8.815] (II) modeset(0): Damage tracking initialized
[ 8.815] (II) modeset(0): Setting screen physical size to 338 x 211
[ 8.849] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 8.849] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 8.849] (II) LoadModule: "libinput"
[ 8.849] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 8.851] (II) Module libinput: vendor="X.Org Foundation"
[ 8.851] compiled for 1.19.0, module version = 0.23.0
[ 8.851] Module class: X.Org XInput Driver
[ 8.851] ABI class: X.Org XInput driver, version 24.1
[ 8.851] (II) Using input driver 'libinput' for 'Power Button'
[ 8.851] (**) Power Button: always reports core events
[ 8.851] (**) Option "Device" "/dev/input/event5"
[ 8.851] (**) Option "_source" "server/udev"
[ 8.852] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 8.852] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 8.867] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event5"
[ 8.867] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 8.867] (**) Option "xkb_model" "pc105"
[ 8.867] (**) Option "xkb_layout" "us"
[ 8.867] (**) Option "xkb_options" "compose:menu,terminate:ctrl_alt_bksp"
[ 8.895] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 8.895] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 8.895] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[ 8.895] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 8.895] (II) Using input driver 'libinput' for 'Video Bus'
[ 8.895] (**) Video Bus: always reports core events
[ 8.895] (**) Option "Device" "/dev/input/event2"
[ 8.895] (**) Option "_source" "server/udev"
[ 8.895] (II) input device 'Video Bus', /dev/input/event2 is tagged by udev as: Keyboard
[ 8.895] (II) input device 'Video Bus', /dev/input/event2 is a keyboard
[ 8.908] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4/event2"
[ 8.908] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 8.908] (**) Option "xkb_model" "pc105"
[ 8.908] (**) Option "xkb_layout" "us"
[ 8.908] (**) Option "xkb_options" "compose:menu,terminate:ctrl_alt_bksp"
[ 8.908] (II) input device 'Video Bus', /dev/input/event2 is tagged by udev as: Keyboard
[ 8.908] (II) input device 'Video Bus', /dev/input/event2 is a keyboard
[ 8.908] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
[ 8.908] (II) No input driver specified, ignoring this device.
[ 8.908] (II) This device may have been added with another device file.
[ 8.909] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 8.909] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 8.909] (II) Using input driver 'libinput' for 'Sleep Button'
[ 8.909] (**) Sleep Button: always reports core events
[ 8.909] (**) Option "Device" "/dev/input/event3"
[ 8.909] (**) Option "_source" "server/udev"
[ 8.909] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
[ 8.909] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
[ 8.937] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C09:00/PNP0C0E:00/input/input5/event3"
[ 8.937] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 8.937] (**) Option "xkb_model" "pc105"
[ 8.937] (**) Option "xkb_layout" "us"
[ 8.937] (**) Option "xkb_options" "compose:menu,terminate:ctrl_alt_bksp"
[ 8.937] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
[ 8.937] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
[ 8.938] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 8.938] (II) No input driver specified, ignoring this device.
[ 8.938] (II) This device may have been added with another device file.
[ 8.938] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
[ 8.938] (II) No input driver specified, ignoring this device.
[ 8.938] (II) This device may have been added with another device file.
[ 8.938] (II) config/udev: Adding input device HDA Intel Dock Mic (/dev/input/event9)
[ 8.938] (II) No input driver specified, ignoring this device.
[ 8.938] (II) This device may have been added with another device file.
[ 8.938] (II) config/udev: Adding input device HDA Intel Dock Headphone (/dev/input/event10)
[ 8.938] (II) No input driver specified, ignoring this device.
[ 8.938] (II) This device may have been added with another device file.
[ 8.939] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event11)
[ 8.939] (II) No input driver specified, ignoring this device.
[ 8.939] (II) This device may have been added with another device file.
[ 8.939] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 8.939] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 8.939] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 8.939] (**) AT Translated Set 2 keyboard: always reports core events
[ 8.939] (**) Option "Device" "/dev/input/event0"
[ 8.939] (**) Option "_source" "server/udev"
[ 8.939] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 8.939] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 8.956] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 8.956] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 8.956] (**) Option "xkb_model" "pc105"
[ 8.956] (**) Option "xkb_layout" "us"
[ 8.956] (**) Option "xkb_options" "compose:menu,terminate:ctrl_alt_bksp"
[ 8.958] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 8.958] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 8.959] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
[ 8.959] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
[ 8.959] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 8.959] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 8.959] (II) LoadModule: "synaptics"
[ 8.959] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 8.960] (II) Module synaptics: vendor="X.Org Foundation"
[ 8.960] compiled for 1.19.0, module version = 1.9.0
[ 8.960] Module class: X.Org XInput Driver
[ 8.960] ABI class: X.Org XInput driver, version 24.1
[ 8.960] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 8.960] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 8.960] (**) Option "Device" "/dev/input/event1"
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5598 (res 67)
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4670 (res 111)
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right
[ 8.992] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 8.993] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8.993] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 9.052] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
[ 9.052] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
[ 9.052] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 9.052] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 9.052] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 9.053] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 9.053] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 9.053] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 9.053] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 9.054] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 9.054] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 9.055] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 9.055] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event13)
[ 9.055] (**) TPPS/2 IBM TrackPoint: Applying InputClass "libinput pointer catchall"
[ 9.055] (II) Using input driver 'libinput' for 'TPPS/2 IBM TrackPoint'
[ 9.055] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 9.055] (**) Option "Device" "/dev/input/event13"
[ 9.056] (**) Option "_source" "server/udev"
[ 9.056] (II) input device 'TPPS/2 IBM TrackPoint', /dev/input/event13 is tagged by udev as: Mouse
[ 9.056] (II) input device 'TPPS/2 IBM TrackPoint', /dev/input/event13 is a pointer caps
[ 9.076] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input3/event13"
[ 9.076] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 11)
[ 9.077] (**) Option "AccelerationScheme" "none"
[ 9.077] (**) TPPS/2 IBM TrackPoint: (accel) selected scheme none/0
[ 9.077] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 9.077] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 9.078] (II) input device 'TPPS/2 IBM TrackPoint', /dev/input/event13 is tagged by udev as: Mouse
[ 9.078] (II) input device 'TPPS/2 IBM TrackPoint', /dev/input/event13 is a pointer caps
[ 9.079] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[ 9.079] (II) No input driver specified, ignoring this device.
[ 9.079] (II) This device may have been added with another device file.
[ 9.080] (II) config/udev: Adding input device PC Speaker (/dev/input/event12)
[ 9.080] (II) No input driver specified, ignoring this device.
[ 9.080] (II) This device may have been added with another device file.
[ 9.081] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event6)
[ 9.082] (**) ThinkPad Extra Buttons: Applying InputClass "libinput keyboard catchall"
[ 9.082] (II) Using input driver 'libinput' for 'ThinkPad Extra Buttons'
[ 9.082] (**) ThinkPad Extra Buttons: always reports core events
[ 9.082] (**) Option "Device" "/dev/input/event6"
[ 9.082] (**) Option "_source" "server/udev"
[ 9.082] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is tagged by udev as: Keyboard
[ 9.083] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is a keyboard
[ 9.108] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input8/event6"
[ 9.108] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 12)
[ 9.108] (**) Option "xkb_model" "pc105"
[ 9.108] (**) Option "xkb_layout" "us"
[ 9.108] (**) Option "xkb_options" "compose:menu,terminate:ctrl_alt_bksp"
[ 9.110] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is tagged by udev as: Keyboard
[ 9.110] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is a keyboardHowever, lightdm log for the failed boot ends with an error:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=2329
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.32s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.32s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.33s] DEBUG: Seat seat0: Creating display server of type x
[+0.33s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.33s] DEBUG: Using VT 7
[+0.33s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.33s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.33s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.33s] DEBUG: DisplayServer x-0: Launching X Server
[+0.33s] DEBUG: Launching process 2511: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.33s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.33s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.33s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+1.24s] DEBUG: Got signal 10 from process 2511
[+1.24s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1.24s] DEBUG: DisplayServer x-0: Connecting to XServer :0
********** [+1.41s] DEBUG: DisplayServer x-0: Error connecting to XServer :0
[+1.41s] DEBUG: Process 2511 exited with return value 1
[+1.41s] DEBUG: DisplayServer x-0: X server stopped
[+1.41s] DEBUG: Releasing VT 7
[+1.41s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+1.41s] DEBUG: Seat seat0: Display server stopped
[+1.41s] DEBUG: Seat seat0: Stopping session
[+1.41s] DEBUG: Seat seat0: Session stopped
[+1.41s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.41s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+1.41s] DEBUG: Seat seat0: Creating greeter session
[+1.41s] DEBUG: Seat seat0: Creating display server of type x
[+1.41s] DEBUG: Using VT 7
[+1.41s] DEBUG: Seat seat0: Starting local X display on VT 7
[+1.41s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+1.41s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+1.41s] DEBUG: DisplayServer x-0: Launching X Server
[+1.42s] DEBUG: Launching process 2539: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1.42s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+2.21s] DEBUG: Got signal 10 from process 2539
[+2.21s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+2.21s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+2.36s] DEBUG: DisplayServer x-0: Error connecting to XServer :0
[+2.36s] DEBUG: Process 2539 exited with return value 1
[+2.36s] DEBUG: DisplayServer x-0: X server stopped
[+2.36s] DEBUG: Releasing VT 7
[+2.36s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+2.36s] DEBUG: Seat seat0: Display server stopped
[+2.36s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+2.36s] DEBUG: Seat seat0: Stopping
[+2.36s] DEBUG: Seat seat0: Stopping session
[+2.36s] DEBUG: Seat seat0: Session stopped
[+2.36s] DEBUG: Seat seat0: Stopped
[+2.36s] DEBUG: Required seat has stopped
[+2.36s] DEBUG: Stopping display manager
[+2.36s] DEBUG: Display manager stopped
[+2.36s] DEBUG: Stopping daemon
[+2.36s] DEBUG: Seat seat0: Stopping session
[+2.36s] DEBUG: Exiting with return value 1For comparison, here is a lightdm log from a successful boot:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=2332
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.32s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.32s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.33s] DEBUG: Seat seat0: Creating display server of type x
[+0.33s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.33s] DEBUG: Using VT 7
[+0.33s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.33s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.33s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.33s] DEBUG: DisplayServer x-0: Launching X Server
[+0.33s] DEBUG: Launching process 2513: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.33s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.33s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.33s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+1.24s] DEBUG: Got signal 10 from process 2513
[+1.24s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1.24s] DEBUG: DisplayServer x-0: Connecting to XServer :0
********** [+1.26s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.26s] DEBUG: Session pid=2536: Started with service 'lightdm-autologin', username 'bruno'
[+1.28s] DEBUG: Session pid=2536: Authentication complete with return value 0: Success
[+1.28s] DEBUG: Seat seat0: Session authenticated, running command
[+1.28s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+1.29s] DEBUG: Session pid=2536: Running command /etc/X11/Xsession default
[+1.29s] DEBUG: Creating shared data directory /var/lib/lightdm/data/bruno
[+1.29s] DEBUG: Session pid=2536: Logging to .xsession-errors
[+1.29s] DEBUG: Activating VT 7
[+1.29s] DEBUG: Activating login1 session 1
[+1.29s] DEBUG: Seat seat0 changes active session to 1
[+1.29s] DEBUG: Session 1 is already activeI marked the first line that's different between the two lightdm logs with some asterisks.
Before I jump ship and switch from lightdm to slim (which I've never used), I'd like to try troubleshooting my system as currently configured. Maybe lightdm is innocent and this is actually an X issue despite the benign-appearing X log?
Any idea why lightdm is failing? Now I have access to whatever logs we need.
P.S. I tried bbatten's idea but no luck. When boot hangs this way, computer does not respond to anything except power button and SysRq key.
#353 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 18:33:45
bbatten, that's an interesting idea. I will try that next time I have the issue and will post the result in this thread. I do know that at least the kernel is running (SysRq key works and I can use it instead of power button to reboot).
Also, FWIW the problem affects all virtual consoles: When screen is black and I press Ctrl+Alt+F1 (or F2, F3, etc), instead of seeing a login prompt like I normally do I just see the same totally black screen.
Next time it happens I'll save the X and lightdm logs in addition to syslog.
#354 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 18:01:33
I just had another hung boot. It was 1:42 pm when the boot process left me at the black screen. I waited at the black screen until 1:46 pm before forcing a reboot with SysRq keys. These are the last few relevant lines from /var/log/syslog. I can go further back if necessary:
Mar 29 13:42:03 localhost nm-dispatcher: req:2 'up' [wlan1]: start running ordered scripts...
Mar 29 13:42:03 localhost NetworkManager[2445]: <warn> [1522345323.3555] dispatcher: (2) bruno-nm-dispatcher-hooks failed (failed): Script '/etc/NetworkManager/dispatcher.d/bruno-nm-dispatcher-hooks' exited with error status 1.
Mar 29 13:42:03 localhost ntpd[2170]: Soliciting pool server 66.135.44.92
Mar 29 13:42:03 localhost ntpdate[2601]: the NTP socket is in use, exiting
Mar 29 13:42:03 localhost nm-dispatcher: req:2 'up' [wlan1], "/etc/NetworkManager/dispatcher.d/bruno-nm-dispatcher-hooks": complete: failed with Script '/etc/NetworkManager/dispatcher.d/bruno-nm-dispatcher-hooks' exited with error status 1.
Mar 29 13:42:03 localhost NetworkManager[2445]: <warn> [1522345323.6479] dispatcher: (3) bruno-nm-dispatcher-hooks failed (failed): Script '/etc/NetworkManager/dispatcher.d/bruno-nm-dispatcher-hooks' exited with error status 1.
Mar 29 13:42:04 localhost ntpd[2170]: Listen normally on 4 wlan1 192.168.10.190:123
Mar 29 13:42:04 localhost ntpd[2170]: bind(24) AF_INET6 fe80::5eac:4cff:fe0d:5e5c%3#123 flags 0x11 failed: Cannot assign requested address
Mar 29 13:42:04 localhost ntpd[2170]: unable to create socket on wlan1 (5) for fe80::5eac:4cff:fe0d:5e5c%3#123
Mar 29 13:42:04 localhost ntpd[2170]: failed to init interface for address fe80::5eac:4cff:fe0d:5e5c%3
Mar 29 13:42:04 localhost ntpd[2170]: Soliciting pool server 162.210.111.4
Mar 29 13:42:04 localhost avahi-daemon[2306]: Joining mDNS multicast group on interface wlan1.IPv6 with address fe80::5eac:4cff:fe0d:5e5c.
Mar 29 13:42:04 localhost avahi-daemon[2306]: New relevant interface wlan1.IPv6 for mDNS.
Mar 29 13:42:04 localhost avahi-daemon[2306]: Registering new address record for fe80::5eac:4cff:fe0d:5e5c on wlan1.*.
Mar 29 13:42:04 localhost ModemManager[2516]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Mar 29 13:42:04 localhost ModemManager[2516]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by any plugin
Mar 29 13:42:05 localhost ntpd[2170]: Soliciting pool server 66.96.99.10
Mar 29 13:42:05 localhost ntpd[2170]: Soliciting pool server 62.168.65.36
Mar 29 13:42:06 localhost ntpd[2170]: Soliciting pool server 89.40.116.249
Mar 29 13:42:06 localhost ntpd[2170]: Soliciting pool server 45.76.244.193
Mar 29 13:42:06 localhost ntpd[2170]: Listen normally on 6 wlan1 [fe80::5eac:4cff:fe0d:5e5c%3]:123
Mar 29 13:42:07 localhost NetworkManager[2445]: <info> [1522345327.2660] manager: startup complete
Mar 29 13:42:07 localhost ntpd[2170]: Soliciting pool server 85.93.7.12
Mar 29 13:42:07 localhost ntpd[2170]: Soliciting pool server 129.250.35.251
Mar 29 13:42:08 localhost ntpd[2170]: Soliciting pool server 96.126.105.86
Mar 29 13:42:08 localhost ntpd[2170]: Soliciting pool server 2600:3c01::f03c:91ff:fec8:5c8
Mar 29 13:42:14 localhost ntpd[2170]: receive: Unexpected origin timestamp 0xde67a3f5.77f33bc6 does not match aorg 0000000000.00000000 from server@45.76.244.193 xmt 0xde67a3f6.40b18fc8
Mar 29 13:42:14 localhost ntpd[2170]: receive: Unexpected origin timestamp 0xde67a3f5.77feb327 does not match aorg 0000000000.00000000 from server@162.210.111.4 xmt 0xde67a3f6.45945a7c
Mar 29 13:42:38 localhost wpa_supplicant[2517]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Mar 29 13:43:21 localhost wpa_supplicant[2517]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Mar 29 13:44:24 localhost wpa_supplicant[2517]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Mar 29 13:46:24 localhost kernel: [ 268.745006] SysRq : Keyboard mode set to system defaultIt seems that the last lines logged from the boot attempt were from ntpd, but maybe that's a red herring. Any ideas?
#355 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 17:32:39
I use MATE with its default WM, which is marco. My display/login manager is lightdm.
I took a look through /var/log/syslog but did not find anything obvious yet.
#356 Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-29 16:10:41
- GNUser
- Replies: 26
Approximately 1 out of every 5-10 boots hangs on my T400 with ASCII. It seems to be completely random.
When it happens, the usual boot messages scroll by without any errors and then the messages are cleared to a black screen as usual, but instead of my desktop appearing the screen stays black with cursor blinking in the upper left corner of the screen. The only way forward is to press and hold the power button until system is off then power up again (or do SysRq + r-e-i-s-u-b).
Has anyone else experienced this? If not, can you help me troubleshoot? I guess setting up saved boot logs would be a first step?
#357 Re: Off-topic » how to force scrollbar buttons on all desktop themes [SOLVED] » 2018-03-27 22:07:22
xunilog, I'm really happy you found my hack to be useful 
BTW, I added a comment to the above code to show what to change if you wish to customize the color of the scrollbar when you hover over it with the mouse. Search for "customize mouse hover color".
#358 Re: Off-topic » how to force scrollbar buttons on all desktop themes [SOLVED] » 2018-03-20 23:17:33
I think it's a slightly different issue. The issue I'm having is that all of the recently-created themes I downloaded (e.g., from gnome-look.org) have only a skinny "modern" scrollbar without scrollbar buttons. Just forcing these themes to show the scrollbar buttons by changing "has-backward-stepper" and "has-forward-stepper" to true in the theme's css files is not satisfactory, as scrollbar buttons do show up but both the scrollbar and the buttons look weird because the themes do not include a design for the buttons.
My solution is a complete, traditional scrollbar-with-buttons design that overrides whatever scrollbar is specified in the selected theme.
Just to clarify: I was able to solve my problem. I created the thread only in the hope that my solution may be useful to others who want to use a modern theme but override its vestigial toolbar with something more traditional.
#359 Off-topic » how to force scrollbar buttons on all desktop themes [SOLVED] » 2018-03-20 20:05:06
- GNUser
- Replies: 5
All nice-looking themes these days seem to think that scrollbar buttons are obsolete. Old habits die hard, and the UI designer masterminds are going to have to rip my scrollbar buttons from my cold dead hands.
I came up with a solution that gives me a nice scrollbar with buttons regardless of selected theme. By putting the code below in ~/.config/gtk-3.0/gtk.css I can have the same exact, traditional scrollbar across all themes available on my machine:
@define-color scrollbar_theme_fg_color #000000;
@define-color scrollbar_theme_bg_color #eeeeee;
@define-color scrollbar_core_color_b #eeeeee;
@define-color scrollbar_insensitive_fg_color shade(@scrollbar_core_color_b, 0.70);
@define-color scrollbar_internal_element_insensitive_color @scrollbar_insensitive_fg_color;
@define-color scrollbar_theme_text_color #000000;
/* junction */
@define-color scrollbars_junction_bg_color @scrollbar_theme_bg_color;
/* trough */
@define-color scrollbar_trough_border_color shade(@scrollbar_core_color_b, 0.67);
@define-color scrollbar_trough_gradient_a shade(@scrollbar_core_color_b, 0.86);
@define-color scrollbar_trough_gradient_b shade(@scrollbar_core_color_b, 0.90);
/* slider */
@define-color scrollbar_slider_bg_color shade(@scrollbar_core_color_b, 1.03);
@define-color scrollbar_slider_gradient_a @scrollbar_slider_bg_color;
@define-color scrollbar_slider_gradient_b shade(@scrollbar_core_color_b, 0.98);
@define-color scrollbar_slider_gradient_c shade(@scrollbar_core_color_b, 0.94);
@define-color scrollbar_slider_gradient_d shade(@scrollbar_core_color_b, 0.88);
@define-color scrollbar_slider_border_color mix(#000000, shade(@scrollbar_core_color_b, 0.72), 0.95);
@define-color scrollbar_slider_inner_border_color shade(@scrollbar_core_color_b, 1.04);
/* slider hover */
@define-color scrollbar_slider_hover_bg_color shade(#5294e2, 1.03); /* customize mouse hover color by changing #5294e2 to your desired color */
@define-color scrollbar_slider_hover_gradient_a @scrollbar_slider_hover_bg_color;
@define-color scrollbar_slider_hover_gradient_b shade(@scrollbar_core_color_b, 1.00);
@define-color scrollbar_slider_hover_gradient_c shade(@scrollbar_core_color_b, 0.98);
@define-color scrollbar_slider_hover_gradient_d shade(@scrollbar_core_color_b, 0.96);
/* button */
@define-color scrollbar_button_color @scrollbar_theme_fg_color;
@define-color scrollbar_button_insensitive_color @scrollbar_internal_element_insensitive_color;
@define-color scrollbar_button_border_color shade(@scrollbar_core_color_b, 0.56);
@define-color scrollbar_button_gradient_a shade(@scrollbar_core_color_b, 1.07);
@define-color scrollbar_button_gradient_b shade(@scrollbar_core_color_b, 1.02);
@define-color scrollbar_button_gradient_c shade(@scrollbar_core_color_b, 0.99);
@define-color scrollbar_button_gradient_d shade(@scrollbar_core_color_b, 0.95);
/* button hover */
@define-color scrollbar_button_hover_gradient_a shade(@scrollbar_core_color_b, 1.07);
@define-color scrollbar_button_hover_gradient_b shade(@scrollbar_core_color_b, 1.05);
@define-color scrollbar_button_hover_gradient_c shade(@scrollbar_core_color_b, 1.02);
@define-color scrollbar_button_hover_gradient_d shade(@scrollbar_core_color_b, 0.97);
/* button active */
@define-color scrollbar_button_active_gradient_a shade(@scrollbar_core_color_b, 0.95);
@define-color scrollbar_button_active_gradient_b shade(@scrollbar_core_color_b, 0.92);
@define-color scrollbar_button_active_gradient_c shade(@scrollbar_core_color_b, 0.89);
@define-color scrollbar_button_active_gradient_d shade(@scrollbar_core_color_b, 0.85);
scrollbar {
background-image: none;
border-style: solid;
border-color: @scrollbar_trough_border_color;
-GtkScrollbar-has-backward-stepper: true;
-GtkScrollbar-has-forward-stepper: true;
box-shadow: none;
border-image: none;
}
scrollbar.vertical {
border-width: 0px 0px 0px 1px;
min-width: 14px;
}
scrollbar.horizontal {
border-width: 1px 0px 0px 0px;
min-height: 14px;
}
scrollbar trough {
border-style: solid;
border-color: @scrollbar_trough_border_color;
}
scrolledwindow junction {
background-image: none;
background-color: @scrollbars_junction_bg_color;
}
scrollbar.horizontal trough {
min-height: 14px;
border-radius: 0px;
border-width: 0px 1px 0px 1px;
border-image: none;
background-image: -gtk-gradient (linear,
left top,
left bottom,
color-stop (0, @scrollbar_trough_gradient_a),
color-stop (0.5, @scrollbar_trough_gradient_b));
}
scrollbar.vertical trough {
min-width: 14px;
border-radius: 0px;
border-width: 1px 0px 1px 0px;
border-image: none;
background-image: -gtk-gradient (linear,
left top,
right top,
color-stop (0, @scrollbar_trough_gradient_a),
color-stop (0.5, @scrollbar_trough_gradient_b));
}
/* Buttons */
scrollbar.vertical button,
scrollbar.vertical .button {
min-width: 14px;
min-height: 16px;
padding: 1px 0px;
}
scrollbar.horizontal button,
scrollbar.horizontal .button {
min-width: 16px;
min-height: 14px;
padding: 0px 1px;
}
scrollbar.vertical button.up,
scrollbar.vertical .button.up {
-gtk-icon-source: -gtk-icontheme("pan-up-symbolic");
}
scrollbar.vertical button.down,
scrollbar.vertical .button.down {
-gtk-icon-source: -gtk-icontheme("pan-down-symbolic");
}
scrollbar.horizontal button.up,
scrollbar.horizontal .button.up {
-gtk-icon-source: -gtk-icontheme("pan-start-symbolic");
}
scrollbar.horizontal button.down,
scrollbar.horizontal .button.down {
-gtk-icon-source: -gtk-icontheme("pan-end-symbolic");
}
scrollbar button,
scrollbar .button {
border-image: none;
border-style: none;
border-width: 0px;
border-radius: 0px;
background-image: none;
background-color: transparent;
color: @scrollbar_theme_text_color;
border-style: solid;
border-color: transparent;
}
scrollbar button:hover,
scrollbar .button:hover {
border-image: none;
border-style: none;
border-width: 0px;
border-radius: 0px;
}
scrollbar button:disabled,
scrollbar .button:disabled {
color: @scrollbar_button_insensitive_color;
border-image: none;
border-style: none;
border-width: 0px;
border-radius: 0px;
}
scrollbar.horizontal button,
scrollbar.horizontal .button {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (@scrollbar_button_gradient_a),
to (@scrollbar_button_gradient_d));
}
scrollbar.horizontal button:hover,
scrollbar.horizontal .button:hover {
background-image: -gtk-gradient (linear,
left bottom,
left top,
from (@scrollbar_button_hover_gradient_a),
to (@scrollbar_button_hover_gradient_d));
}
scrollbar.horizontal button:hover:active,
scrollbar.horizontal .button:hover:active {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (@scrollbar_button_active_gradient_a),
to (@scrollbar_button_active_gradient_d));
}
scrollbar.vertical button,
scrollbar.vertical .button {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (@scrollbar_button_gradient_a),
to (@scrollbar_button_gradient_d));
}
scrollbar.vertical button:hover,
scrollbar.vertical .button:hover {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (@scrollbar_button_hover_gradient_d),
to (@scrollbar_button_hover_gradient_a));
}
scrollbar.vertical button:hover:active,
scrollbar.vertical .button:hover:active {
background-image: -gtk-gradient (linear,
left top,
right top,
from (@scrollbar_button_active_gradient_a),
color-stop (0.50, @scrollbar_button_active_gradient_b),
color-stop (0.50, @scrollbar_button_active_gradient_c),
to (@scrollbar_button_active_gradient_d));
}
scrollbar.vertical slider,
scrollbar.vertical .slider {
min-width: 14px;
min-height: 42px;
margin: 0px -1px 0px -1px;
}
scrollbar.horizontal slider,
scrollbar.horizontal .slider {
min-width: 42px;
min-height: 14px;
margin: -1px 0px -1px 0px;
}
scrollbar slider,
scrollbar .slider {
background-color: @scrollbar_slider_bg_color;
background-image: none;
border-radius: 0;
border-style: solid;
border-image: none;
border-color: @scrollbar_slider_border_color;
border-width: 1px;
}
scrollbar slider:hover,
scrollbar .slider:hover {
background-color: @scrollbar_slider_hover_bg_color;
}
scrollbar slider {
background-repeat: no-repeat;
background-position: center center;
}
scrollbar.vertical slider {
background-image: linear-gradient(to right,
alpha (@scrollbar_slider_inner_border_color, 0.5),
alpha (@scrollbar_slider_gradient_a, 0.5) 1px,
alpha (@scrollbar_slider_gradient_b, 0.5) 50%,
alpha (@scrollbar_slider_gradient_c, 0.5) 50%,
alpha (@scrollbar_slider_gradient_d, 0.5) 95%,
alpha (@scrollbar_slider_inner_border_color, 0.5)),
url("/opt/scripts/media/scrollbar/slider-vert-grip.png");
}
scrollbar.horizontal slider {
background-image: linear-gradient(to bottom,
alpha (@scrollbar_slider_inner_border_color, 0.5),
alpha (@scrollbar_slider_gradient_a, 0.5) 1px,
alpha (@scrollbar_slider_gradient_b, 0.5) 50%,
alpha (@scrollbar_slider_gradient_c, 0.5) 50%,
alpha (@scrollbar_slider_gradient_d, 0.5) 95%,
alpha (@scrollbar_slider_inner_border_color, 0.5)),
url("/opt/scripts/media/scrollbar/slider-horz-grip.png");
}
scrollbar.vertical slider:hover {
background-image: linear-gradient(to right,
alpha (@scrollbar_slider_inner_border_color, 0.5),
alpha (@scrollbar_slider_hover_gradient_a, 0.5) 1px,
alpha (@scrollbar_slider_hover_gradient_b, 0.5) 50%,
alpha (@scrollbar_slider_hover_gradient_c, 0.5) 50%,
alpha (@scrollbar_slider_hover_gradient_d, 0.5) 95%,
alpha (@scrollbar_slider_inner_border_color, 0.5)),
url("/opt/scripts/media/scrollbar/slider-vert-grip.png");
}
scrollbar.horizontal slider:hover {
background-image: linear-gradient(to bottom,
alpha (@scrollbar_slider_inner_border_color, 0.5),
alpha (@scrollbar_slider_hover_gradient_a, 0.5) 1px,
alpha (@scrollbar_slider_hover_gradient_b, 0.5) 50%,
alpha (@scrollbar_slider_hover_gradient_c, 0.5) 50%,
alpha (@scrollbar_slider_hover_gradient_d, 0.5) 95%,
alpha (@scrollbar_slider_inner_border_color, 0.5)),
url("/opt/scripts/media/scrollbar/slider-horz-grip.png");
}
/*********************
* GtkScale's slider *
*********************/
scale slider,
scale.horizontal slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz.png");
}
scale slider:hover,
scale.horizontal slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-hover.png");
}
scale slider:disabled,
scale.horizontal slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-insensitive.png");
}
scale.vertical slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert.png");
}
scale.vertical slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-hover.png");
}
scale.vertical slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-insensitive.png");
}
scale.horizontal.marks-before slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz.png");
}
scale.horizontal.marks-before slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-hover.png");
}
scale.horizontal.marks-before slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-insensitive.png");
}
scale.vertical.marks-before slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert.png");
}
scale.vertical.marks-before slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-hover.png");
}
scale.vertical.marks-before slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-insensitive.png");
}
scale.horizontal.marks-after slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz.png");
}
scale.horizontal.marks-after slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-hover.png");
}
scale.horizontal.marks-after slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-horz-insensitive.png");
}
scale.vertical.marks-after slider {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert.png");
}
scale.vertical.marks-after slider:hover {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-hover.png");
}
scale.vertical.marks-after slider:disabled {
background-image: url("/opt/scripts/media/scrollbar/scale-slider-vert-insensitive.png");
}Hopefully the above will work for you with only minimal alteration. The only thing you need to do for sure is get the few image files that are required (you can get them from my file storage here: http://files.dantas.airpost.net/public/scrollbar.tar.gz) and change every instance of /opt/scripts/media/scrollbar in the above code to where you put the image files on your system.
Enjoy!
P.S. It seems excessive to need so many lines of code for just a scrollbar, but I guess gtk programmers are not into golfing. (I fished out the code from a theme that gave me the scrollbar I wanted, so I'm not to blame for the verboseness )
#360 Re: Hardware & System Configuration » how to make Thinkpad's Thinklight brighter? » 2018-03-17 06:32:28
I tried booting a Linux Mint live image from USB stick. Same thinklight intensity, same directories in /sys/class/leds/ (i.e., some tpacpi::foo directories in there, but no tpacpi::thinklight).
The problem must be a bad LED or Libreboot bug. Sorry for the noise.
#361 Re: Hardware & System Configuration » how to make Thinkpad's Thinklight brighter? » 2018-03-17 05:44:30
I only know how to load a live image via the libreboot menu. Nevertheless, I'll try it and will report back.
#362 Re: Hardware & System Configuration » how to make Thinkpad's Thinklight brighter? » 2018-03-17 05:18:57
Good thought, golinux. Unfortunately, on a Libreboot system it is impossible to bypass Libreboot AFAIK, since it is Libreboot itself that loads live disks and passes on basic hardware data to them. (I think the same is true even for stock BIOS, but don't quote me bc I'm over my head in such low-level stuff.)
#363 Re: Hardware & System Configuration » how to make Thinkpad's Thinklight brighter? » 2018-03-17 02:28:48
Thanks, ralph.ronnquist. I hadn't looked in there. After reading your post I snooped around in that directory but didn't find anything related to the thinklight.
I did some more tests and realized that even while at the GRUB menu, I'm able to toggle the thinklight on and off and its intensity is identical to what is is while running Devuan ASCII, Debian Jessie, or Arch Linux. I think that pretty much rules out a system configuration or init issue.
Acpid and the kernel are probably completely unaware that the thinklight exists. I'm starting to think that the dim thinklight is due to either a BIOS bug (my laptop has Libreboot) or a bad LED.
#364 Hardware & System Configuration » how to make Thinkpad's Thinklight brighter? » 2018-03-16 19:45:35
- GNUser
- Replies: 7
I'm trying to make the ThinkLight brighter on my T400 ThinkPad, as it currently can be toggled on and off (via Fn + PgUp) but is so faint as to be totally useless. "ThinkLight" is the LED above the screen that can be used to illuminate the keyboard at night.
It looks like this: 
It would be nice to try editing the contents of /sys/class/leds/tpacpi:thinklight/brightness, except that this file does not exist on my system (it does exist on some systems according to this). In fact, even though acpid is running and thinkpad_acpi kernel module is loaded, I have no evidence that acpid can detect the thinklight (e.g., /sys/class/leds/tpacpi::thinklight directory does not exist even though other /sys/class/leds/tpacpi::foo directories do exist).
If I could make acpi detect the thinklight, perhaps /sys/class/leds/tpacpi:thinklight/brightness would appear, I could edit it, and find joy.
Does anyone know how to make acpid detect a component it seems to be ignoring (or how to make the Thinklight brighter through some other means)?
#365 Re: Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 16:54:20
golinux, I thought it was weird that you said "I am blind without seeing hidden files at all times" because this is the icon I had selected to show in my notification area when hidden files are being shown:
Haha, what are the odds?
#366 Re: Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 15:56:15
If I keep finding these annoying little bugs, I may eventually switch to XFCE, too. As much as I love MATE, it has definitely gotten sloppy.
Not to be ungrateful (MATE is both libre and gratis, after all), but you'd think that toggling hidden files and mounting run-of-the-mill Android phones are things that file managers should be able to do out-of-the-box these days, without nasty surprises.
#367 Re: Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 15:29:52
Thanks for your help, catprints. It was helpful to know that another Devuan ASCII + MATE user was experiencing the same thing, since that confirms that this is caused by a bug and not by some misconfiguration on my system.
This behavior bothers me enough that for the time being I've remapped control+h to run this script of mine:
#!/bin/sh
current_state=$(gsettings get org.mate.caja.preferences show-hidden-files)
if [ "$current_state" = "false" ]; then
gsettings set org.mate.caja.preferences show-hidden-files true # to show regular user's hidden files
sudo gsettings set org.mate.caja.preferences show-hidden-files true # to show root user's hidden files
else
gsettings set org.mate.caja.preferences show-hidden-files false
sudo gsettings set org.mate.caja.preferences show-hidden-files false
fiHere's a prettier version that puts an icon in the taskbar while hidden files/folders are visible (requires yad to be installed):
#!/bin/sh
icon=/path/to/your/icon.png
current_state=$(gsettings get org.mate.caja.preferences show-hidden-files)
if [ "$current_state" = "false" ]; then
gsettings set org.mate.caja.preferences show-hidden-files true # to show regular user's hidden files
sudo gsettings set org.mate.caja.preferences show-hidden-files true # to show root user's hidden files
yad --notification --image=$icon --text="Showing hidden files" --no-middle &
else
gsettings set org.mate.caja.preferences show-hidden-files false
sudo gsettings set org.mate.caja.preferences show-hidden-files false
pkill -f "Showing hidden files"
fiIt's a workaround and not a fix, of course, but I want the unexpected teleports to other filesystem locations to stop right away. Hopefully a caja expert will come along and offer us a proper fix.
#368 Re: Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 14:36:14
I reinstalled caja and it made no difference 
#369 Re: Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 14:33:05
I will try reinstalling, wouldn't hurt.
Expected behavior when I press control + h in the file manager is to toggle visibility of hidden files and directories in the directory I'm in, not to take me to another directory (/proc, /, or anywhere else).
When you press control + h caja takes you to file systems? That's unexpected behavior, similar to what I'm experiencing.
#370 Desktop and Multimedia » toggling hidden files in caja changes directory to /proc or / » 2018-03-14 12:24:41
- GNUser
- Replies: 10
I noticed a strange bug in caja. If I'm inside a hidden directory (e.g., ~/.config) and toggle hidden files by pressing control + h, caja changes directory to /proc or / (root directory). This is quite disorienting.
I have absolutely no idea how to begin troubleshooting this. Any ideas? I hope one of you guys can help, as I don't think a MATE-specific forum exists anymore (notice the forums listed here: https://mate-desktop.org/community/).
Details:
Devuan ASCII
MATE version 1.16.2
Caja version 1.16.6-1+deb9u1
P.S. I also asked in the debian forum (for more eyeballs). The post is here: http://forums.debian.net/viewtopic.php? … 46&start=0
#371 Re: Desktop and Multimedia » mtp device shown twice when plugged into ascii laptop » 2018-03-12 19:13:01
A quick follow-up:
When my Android phone is mounted by jmtpfs, I can perform all these operations from within the file manager (caja) on my Devuan laptop without any problems:
- copy and paste files in either direction (phone <-> laptop)
- cut and paste files in either direction (phone <-> laptop)
- create new files on the phone
- delete files from the phone
- open and view files on the phone
However, jmtpfs mounts the phone in such a way that GUI applications such as pluma cannot modify files on the phone--I am able to start editing files that are on the phone, but I get an I/O error when I try to save the modified file. I did some duck-ducking and it seems this a known mtp limitation (https://askubuntu.com/questions/284762/ … why/421503).
Interestingly, gvfs (when it works) mounts my phone in such a way that pluma and other GUI applications can modify and save files on the phone. How does gvfs-mtp-volume-monitor magically work around an mtp limitation? I'd love to learn the trick so that I can implement it in my workaround. Anybody know?
#372 Re: Other Issues » policykit-1, polkit, polkitd authentication problems » 2018-03-07 20:12:34
rfgmm, when I installed ascii then mate desktop, I was having similar problems. Polkit was installed but the system would not allow me (as regular user) to mount or unmount usb drives, nor shutdown/reboot using the power button on my taskbar.
For me, the solution was to install these two packages: libpolkit-backend-1-0-elogind libpolkit-gobject-1-0-elogind and reboot.
#373 Re: Desktop and Multimedia » alternative to mate-power-manager for ascii? [SOLVED] » 2018-03-04 03:24:03
Got it. Thanks.
#374 Re: Desktop and Multimedia » alternative to mate-power-manager for ascii? [SOLVED] » 2018-03-04 00:43:03
Thanks for clarifying, catprints. Oops, I guess this whole thread was moot. Yes, I can see mate-power-manager-common is available for installation. I had assumed that mate-power-manager-common was a dependency and that mate-power-manager (which I couldn't find) was the main package. I feel silly.
Nevertheless, since we are on the topic, this is my /etc/apt/sources.list:
deb http://pkgmaster.devuan.org/merged/ ascii main
deb http://pkgmaster.devuan.org/merged/ ascii-security main
deb http://pkgmaster.devuan.org/merged/ ascii-updates mainHow are http://deb.devuan.org/merged/ and http://pkgmaster.devuan.org/merged different? Is one more "correct"?
#375 Re: Desktop and Multimedia » how to unmount fuse mount using desktop icon? » 2018-03-03 15:08:06
Thanks, fsmithred. I did solve it that way (with .desktop file that runs the fusermount command). Take a look at the link in first post.
Board footer
