The checkbox to enable showing printers shared by other systems also
seems to be gone from localhost:631/admin, and enabling local printer
sharing currently breaks CUPS entirely: the system-config-printer-gnome
applet will no longer connect to CUPS, and localhost:631 will reject the
connection
I agree with Tony Narlock. After all, you only have to run sudo apt-get
purge unity-lens-shopping unity-scope-musicstores unity-webapps-common
rm ~/.local/share/applications/Amazonwwwamazoncom.desktop in order to
get rid of all the search suggestions and web apps. If those three
packages wouldn't
Public bug reported:
As with most other GNOME games, glines does not save the window
dimensions. For the regular board size, the default window size is all
right, but when selecting a larger board size, the default window size
makes the game pretty much unplayable. The window has to be maximized
** Attachment added: Large board size with default dimensions under Xubuntu
12.10
https://bugs.launchpad.net/bugs/1057028/+attachment/3345962/+files/Screenshot%20-%20092612%20-%2018%3A36%3A44.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
This is still present in 12.10 and still has to be fixed quickly in my
opinion. Modifying /usr/share/gvfs/mounts/network.mount has three clear
downsides; it has to be done on every machine after every clean install
(so basically twice a year on all your computers); it puts an ugly
broken-file icon
The recent updates have simply removed the checkbox from system-config-
printer-gnome. Admittedly, you can manually add network printers by
entering the IP address of the local print server (or whichever computer
has the printer connected to it), but printers still do not show up
automatically.
This seems fixed in Xubuntu 12.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/727415
Title:
Disk Utility tries to launch Nautilus
Status in gnome-disk-utility:
New
Public bug reported:
In order to keep my data storage disks from slowly committing suicide by
unloading their heads, I have to disable APM for both of them. Usually I
would be able to do so by putting 'hdparm -B255 -S0 /dev/sdx*' in
/etc/rc.local.
Since Ubuntu 12.10, Palimpsest has a built-in
Just a side note: when I only purge network-manager and network-manager-
gnome, but leave dnsmasq-base installed, the slow shutdown bug is
solved, but the unmount problem persists. So I'm not completely sure if
it's entirely caused by network-manager, as it also seems to happen when
I guess this was to be expected with Apple being in charge of CUPS. No
longer having network printers automatically discovered and needing the
drivers on the client-side are two of the worst regressions in Ubuntu
and GNU/Linux in general that I've seen in years.
Fork time? Seriously, this is bad.
This should be a high importance bug. Basic functionalities like these
may not be broken, and the Quantal release isn't that far away anymore.
As of today, it is still not working with the latest packages from the
repositories.
--
You received this bug notification because you are a member of
I've just installed the updates; and it doesn't make any difference for
me. I also tried reinstalling network-manager, network-manager-gnome and
dnsmasq-base, but still nothing. I'll try a clean install in VirtualBox
tonight.
--
You received this bug notification because you are a member of
Tested this in VirtualBox:
Custom Xubuntu 12.10 installation (netinst with Xfce packages) - fully updated:
not fixed
Stock Ubuntu 12.10 installation (installed with ubiquity, unmodified) - fully
updated: not fixed
Stock Xubuntu 12.10 installation (installed with ubiquity, unmodified) - fully
After tonight's dbus updates, still no change.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1058987
Title:
In Quantal, the root filesystem is not cleanly unmounted at
I can confirm that everything is working as before. Thanks a lot for
this fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1061063
Title:
[FFE] Reimplement automatic appearing of
Yes, it's still broken for me as well. And don't bother upgrading to the
packages from proposed, because even though -this- bug is fixed there,
many worse bugs are introduced; especially for non-Unity users.
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
Since last night's updates, automatically logging in with LightDM causes
the screen to be blank with only a cursor shown. The desktop does appear
to be rendered on the background, because moving icons and clicking
menus (after guessing where they are) does work. The only way
Even manually logging in is starting to become glitchy now. A black box
is constantly shown, and the cursor starts disappearing every now and
then.
This is probably more related to the X server than to LightDM, it seems.
** Attachment added: Black box at the top left of the gtk greeter
** Attachment added: Console output disappearing when the cursor moves over it
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1064878/+attachment/3391952/+files/IMG_20121010_092924.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is
It isn't visible on screenshots, so I'll add some pictures.
** Attachment added: Blinking cursor shown through the desktop
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1064878/+attachment/3391944/+files/IMG_20121010_092854.jpg
--
You received this bug notification because you are
** Attachment added: Cursor is even shown on tty1
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1064878/+attachment/3391953/+files/IMG_20121010_093145.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
I thought that autologin made a difference, but it appears that I was
wrong. This is more likely an X bug than LightDM-specific.
** Package changed: lightdm (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg
I think I've found what triggers this behaviour: I have a line in
/etc/rc.local to set my initial brightness to a certain point. I believe
the last update to either X or LightDM causes a race condition which
triggers this bug. I have now added 'sleep 2' as the first line in
/etc/rc.local, and
Edit: and once again I spoke too early, as the problem is back after a
reboot. I have now removed everything from /etc/rc.local, but it still
happens every now and then. And I can't get apport-collect to properly
work either, as it crashes as soon as I try to send the logs. Hence the
one big log
This has just landed through the regular channels, and it has indeed
fixed the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1049025
Title:
Can't select text/highlight
Switching to tty1 and moving the cursor, results in this behaviour
** Attachment added: Switching to tty1 and moving the cursor, results in this
behaviour
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1064878/+attachment/3393287/+files/IMG_20121010_185425.jpg
--
You received this bug
** Attachment added: Logging out on tty1 confuses ConsoleKit, so the system is
aware that this is not tty7
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1064878/+attachment/3393290/+files/IMG_20121010_185528.jpg
--
You received this bug notification because you are a member of Desktop
It seems to be related to the /etc/rc.local script after all. I forgot
to disable the execution bits the last time; but now I've run chmod -x,
the problem really seems to be gone. I've done a fresh install and
rebooted over 20 times, but I haven't seen anything weird anymore.
So I think it's safe
*** This bug is a duplicate of bug 1061639 ***
https://bugs.launchpad.net/bugs/1061639
I agree with Christian. Even though the unmount issues don't seem to
happen on my testing machine anymore, shutting down still feels weird.
Just shut down a 12.04 machine and compare it to a 12.10 machine.
Just use chattr +i /usr/share/gvfs/mounts/network.mount?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/775117
Title:
Thunar hangs on first launch of each session
Status in GVFS:
New
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1442728
Title:
Chromium fullscreen should be unredirected
All I have to do is a mini.iso 15.04 netinstall, install my default
packages, and I can reproduce this bug on any machine I've tested.
The only workaround for me is:
Immediately after a netinstall:
---
sudo apt-get purge policykit-1
sudo apt-get update
sudo apt-get upgrade
sudo systemctl reboot
Disabling WebGL is one thing, but disabling hardware acceleration
altogether causes horrible tearing with each and every driver. All
videos look terrible and even smooth scrolling is no longer acceptable.
I've received dozens of support calls from clients about how the latest
Chromium build is
As part of the big bug review for 16.04 LTS I have tested this on 15.10
and the bug is still there.
** Attachment added: "Screenshot of CCSM in a Wily VM"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1442728/+attachment/4466059/+files/ccsm.png
** Tags added: desktop-bugscrub-triaged
This also happens for me on i965, r600 and radeonsi, especially when
running a background window with moving pixels (something like GNOME
System Monitor on the Graphs tab for instance). Enabling
force_swap_buffers indeed seems to make the problem go away.
As part of the big bug review for 16.04
I did a couple of wily netinstalls today, and I'm still having this
problem.
I first have to run sudo apt-get install policykit-1, and only then I
can run my postinstall scripts normally.
Otherwise, I'm left with the notorious timeouts.
Can't policykit-1 be installed as part of the mini.iso?
Since the Chromium 79 snap, this seems to no longer work.
I have the libwidevinecdm.so from Firefox in
~/snap/chromium/current/.local/lib/, which always worked fine before,
but now EME videos all just show warnings and the plugin does not seem
to be loaded.
Extracting the libwidevinecdm.so from
I think everyone agrees that the 'Chromium/' part is the main
problem. The snap also adds 'snap', which is an additional problem, but
only removing 'snap' wouldn't help.
The deb version adds 'Ubuntu' in the OS part, which the snap does not.
I'm unsure if that is much of a problem. Firefox on
https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/129
** Bug watch added: gitlab.freedesktop.org/geoclue/geoclue/-/issues #129
https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/129
--
You received this bug notification because you are a member of Desktop
Packages, which is
I will. But for the time being, perhaps it should be tested with more
WiFi adapters? (I only have AR9380's, so I can only test ath9k.)
If this is a problem for many chipsets, the default should probably be
changed back to 'false'.
--
You received this bug notification because you are a member
Public bug reported:
Ubuntu's Chromium build uses a custom user agent in many ways. It
included "Ubuntu" in the .deb versions, and now it includes "snap" in
the snap versions. Also, it adds a "Chromium/" field. This
breaks many websites that do aggressive user agent matching, such as
Netflix and
It's not just gnome-weather; it seems to be a more generic problem in
geocule
** Package changed: gnome-weather (Ubuntu) => geoclue-2.0 (Ubuntu)
** Summary changed:
- gnome-weather / geoclue polls wpasupplicant SSID list too often
+ geoclue polls wpasupplicant SSID list too often
**
Agreed, it works for Netflix, but it does not work for Teams and some
other sites. There, one has to go to the Developer tools > More tools >
Network conditions and change the UA there.
Merely removing "snap Chromium/" fixes the issue.
I guess that the UA switcher extension doesn't change the UA
Pretty much every incompatibility-related issue is solved by spoofing
the user agent and removing the "snap Chromium/" part, simply
claiming to be normal Chrome. There is not really any point in
differentiating between Chromium and Chrome, but it breaks many
websites, and it's also a nasty feature
I'm guessing that this patch [1] should not be added.
[1] https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/tree/build/patches/snap_useragent.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
It sounds like geoclue is hardly maintained upstream. And I really don't
think it's a driver issue. It's common physics that tuning a radio to
different channels all the time will break the transmission to and from
the channel you want to tune to.
In Ubuntu 18.04, this was disabled by default.
Will this be in the next stable channel snap update?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1868117
Title:
[snap] Adapt chromium user agent to avoid "not supported
I think part of the culprit may be that the Frequent / All buttons on
the bottom are pushed downwards when opening an app folder on a 1366x768
display, causing the grid to re-align. This doesn't happen on 1280x800
or 1680x1050, where the bugs related to the many dots on the right or
the shell
I can confirm that setting org.gnome.desktop.privacy remember-app-usage
to false, and thus removing the Frequent / All buttons, also works
around this problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This is definitely resolution related. I am unable to reproduce this on
my X200's and T400's (1280x800) or T500's (1680x1050), but it hits me
every time on my X220's (1366x768).
I also tried gnome-shell-extension-ubuntu-dock 68 from focal-proposed,
but that does not help at all. Setting
** Description changed:
I have a Nitrokey FIDO2, which works fine with the Firefox deb package.
However, it does not work at all with the Chromium snap. I have
libu2f-udev installed.
- This problem can be fixed by adding the following line to
+ This problem can be fixed by adding the
Public bug reported:
I have a Nitrokey FIDO2, which works fine with the Firefox deb package.
However, it does not work at all with the Chromium snap. I have
libu2f-udev installed.
This problem can be fixed by adding the following line to
/etc/udev/rules.d/70-snap.chromium.rules:
# u2f-devices
#
This still affects me on my Pinebook Pro. Are there any plans to
backport this to focal?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1915929
Title:
gnome-shell-calendar-server
Related pull request here: https://github.com/snapcore/snapd/pull/10642
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2 does not work
@vanvugt Are you sure it works?
I'm currently testing Ubuntu 22.04 (completely updated as of writing)
with the 94.0.2-2 Firefox snap. When I go to https://meet.jit.si/ and
click the screen sharing button, I can only select "Use operating system
settings". When I do that, nothing happens. I don't
I noticed that both the Firefox and Chromium snaps do work in Debian 11,
which uses an older xdg-desktop-portal than Ubuntu 22.04. I wondered
what would happen if I'd install xdg-desktop-portal and xdg-desktop-
portal-gtk 1.8 from 21.10 in 22.04, and it turns out that this fixes it.
So I guess
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
Likely caused by this change:
https://bugzilla.mozilla.org/show_bug.cgi?id=1737068
** Bug watch added: Mozilla Bugzilla #1745098
https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
** Bug watch added: Mozilla Bugzilla
** Changed in: snapd
Status: Fix Committed => Fix Released
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1940467
I have also tested the tarball releases from
https://www.mozilla.org/firefox/
The problems are identical with those releases. I tested 94.0.2, 95.0,
96.0b2 and 97.0a1.
I ran all of them with `MOZ_ENABLE_WAYLAND=1`.
94.0.2 works perfectly fine, and all the other releases show lag while
** Description changed:
I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
- the update to Firefox 95, it's been verry laggy; especially noticeable
+ the update to Firefox 95, it's been very laggy; especially noticeable
while scrolling, for instance on about:support.
Public bug reported:
I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
the update to Firefox 95, it's been verry laggy; especially noticeable
while scrolling, for instance on about:support.
Strangely, the bug is less present when the browser window is smaller. A
maximized
Copy/paste works for me, but drag/drop does not. I can't even rearrange
tabs or bookmarks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1947210
Title:
Firefox Snap can't copy or
Public bug reported:
After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no
longer shows any sessions in the bottom-right corner. When I log in, I
am dropped into an X11 session, with no way to switch to Wayland.
Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to
kevin@arcadia:~$ apt info network-manager
Package: network-manager
Version: 1.36.6-0ubuntu2
kevin@arcadia:~$ apt info libnm0
Package: libnm0
Version: 1.36.6-0ubuntu2
I have installed network-manager and libnm0 version 1.36.6-0ubuntu2 from
jammy-proposed. After connecting to a network with both
Unfortunately I was not tracking jammy-proposed, so I only found out
about this bug when it entered jammy-updates.
I don't think my configuration is that exotic to be honest. Many
companies use DHCPv6 servers giving out static leases, and many
companies use firewalls to restrict incoming (SSH)
@seb128 What is the plan for the network-manager package in Ubuntu
jammy-updates? Is it to be left broken until upstream fixes this bug?
Because I think that the problem this last version introduces is a lot
bigger than the problem(s) it solves. Therefore I would say that it can
be defended to
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
Status in
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
-
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
It's fixed upstream as well now:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6920b6ceb1c2e7856ad76e118ee5b4dd36130735
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This seems to restore previous behaviour yes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
** Tags added: jammy
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1974428
Title:
Update to the current 1.36 stable version
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being
@seb128 I have created a new bug report with links to the upstream
commits. The core of the issue is that IPv6 addresses are now being
added in the wrong order, so the kernel prefers SLAAC addresses over
DHCPv6 addresses, which should be the other way around.
As this is a breaking change in
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
I've just tested the latest snap from the beta channel (2751). I deleted
~/.chromium-browser.init, and I can confirm that the webcam works fine
now in the default configuration. VAAPI is also still functional
according to intel_gpu_top.
Thanks!
--
You received this bug notification because you
Sure, no problem.
Could you by any chance do a new build for the beta channel with this
fix included? Then I can test if the webcam still works in the default
configuration, without the ~/.chromium-browser.init file.
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Looking at https://discourse.ubuntu.com/t/an-overview-of-hardware-
acceleration-in-chromium/36672, a couple of flags are added for beta and
edge channel builds of Chromium to enable VAAPI.
You may want to remove the flag --video-capture-use-gpu-memory-buffer
from the builds,
93 matches
Mail list logo
