[Ubuntu-x-swat] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning

2021-05-27 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => libx11 (Ubuntu)

** Also affects: grub2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: openssh (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1929854

Title:
  Vital and critical configuration files get overridden by system
  updates without warning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1929815] Re: intel-vaapi-driver conflicts with window manager compiz in plugin scale

2021-05-27 Thread Daniel van Vugt
> If i check vaapi with intel-gpu-tools with the command intel_gpu_top
> it seems that gstreamer is using the Engines Render/3D Blitter and
> Video for hardware decoding, whereas vlc and mpv only uses the Engines
> Render/3D and Video for hardware decoding.
> The Engine Blitter is not used.

That part is probably not a bug. A well-written player ideally should
not be using the Blitter. You just need 'Video' for decoding the video
and 'Render/3D' for putting it on screen. Using 'Blitter' possibly means
gstreamer is using too much software rendering, somewhere. That's a bug
in gstreamer.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1929815

Title:
  intel-vaapi-driver conflicts with window manager compiz in plugin
  scale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1929815/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-05-27 Thread jeremyszu
** Tags added: originate-from-1929152 stella

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1929815] Re: intel-vaapi-driver conflicts with window manager compiz in plugin scale

2021-05-27 Thread Daniel van Vugt
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1929815

Title:
  intel-vaapi-driver conflicts with window manager compiz in plugin
  scale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1929815/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24

2021-05-27 Thread Erich Eickmeyer 
** Summary changed:

- Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146

Title:
  Please SRU nvidia-modprobe 465.24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73

