MX-19 Beta 2.1 Feedback

[zebedeeboss]

Hi

OBS-Studio is not offering nvenc enccoding, even though nvenc is installed. obs v 0.01 (64 bit)

and the snap states Failed to initialize video. Your GPU may not be supported, or your graphics drivers may need to be updated.

Regards Zeb...
...

Debian's ffmpeg, which is all we have at the present in MX 19, probably doesn't build with nvenc support because it needs non-free packages. I'll see what we need to do to add the support, but we may then need to put our ffmeg into the non-free section (enabled by default, anyway). Ffmpeg is supposed to add the support automatically if it detects the correct Nvidia headers are installed.

It was working in 18.3 with no additional work required by the end user.

Regards Zeb...

[dolphin_oracle]

Hi

OBS-Studio is not offering nvenc enccoding, even though nvenc is installed. obs v 0.01 (64 bit)

and the snap states Failed to initialize video. Your GPU may not be supported, or your graphics drivers may need to be updated.

Regards Zeb...
...

Debian's ffmpeg, which is all we have at the present in MX 19, probably doesn't build with nvenc support because it needs non-free packages. I'll see what we need to do to add the support, but we may then need to put our ffmeg into the non-free section (enabled by default, anyway). Ffmpeg is supposed to add the support automatically if it detects the correct Nvidia headers are installed.

It was working in 18.3 with no additional work required by the end user.

Regards Zeb...

Yep, that's because we rebuilt ffmpeg. should be seeing a new build of ffmpeg "soonish".

[zebedeeboss]

Debian's ffmpeg, which is all we have at the present in MX 19, probably doesn't build with nvenc support because it needs non-free packages. I'll see what we need to do to add the support, but we may then need to put our ffmeg into the non-free section (enabled by default, anyway). Ffmpeg is supposed to add the support automatically if it detects the correct Nvidia headers are installed.

It was working in 18.3 with no additional work required by the end user.

Regards Zeb...

Yep, that's because we rebuilt ffmpeg. should be seeing a new build of ffmpeg "soonish".

Awesome, thank you

Regards Zeb...

[chrispop99]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

This is broken in MX-19; the function key settings are not respected as the clocks display in 12 hour format, and at the installer screen the 12 hour radio button is pre-set.

Running live in MX-18, issuing 'timedatecl' show this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
      Local time: Tue 2019-09-17 08:33:30 BST
  Universal time: Tue 2019-09-17 07:33:30 UTC
        RTC time: Tue 2019-09-17 07:33:30
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

Whereas in MX-19, running live or installed, 'timedatectl' shows this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down


Chris

[mystic]

LibreOffice is not launching in the live usb.

[chrispop99]

LibreOffice is not launching in the live usb.

Confirmed. Launching from a terminal gives a fatal exception error. It works fine installed.

(I can't believe I hadn't noticed this before!)

Chris

[AK-47]

Try disabling some of the LibreOffice AppArmor profiles:

Code: Select all

sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.oosplash /etc/apparmor.d/disable/
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin /etc/apparmor.d/disable/
sudo aa-teardown
sudo service apparmor restart

I'm at a loss as to why it doesn't work on the live system, but works perfectly on the installed system.

[Jerry3904]

Time zone regression

In MX-18 and earlier versions, using the function keys at the boot screen to set Language to UK, and Time Zone to London allowed the Conky clock and the panel clock to display correctly in 24 hour format. During installation, on the 'Locale...' screen, the 'Configure clock' radio button was correctly pre-set to 24 hour format.

This is broken in MX-19; the function key settings are not respected as the clocks display in 12 hour format, and at the installer screen the 12 hour radio button is pre-set.

Running live in MX-18, issuing 'timedatecl' show this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
      Local time: Tue 2019-09-17 08:33:30 BST
  Universal time: Tue 2019-09-17 07:33:30 UTC
        RTC time: Tue 2019-09-17 07:33:30
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

Whereas in MX-19, running live or installed, 'timedatectl' shows this:

Code: Select all

demo@mx1:~/Desktop
$ timedatectl
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down


Chris

Running b2 installed it works here:

Code: Select all

$ timedatectl
               Local time: Tue 2019-09-17 06:58:43 EDT
           Universal time: Tue 2019-09-17 10:58:43 UTC
                 RTC time: Tue 2019-09-17 10:58:43
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

[karieho]

I can’t run Pixeluvo from menu.
It can run from console when first run export OPENSSL_CONF=/etc/ssl/
How can this issue fix permanent?

[Jerry3904]

I never even heard of this, but I downloaded it and found this: right-clicked the menu entry > Edit Application, and checked the box to open in a terminal. Saw a quick message "Using System Qt Libraries" and after that the application launched correctly from the menu. Once. After that no longer worked from the menu or from a terminal.

Since "blobs" like this are typically located in /opt, I looked there and sure enough it was there, and the executable was in /bin. So now we can fix the problem: right-click the menu entry > Edit Application, and paste this into the Command box:

Code: Select all

/opt/pixeluvo/bin/Pixeluvo64

Ta-da! Very handsome, but since I'm not going to buy it:

Code: Select all

sudo apt purge pixeluvo -y