Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX-19 Beta 2.1 Feedback

User avatar
dolphin_oracle
Developer
Posts: 12593
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-19 Beta 2.1 Feedback

#291

Post by dolphin_oracle » Fri Sep 13, 2019 2:36 pm

Gerson wrote:
Fri Sep 13, 2019 1:50 pm
I don't know if it's already reported but since beta 1 when the command to restart or turn off is given, the Login screen appears for a few seconds and confuses. You should execute the command without that screen appearing.
This will not change. Its due to sysVinit and the way the init scripts for lightdm work.

booting with systemd does not produce this.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-18.3
lenovo s21e - antiX-19 beta 2 (live-USB)
FYI: mx "test" repo is not the same thing as debian testing repo.

slipperyslope
Forum Novice
Forum  Novice
Posts: 7
Joined: Sat Feb 03, 2018 2:56 pm

Re: MX-19 Beta 2.1 Feedback

#292

Post by slipperyslope » Fri Sep 13, 2019 4:39 pm

Clipgrab install via stable repo impacts ublock origin ad blocker and foxnew.com. Videos, specifically from foxnews.com just spin and don't play. If you are syncing all your devices, the problem will move to all synced devices. i uninstalled Clipgrab, but issue remained. I turned off ublock origin ad blocker and the site worked. I purged all cache in Ublock origin and re-updated the Ublock Origin cache which has fixed my issue, minus Clipgrab of course. I also change how I sync devices. The issue ranges across chromium and firefox browsers when you install Clipgrab from stable repo with Ublock Origin ad blocker running. All videos from foxnews.com fail to load until you uninstall Clipgrab, purge Ublock Origin Ad blocker cache and re-update the ublock Origin cache. 09/14/19 I have noted the new MX Linux Beta2.1 is running Advert-Block-antiX by default, but do no know if this is causing any conflict.

Code: Select all

-----------------------------------------------------------
MXPI SESSION                   
-----------------------------------------------------------
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  ffmpeg libavdevice58 libminizip1 libqt5quickwidgets5 libqt5webengine-data
  libqt5webenginecore5 libqt5webenginewidgets5 libre2-5
Suggested packages:
  ffmpeg-doc
The following NEW packages will be installed:
  clipgrab ffmpeg libavdevice58 libminizip1 libqt5quickwidgets5
  libqt5webengine-data libqt5webenginecore5 libqt5webenginewidgets5 libre2-5