2021-05-27 Thread Erich Eickmeyer 
** Changed in: nvidia-settings (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-settings (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-settings (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146

Title:
  Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning

2021-05-27 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1929854

Title:
  Vital and critical configuration files get overridden by system
  updates without warning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1929854/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1929854] [NEW] Vital and critical configuration files get overridden by system updates without warning

2021-05-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

• In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of 
special compose keys defined.
• In my /boot/grub/grub.cfg I have a very complicated special setup for my 
various boot configurations, and a 5-sec timout for my EFI-config.
• My /etc/ssh/sshd_config contains a well-balanced configuration 

All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
or ASKING BACK by ubuntu system setups (discover).

I set all of them to read-only by root and no-access for group and other
users, but they still get overridden by every other system update.  I
even have a shutdown process in place which should actually make sure
that changes to these files are reverted by writing a backup copy over
any newly installed override — unfortunately, everything I did to run
either a custom shutdown process or a startup process with systemd
turned out to not work and be a nightmare to make work.

How somebody could be as bold as to override vital configuration files
like this without even asking  for consent is one of the strange
miracles in this world which I'll probably never understand.  However,
if "ubuntu" is really what it translates to, it should take a little bit
more care about pre-existing configurations on systems on which it is
set up and running well — until one system update suddenly jeopardizes
the functioning of the entire system.  I'm pretty sure these are not the
only configuration files which are carelessly just overridden.  They're
just the ones every other update breaks my system and inflinges on my
the costs of hours of research until I find out that — of course — it
was an overridden critical system configuration again.  The really mean
thing is that you don't notice anything when you run the update … only
next time you start your system and of course are not aware anymore that
you did a system update, the new (absolutely wrong and/or insufficent)
settings are in place and shoot you in the leg.

Take an example from gentoo's etc-update feature which lets you merge
new configuration files with pre-existing ones using a diff3-update.  I
went away from gentoo for other reasons, but I always praised that
feature.

Please make sure immediately that critical configuration files do not
get overridden if they are non-writable by root, and then gradually
introduce a system that merges changes to configuration files with the
current situation on the target system.  Or at least present the configs
that would be changed in a particular directory, so that anybody who is
interested in preserving local settings could merge them in a suitable
way.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu May 27 18:48:15 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
InstallationDate: Installed on 2021-01-15 (132 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20QQS0KL13
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic 
root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET38W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QQS0KL13
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: ZF211710
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QQS0KL13
dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: 

[Ubuntu-x-swat] [Bug 1929815] [NEW] intel-vaapi-driver conflicts with window manager compiz in plugin scale

2021-05-27 Thread Heinz Assmus
Public bug reported:

I'm using Ubuntu 20.04 MATE with window manager compiz and 4 screens with 
compiz plugins Expo and Desktop Wall with hot corners for Scale-plugin.
Hardware accellerated videos with mpv and vlc leads to stuttering previews in 
scale function in overview for all windows when the actice screen is not the 
screen where the active porgram (mpv or vlc) was started.
In Terminal both programs gives several failure messages (see adendon).
If i play the same video with gstreamer gst-play-1.0 the video runs fine in all 
screens when Scale gives an overview of all windows of all workspaces.
If i check vaapi with intel-gpu-tools with the command intel_gpu_top it seems 
that gstreamer is using the Engines Render/3D  Blitter and Video for hardware 
decoding, whereas vlc and mpv only uses the Engines Render/3D and Video for 
hardware decoding.
The Engine Blitter is not used.

Terminal messages:

tux@tux-Aspire-V5-573G:~/Videos$ gst-play-1.0 
hr__tierisch-schlau-waschbaeren3-banse_syn2_1920x1080-50p-8000kbit.mp4
Geben Sie »k« ein, um die Liste der Tastenkombinationen zu sehen.
Momentan wird 
/home/tux/Videos/hr__tierisch-schlau-waschbaeren3-banse_syn2_1920x1080-50p-8000kbit.mp4
 wiedergegeben
Redistribute latency...
Redistribute latency...
0:01:02.6 / 0:04:52.1   
tux@tux-Aspire-V5-573G:~/Videos$ mpv 
hr__tierisch-schlau-waschbaeren3-banse_syn2_1920x1080-50p-8000kbit.mp4
 (+) Video --vid=1 (*) (h264 1920x1080 50.000fps)
 (+) Audio --aid=1 (*) (aac 2ch 48000Hz)
[vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
Using hardware decoding (vaapi).
AO: [pulse] 48000Hz stereo 2ch float
VO: [gpu] 1920x1080 vaapi[nv12]
AV: 00:00:04 / 00:04:52 (2%) A-V:  0.000

Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).

AV: 00:00:44 / 00:04:52 (15%) A-V:  0.000 Dropped: 1605

Exiting... (Quit)
tux@tux-Aspire-V5-573G:~/Videos$ vlc 
hr__tierisch-schlau-waschbaeren3-banse_syn2_1920x1080-50p-8000kbit.mp4
VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
[55f2dd4e45b0] main libvlc: VLC wird mit dem Standard-Interface ausgeführt. 
Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
[7f0cc4d022f0] avcodec decoder: Using Intel i965 driver for Intel(R) 
Haswell Mobile - 2.4.0 for hardware decoding
[h264 @ 0x7f0cc4d28840] co located POCs unavailable
[h264 @ 0x7f0cc4d9d440] mmco: unref short failure
[h264 @ 0x7f0cc4d80c80] mmco: unref short failure
[h264 @ 0x7f0cc4d385c0] co located POCs unavailable
[h264 @ 0x7f0cc4db9bc0] mmco: unref short failure
[h264 @ 0x7f0cc4d9d440] mmco: unref short failure
[h264 @ 0x7f0cc4d80c80] co located POCs unavailable
[h264 @ 0x7f0cc4d28840] mmco: unref short failure
[h264 @ 0x7f0cc4db9bc0] mmco: unref short failure
[h264 @ 0x7f0cc4d9d440] co located POCs unavailable
[h264 @ 0x7f0cc4d385c0] mmco: unref short failure
[h264 @ 0x7f0cc4d28840] mmco: unref short failure
[h264 @ 0x7f0cc4db9bc0] co located POCs unavailable
[h264 @ 0x7f0cc4d80c80] mmco: unref short failure
[h264 @ 0x7f0cc4d385c0] mmco: unref short failure
[h264 @ 0x7f0cc4d28840] co located POCs unavailable
[h264 @ 0x7f0cc4d9d440] mmco: unref short failure
[h264 @ 0x7f0cc4d80c80] mmco: unref short failure
[h264 @ 0x7f0cc4d385c0] co located POCs unavailable
[h264 @ 0x7f0cc4d80c80] mmco: unref short failure
[h264 @ 0x7f0cc4d385c0] co located POCs unavailable
[h264 @ 0x7f0cc4db9bc0] mmco: unref short failure
[h264 @ 0x7f0cc4d9d440] mmco: unref short failure
[h264 @ 0x7f0cc4d80c80] co located POCs unavailable
[h264 @ 0x7f0cc4db9bc0] mmco: unref short failure
[h264 @ 0x7f0cc4d9d440] co located POCs unavailable
[h264 @ 0x7f0cc4d28840] mmco: unref short failure
[h264 @ 0x7f0cc4d28840] co located POCs unavailable
[h264 @ 0x7f0cc4db9bc0] co located POCs unavailable
[h264 @ 0x7f0cc4d385c0] mmco: unref short failure
[h264 @ 0x7f0cc4d385c0] co located POCs unavailable
[h264 @ 0x7f0cc4d28840] co located POCs unavailable
[h264 @ 0x7f0cc4d80c80] mmco: unref short failure
[h264 @ 0x7f0cc4d80c80] co located POCs unavailable
[h264 @ 0x7f0cc4d385c0] co located POCs unavailable
[h264 @ 0x7f0cc4d9d440] mmco: unref short failure
[h264 @ 0x7f0cc4d9d440] co located POCs unavailable
[h264 @ 0x7f0cc4d80c80] co located POCs unavailable
[h264 @ 0x7f0cc4db9bc0] mmco: unref short failure
[h264 @ 0x7f0cc4db9bc0] co located POCs unavailable
[h264 @ 0x7f0cc4d9d440] co located POCs unavailable
[h264 @ 0x7f0cc4d28840] mmco: unref short 

[Ubuntu-x-swat] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

2021-05-27 Thread Kai-Chuan Hsieh
Try to enable proposed channel and update the libdrm and mesa on ADL-S.

The graphic works good on it.
Attach the system info. 

** Attachment added: "gfx-info.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925320/+attachment/5500621/+files/gfx-info.log

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1925320

Title:
  Backport packages for 20.04.3 HWE stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp