Page 31 of 60
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 9:13 am
by dolphin_oracle
Eadwine Rose wrote: Sat Sep 14, 2019 8:54 am
Found something else. When I am in Thunar in a folder that I want to open a root Thunar in, when that folder's name I am in has spaces I get an error message.
Start Thunar, create a new folder in Documents, called New Folder. Whatever works, just it has to have a space in it.
Now when you go into Documents and right click open root thunar here it works just fine.
Go into the New Folder, do the same, it will let you enter your password, and then this appears:
Screenshot.png
Navigating with a root thunar to that folder works just fine, as long as you open that root thunar like above in a nospaces name folder.
nice find. easy fix. I'll fix for next iso, but in the mean time, edit the "Open root thunar here" custom action and change the command to
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 9:29 am
by Eadwine Rose
Easy fix indeed :)
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 9:30 am
by AK-47
dolphin_oracle wrote: Sat Sep 14, 2019 9:13 amnice find. easy fix. I'll fix for next iso, but in the mean time, edit the "Open root thunar here" custom action and change the command to
That will give you the same problem, so best to put the quote around just the "%f" bit.
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 9:36 am
by Eadwine Rose
Hmm DO's fix worked for me though? Weird!
Another thing I am seeing is two volume icons in the notification area, both muted when I log in (not always though!). I thought to look in session and autostart, maybe two were there but nope. Saving a session with one removed doesn't seem to help.
Maybe something to do with start volumeicon after pulseaudio?
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 10:34 am
by berlin59
Starting VLC with the terminal does work.
A second VLC icon appears in the task-panel.
From the VLC window I can then open different videos and they play.
After closing the VLC window, the icon remains. Right now I have 3 VLC-icons which cannot be deleted.
Here is the terminal-output where I opened 3 different videos , then I closed the vlc-window.
Code: Select all
franz@mx:~
$ vlc
VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
[00005570437e4570] main libvlc: VLC wird mit dem Standard-Interface ausgeführt. Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
[00005570437e8530] main playlist: playlist is empty
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007fc7c76441b0] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
[000055704389a0b0] main video output error: video output creation failed
[00007fc7c759db20] main decoder error: failed to create video output
[00007fc7c759db20] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007fc7d01d7430] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007fc7d024af40] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
[00007fc80006af10] main video output error: video output creation failed
[00007fc7d6616e60] main decoder error: failed to create video output
[00007fc7d6616e60] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007fc7d024af40] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007fc7cc0071b0] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
[00007fc7c75cbee0] main video output error: video output creation failed
[00007fc7b8417820] main decoder error: failed to create video output
[00007fc7b8417820] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 11:00 am
by Eadwine Rose
What happens when in a terminal:
Does this get rid of the icons? No need to be root, sorry about that.
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 11:09 am
by berlin59
Yes.
killall -9 vlc removes all vlc icons from the task-panel.
Thanks for that.
After having the icons removed, I can start vlc with right-clicking on a video-file once.
Looks like the icons somehow block vlc ?
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 11:30 am
by Eadwine Rose
The fact that you see an icon means that VLC is still running, so it won't start a new instance until the first one stops.
Or something like that anyway
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 12:49 pm
by davemx
I cannot get xsetwacom --list to list my Tablet devices in MX19ß2.1 — and as it does not find the devices, it cannot set the button presses to something useful.
It works in MX18.3 and it worked in the first beta of MX19.
The correct driver for the HUION H610 is hid_uclogic, and even preloading the module in /etc/modules-load.d/ makes no difference.
I have the file 60-digimend.conf in /usr/share/X11/xorg.conf.d and its code is as follows:
Code: Select all
#
# InputClass sections for some tablets supported by the DIGImend kernel
# drivers. Organized into separate InputClass sections based on (one of) the
# advertised brands. Mostly because the MatchUSBID options would become too
# long otherwise.
#
Section "InputClass"
Identifier "Huion tablets with Wacom driver"
MatchUSBID "5543:006e|256c:006e"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Ugee/XP-Pen tablets with Wacom driver"
MatchUSBID "28bd:007[145]|28bd:0094|28bd:0042|5543:004[57]|5543:0081|5543:0004|5543:3031"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Ugtizer tablets with Wacom driver"
MatchUSBID "2179:0053"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Yiynova tablets with Wacom driver"
MatchUSBID "5543:004d"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
The HUION H610 is device 256c:006e, so it should be picked up every time X starts.
Re: MX-19 Beta 2.1 Feedback
Posted: Sat Sep 14, 2019 12:52 pm
by anticapitalista
davemx wrote: Sat Sep 14, 2019 12:49 pm
I cannot get xsetwacom --list to list my devices in MX19ß2.1 — and as it does not find the devices, it cannot set the button presses to something useful.
It works in MX18.3 and it worked in the first beta of MX19.
Just wondering, does it work on antiX?