0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 37.0 MB of archives.
After this operation, 133 MB of additional disk space will be used.
Do you want to continue? [Y/n] Get:1 http://mxrepo.com/mx/repo buster/main amd64 clipgrab amd64 3.8.4-1~mx19+1 [292 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 libqt5webengine-data all 5.11.3+dfsg-2 [5,105 kB]
Get:3 http://deb.debian.org/debian buster/main amd64 libminizip1 amd64 1.1-8+b1 [20.4 kB]
Get:4 http://deb.debian.org/debian buster/main amd64 libre2-5 amd64 20190101+dfsg-2 [161 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 libqt5webenginecore5 amd64 5.11.3+dfsg-2+b1 [29.7 MB]
Get:6 http://deb.debian.org/debian buster/main amd64 libqt5quickwidgets5 amd64 5.11.3-4 [50.6 kB]
Get:7 http://deb.debian.org/debian buster/main amd64 libqt5webenginewidgets5 amd64 5.11.3+dfsg-2+b1 [136 kB]
Get:8 http://deb.debian.org/debian buster/main amd64 libavdevice58 amd64 7:4.1.4-1~deb10u1 [114 kB]
Get:9 http://deb.debian.org/debian buster/main amd64 ffmpeg amd64 7:4.1.4-1~deb10u1 [1,425 kB]
Fetched 37.0 MB in 4s (9,134 kB/s)
Selecting previously unselected package libqt5webengine-data.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 278894 files and directories currently installed.)
Preparing to unpack .../0-libqt5webengine-data_5.11.3+dfsg-2_all.deb ...
Unpacking libqt5webengine-data (5.11.3+dfsg-2) ...
Selecting previously unselected package libminizip1:amd64.
Preparing to unpack .../1-libminizip1_1.1-8+b1_amd64.deb ...
Unpacking libminizip1:amd64 (1.1-8+b1) ...
Selecting previously unselected package libre2-5:amd64.
Preparing to unpack .../2-libre2-5_20190101+dfsg-2_amd64.deb ...
Unpacking libre2-5:amd64 (20190101+dfsg-2) ...
Selecting previously unselected package libqt5webenginecore5:amd64.
Preparing to unpack .../3-libqt5webenginecore5_5.11.3+dfsg-2+b1_amd64.deb ...
Unpacking libqt5webenginecore5:amd64 (5.11.3+dfsg-2+b1) ...
Selecting previously unselected package libqt5quickwidgets5:amd64.
Preparing to unpack .../4-libqt5quickwidgets5_5.11.3-4_amd64.deb ...
Unpacking libqt5quickwidgets5:amd64 (5.11.3-4) ...
Selecting previously unselected package libqt5webenginewidgets5:amd64.
Preparing to unpack .../5-libqt5webenginewidgets5_5.11.3+dfsg-2+b1_amd64.deb ...
Unpacking libqt5webenginewidgets5:amd64 (5.11.3+dfsg-2+b1) ...
Selecting previously unselected package libavdevice58:amd64.
Preparing to unpack .../6-libavdevice58_7%3a4.1.4-1~deb10u1_amd64.deb ...
Unpacking libavdevice58:amd64 (7:4.1.4-1~deb10u1) ...
Selecting previously unselected package ffmpeg.
Preparing to unpack .../7-ffmpeg_7%3a4.1.4-1~deb10u1_amd64.deb ...
Unpacking ffmpeg (7:4.1.4-1~deb10u1) ...
Selecting previously unselected package clipgrab.
Preparing to unpack .../8-clipgrab_3.8.4-1~mx19+1_amd64.deb ...
Unpacking clipgrab (3.8.4-1~mx19+1) ...
Setting up libqt5webengine-data (5.11.3+dfsg-2) ...
Setting up libminizip1:amd64 (1.1-8+b1) ...
Setting up libqt5quickwidgets5:amd64 (5.11.3-4) ...
Setting up libavdevice58:amd64 (7:4.1.4-1~deb10u1) ...
Setting up libre2-5:amd64 (20190101+dfsg-2) ...
Setting up ffmpeg (7:4.1.4-1~deb10u1) ...
Setting up libqt5webenginecore5:amd64 (5.11.3+dfsg-2+b1) ...
Setting up libqt5webenginewidgets5:amd64 (5.11.3+dfsg-2+b1) ...
Setting up clipgrab (3.8.4-1~mx19+1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...


Last edited by slipperyslope on Sat Sep 14, 2019 12:43 pm, edited 3 times in total.

User avatar
fehlix
Developer
Posts: 4942
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-19 Beta 2.1 Feedback

#293

Post by fehlix » Fri Sep 13, 2019 5:18 pm

attila123 wrote:
Fri Sep 13, 2019 2:24 pm
MX-19 Beta 2.1 installing to a partition on MBR did not add the boot flag
Hi, I did an installation to an existing MBR partition table (which had 3 partitions). During installation I launched gparted and manually deleted sda1, which was an old system partition (so at this point it lost the boot flag).
Then, when asked, I did the manual setting, and set sda1 to the root partition and chose to install grub to the MBR. The installer installed the system correctly to sda1, but did not set the boot flag on sda1. So the system was not bootable (because the BIOS did not find the bootable flag on any partition). It was confusing and it took me some time to realize what the problem may be. When I got the idea, I rebooted to the live system and manually added the bootable flag to sda1 (using fdisk), and finally I could boot into the installed system.
Confirmed. I have installed twice: one way as described above, and a 2nd way just reinstall at the same partition. In both cases the partition did no get a boot flag. OK, my bios booted without the boot-flag. But indeed this might be problematic for older BIOS, which do resist booting from a not-marked-as-boot partition. Even GRUB is happy to boot from such a partition, BIOS might simply assume no bootable partition exists.
So, one workaround for now would be to just select Boot Rescue Menu and search for the Grub-loader to boot from.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Ken S
Forum Novice
Forum  Novice
Posts: 1
Joined: Fri Sep 13, 2019 6:18 pm

Re: MX-19 Beta 2.1 Feedback

#294

Post by Ken S » Fri Sep 13, 2019 6:38 pm

System loaded really nice and smooth.after 1st update and upgrade was done ,I took a chance that my system could run the 5.2.9 or was it the 5.3 kernel.I am currently running 5.2.11-1 on another distro on this same disk.

I was wondering what if any problems I should be looking for.So far everything has run like a clock.Steam games run really well,but I will try codex updater to compare later.
Keep up the great work.
PS: the kernel installed was 5.2.0-13.3-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0

User avatar
chrispop99
Global Moderator
Posts: 3110
Joined: Tue Jan 27, 2009 3:07 pm

Re: MX-19 Beta 2.1 Feedback

#295

Post by chrispop99 » Sat Sep 14, 2019 4:37 am

fehlix wrote:
Fri Sep 13, 2019 5:18 pm
attila123 wrote:
Fri Sep 13, 2019 2:24 pm
MX-19 Beta 2.1 installing to a partition on MBR did not add the boot flag
Hi, I did an installation to an existing MBR partition table (which had 3 partitions). During installation I launched gparted and manually deleted sda1, which was an old system partition (so at this point it lost the boot flag).
Then, when asked, I did the manual setting, and set sda1 to the root partition and chose to install grub to the MBR. The installer installed the system correctly to sda1, but did not set the boot flag on sda1. So the system was not bootable (because the BIOS did not find the bootable flag on any partition). It was confusing and it took me some time to realize what the problem may be. When I got the idea, I rebooted to the live system and manually added the bootable flag to sda1 (using fdisk), and finally I could boot into the installed system.
Confirmed. I have installed twice: one way as described above, and a 2nd way just reinstall at the same partition. In both cases the partition did no get a boot flag. OK, my bios booted without the boot-flag. But indeed this might be problematic for older BIOS, which do resist booting from a not-marked-as-boot partition. Even GRUB is happy to boot from such a partition, BIOS might simply assume no bootable partition exists.
So, one workaround for now would be to just select Boot Rescue Menu and search for the Grub-loader to boot from.
:puppy:
I have this issue with a couple of older machines. I thought I had reported it during Alpha testing, but maybe not.

Chris
Test machines:
32-bit non-PAE - Thinkpad T41, 1.6GHz Pentium M, 1GB RAM.
32-bit PAE - DELL Latitude D610, 1.73GHz Pentium M, 2GB RAM.
64-bit - Lenovo T61, 2GHz Core 2 Duo, 2GB RAM
64-bit - Gigabyte Z77P-D3, Intel i3-3220, GeForce 8400 GS, 4GB PC3-12800.

User avatar
bubba66
Forum Novice
Forum  Novice
Posts: 7
Joined: Tue Mar 12, 2019 4:59 pm

Re: MX-19 Beta 2.1 Feedback

#296

Post by bubba66 » Sat Sep 14, 2019 5:38 am

I have installed this on my Dell 3162-11 so far no problems.

Code: Select all

System:    Host: djh Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Portable System: Dell product: Inspiron 11-3162 v: 2.4.0 serial: <filter> 
           Chassis: type: 8 serial: <filter> 
           Mobo: Dell model: 0P6GKN v: A00 serial: <filter> UEFI: Dell v: 2.4.0 date: 01/31/2018 
Battery:   ID-1: BAT0 charge: 27.2 Wh condition: 27.2/32.0 Wh (85%) volts: 8.6/7.6 
           model: Samsung SD DELL PGYK55C type: Unknown serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont 
           family: 6 model-id: 4C (76) stepping: 3 microcode: 368 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 
           Speed: 480 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 480 2: 480 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated 
           Graphics 
           vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:22b1 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (Braswell) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High 
           Definition Audio 
           vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2284 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0 
           chip ID: 8086:08b3 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 87.36 GiB used: 5.27 GiB (6.0%) 
           ID-1: /dev/mmcblk0 model: DF4032 size: 29.12 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 0x8 scheme: GPT 
           ID-2: /dev/sda type: USB vendor: Generic model: SD MMC MS PRO size: 58.24 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 26.84 GiB size: 26.29 GiB (97.96%) used: 5.27 GiB (20.0%) fs: ext4 
           dev: /dev/mmcblk0p2 
           ID-2: swap-1 size: 2.00 GiB used: 768 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/mmcblk0p3 
Sensors:   System Temperatures: cpu: 34.0 C mobo: 31.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 175 Uptime: 2h 49m Memory: 1.85 GiB used: 584.1 MiB (30.9%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.33 
Regards

DH - user of low end devices - :bagoverhead:

berlin59
Forum Novice
Forum  Novice
Posts: 16
Joined: Wed Nov 08, 2017 4:29 pm

Re: MX-19 Beta 2.1 Feedback

#297

Post by berlin59 » Sat Sep 14, 2019 5:57 am

VLC-Player only works once, then it is impossible to play another mp4-Video with it.
I have to log out and log in to MX-19 Beta 2.1 in order to play another Video.

When first clicked, the VLC-Player puts an icon into the task-panel as shown in the screenshot below.
Image
That icon is telling me: it is over with VLC-Player now, because it cannot be closed anymore. Neither with the TaskManager, nor by right-clicking on the icon and clicking on "close" in the popup-menu of the VLC-icon. Only restarting MX-19 helps.

I installed SMPlayer to check another software. It works fine.
I uninstalled VLC-Player completely and re-installed it with Synaptic, but it produces the same error.

Code: Select all

inxi -F 
System:    Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
Machine:   Type: Desktop System: Dell product: Inspiron 560 v: 00 serial: <root required> 
           Mobo: Dell model: 0K83V0 v: A00 serial: <root required> BIOS: Dell v: A06 
           date: 12/01/2010 
CPU:       Topology: Dual Core model: Pentium E5400 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1242 MHz min/max: 1203/2700 MHz Core speeds (MHz): 1: 1580 2: 1500 
Graphics:  Device-1: AMD Redwood XT [Radeon HD 5670/5690/5730] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1200~60Hz 
           OpenGL: renderer: AMD REDWOOD (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 
Audio:     Device-1: Intel 82801JI HD Audio driver: snd_hda_intel 
           Device-2: AMD Redwood HDMI Audio [Radeon HD 5000 Series] driver: snd_hda_intel 
           Device-3: Microsoft LifeCam VX-2000 type: USB driver: snd-usb-audio,uvcvideo 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:25:64:83:f0:f0 
Drives:    Local Storage: total: 465.76 GiB used: 206.50 GiB (44.3%) 
           ID-1: /dev/sda vendor: Samsung model: HD503HI size: 465.76 GiB 
Partition: ID-1: / size: 25.70 GiB used: 9.90 GiB (38.5%) fs: ext4 dev: /dev/sda11 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: radeon temp: 50 C 
           Fan Speeds (RPM): cpu: 494 mobo: 856 
Info:      Processes: 200 Uptime: 6h 22m Memory: 3.85 GiB used: 1.30 GiB (33.7%) Shell: bash 
           inxi: 3.0.33 

User avatar
Eadwine Rose
Administrator
Posts: 9407
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 2.1 Feedback

#298

Post by Eadwine Rose » Sat Sep 14, 2019 6:07 am

Can you start it through the terminal and see what messages you get?


Just tried this on a vanilla install, only changed monitor positions. For me it does play multiple times, however it starts funny with some screenresize funkiness.


Terminal output (start VLC, play a file, close VLC) is giving this:

Code: Select all

eadwine@eadwinemx19beta2.1:~
$ vlc
VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
[000055ce7557c570] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[000055ce75580530] 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/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007f8d38002d80] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
[00007f8d44049de0] main video output error: video output creation failed
[00007f8d4c1dc5c0] main decoder error: failed to create video output
[00007f8d4c1dc5c0] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
[h264 @ 0x7f8d4c1feec0] Failed setup for format vdpau: hwaccel initialisation returned error.
[00007f8d4c1dc5c0] avcodec decoder error: existing hardware acceleration cannot be reused
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/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007f8d38002d80] 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/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
[00007f8d38002d80] glconv_vaapi_x11 gl error: vaDeriveImage: invalid VASurfaceID
[00007f8d44091120] main video output error: video output creation failed
[00007f8d4c1dc5c0] main decoder error: failed to create video output
QObject::~QObject: Timers cannot be stopped from another thread
eadwine@eadwinemx19beta2.1:~
MX-18.3_x64 May 26 2019 * 4.19.0-5-amd64 ext4 Xfce 4.12.3 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 390.116 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy5030

User avatar
Eadwine Rose
Administrator
Posts: 9407
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 2.1 Feedback

#299

Post by Eadwine Rose » Sat Sep 14, 2019 6:19 am

Made a video of the screensize funkiness. I started VLC by clicking the video file in Thunar and this is what happens:

https://youtu.be/F7--pXNlz7U
MX-18.3_x64 May 26 2019 * 4.19.0-5-amd64 ext4 Xfce 4.12.3 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 390.116 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy5030

User avatar
Eadwine Rose
Administrator
Posts: 9407
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 2.1 Feedback

#300

Post by Eadwine Rose » 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.
You do not have the required permissions to view the files attached to this post.
MX-18.3_x64 May 26 2019 * 4.19.0-5-amd64 ext4 Xfce 4.12.3 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 390.116 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy5030

Post Reply

Return to “General”