I'm hitting this after moving to 15.04 while 14.04 was fine.
In the dialog window:
(1) Creating object for path
'/org/freedesktop/NetworkManager/ActiveConnection/6' failed in libnm-glib.
In /var/log/syslog:
(nm-applet:1417): libnm-glib-WARNING **: async_got_type: could not read
properties for
Public bug reported:
To reproduce this:
Open System Settings.
Click Appearance
Theme: High Contrast.
Click All Settings tab:
Many icons are missing.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
ProcVersionSignature: Ubuntu
Ok, after installing xserver-xorg-core-dbgsym and using "--callstack dwarf" it
now works.
This bug can be closed.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
NOTE: This is an issue with the package xserver-xorg-core-dbg but
launchpad will not let me file against this.
If I collect call-stacks with linux perf utility, then the Xorg process will
not show symbols.
Everything is listed as [Unknown]
Installing the
per report showing [Unknown] for Xorg process, even though xserver-xorg-
core-dbg is installed.
** Attachment added: "unknown.png"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1733697/+attachment/5012461/+files/unknown.png
--
You received this bug notification because you are
Public bug reported:
If I:
1. point my browser to twitter.com and select a random tweet.
2. And then from the Drop Down menu, select: "Copy Link to Tweet."
3. And then paste that link into a gmail composition
Then the link will not show up, although it is there.
It's almost as if it is pasted
Yes, still happens in Firefox 65.0.1
Does no longer happen in Chromium Version 71.0.3578.98 (Official Build)
Built on Ubuntu , running on Ubuntu 18.04 (64-bit)
Attached is how it looks in chromium after paste: note that colour
formatting.
** Attachment added: "How it looks in chromium"
In firefox, the pasted url is there too, but invisible.
See attachment.
Only show up when going to plain text mode.
I cannot select it, even though it is there.
Only been able to reproduce this with twitter's "Copy Link To Tweet"
function.
** Attachment added: "How it looks in firefox"
$ cat /etc/apt/sources.list
# deb cdrom:[Ubuntu 18.04 LTS _Bionic Beaver_ - Release amd64 (20180426)]/
bionic main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ca.archive.ubuntu.com/ubuntu/ bionic main
bram@ubuntupc:/etc/apt/sources.list.d$ cat ddebs.list
deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse
--
You
Same problem, after doing those steps.
There is *no* old version of dbgsym installed. When I try to install it:
$ dpkg --list | grep gnome-shell
ii gnome-shell
3.28.3-0ubuntu0.18.04.4 amd64graphical shell
for the GNOME desktop
ii gnome-shell-common
Public bug reported:
I am using bionic updates repository, and I can't install the debug
symbols for gnome-shell.
gnome-shell-dbgsym Is out of date
gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1)
but 3.28.3-0ubuntu0.18.04.4 is to be installed
E: Unable to
gnome-shell-dbgsym:
Installed: (none)
Candidate: 3.28.3+git20190124-0ubuntu18.04.1
Version table:
3.28.3+git20190124-0ubuntu18.04.1 500
500 http://ddebs.ubuntu.com bionic-proposed/main amd64 Packages
3.28.3-0ubuntu0.18.04.4 500
500 http://ddebs.ubuntu.com
I do not have gnome-shell-dbgsym installed.
On Tue, Mar 12, 2019 at 9:30 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Hmm, gnome-shell-dbgsym (3.28.3+git20190124-0ubuntu18.04.1) installs
> just fine if you install it afterwards.
>
> AFAIK most packages avoid this problem by
My system was indeed mis-configured. Thanks for helping, I apologize for
the distraction.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Thanks for the reply. It is 3.7G byte mapped hardware memory, not just virtual.
Here's the output you asked:
$ cat status
Name: pulseaudio
Umask: 0022
State: S (sleeping)
Tgid: 25499
Ngid: 0
Pid:25499
PPid: 1
TracerPid: 0
Uid:1000100010001000
Gid:1000
Public bug reported:
So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in
memory.
version: 1:11.1-1ubuntu7.2
OS: Ubuntu 18.04.2 LTS
System uptime: 11 days
Desktop: GNOME
pmap output:
$ pmap 25499
25499: /usr/bin/pulseaudio --start --log-target=syslog
55e3bb805000
Running with 'pmap -x' gives this info:
$ pmap -x 25499
25499: /usr/bin/pulseaudio --start --log-target=syslog
Address Kbytes RSS Dirty Mode Mapping
55e3bb805000 84 84 0 r-x-- pulseaudio
55e3bb805000 0 0 0 r-x-- pulseaudio
I get this both on dev, and edge-hwacc, and snaps I build myself.
It consistently gives me a VA error on wayland, but works on X11.
On Wed, Sep 28, 2022 at 2:30 PM Nathan Teodosio <1990...@bugs.launchpad.net>
wrote:
> > Which build guide did you follow to build your chromium browser? Could
> >
The chromium version and vainfo output are in the upstream issue:
https://github.com/intel/media-driver/issues/1498
The chromium build is via our snap, that integrates your patches.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Yes, your r105 debian package works on my machine, with HW-decode under
Wayland.
Are there any patches applied, other than the 3 mentioned in the
building guide?
** Attachment added: "Screenshot from 2022-10-20 11-11-45.png"
Ah... that explains a lot!
Please send me the revised build guide! Mine is v0.5 from june!
Thanks!
On Thu, Oct 20, 2022 at 3:00 PM Qinling Wang <1990...@bugs.launchpad.net>
wrote:
> Which build guide do you have? Is that Revision 0.7? There are 7 patches
> rather than 3.
>
> --
> You received
The hex value 0100 0008 decodes to:
#define I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC fourcc_mod_code(INTEL,
8)
This is not listed as supported by
MediaLibvaCapsG12::SetExternalSurfaceTileFormat()
--
You received this bug notification because you are a member of Desktop
Packages, which
** Attachment added: "trace from libva"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5617882/+files/va.log.161716.thd-0x00021d72
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
Desktop: wayland
OS: Kinetic
CPU: i5-12600k
GPU: Intel Alderlake_s (Gen12)
I hit this error: vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode)
After which chromium seems to fall back to ffmpeg.
[135904:14:0913/135753.793304:INFO:decoder.cc(41)] DecryptingVideoDecoder
Public bug reported:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both
I added logging of the unsupported modifier value.
This is the value that it fails on:
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:379: Unsupported
modifier: 0x108
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
When I play a H264/AAC video with HW decoding enabled on Alderlake
- 12600k, I get the error:
+ 12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the
Public bug reported:
Ubuntu LTS should be capable of display all current color emojis.
For instance, these new emojis in unicode 15.0
https://emojipedia.org/google/15.0/
** Affects: fonts-noto-color-emoji (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects:
** Tags added: jammy
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu.
https://bugs.launchpad.net/bugs/1990677
Title:
Update fonts-noto-color-emoji for Unicode
** Description changed:
- Ubuntu LTS should be capable of display all current color emojis.
+ [Impact]
- For instance, these new emojis in unicode 15.0
+ Ubuntu has included Google's color emoji font by default for years.
+ Annually, the Unicode Consortium releases a new Unicode standard with
@helainewang I can confirm that your .deb file indeed plays with HW
decoding on my Alderlake machine, but not via VAAPI.
If I pass:
```
--enable-logging=stderr
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder
--disable-features=UseChromeOSDirectVideoDecoder
```
Then the decoding is in
The deb does indeed vaapi hw decode for me on Alderlake.
$ LIBVA_TRACE=$HOME/va.log /usr/bin/chromium-browser-unstable --enable-
logging=stderr ~/Downloads/*mp4
** Attachment added: "va trace"
I tried building a snap with 104.0.5112.101 version of chromium, and
that gives me working HW-decode on Wayland.
A later change in chromium must have broken vaapi playback.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
My current theory is that we broke video input for non Intel platforms.
On my machine with AMD GPU, I get:
ERROR:gpu_memory_buffer_support_x11.cc(134)] Can't create buffer -- gbm
device is missing
$ inxi -G
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
@ikepanhc Which GPU do you have? Intel, AMD or nVidia?
$ sudo apt install inxi
$ inxi -G
Thanks.
--
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/1999487
Title:
Webcam does
Intel provided guidance on how to address this. I will make a merge
request.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
I confirm that I see the same.
I will try a non-hwacc build to see if this is specific to hwacc.
NOTE: It wants to create that file.
It uses mknod() but to create a normal file, not a special file.
On systems that have this file, it wants to open it for reading.
We should find out what is
I've traced it down to the Intel Media Driver's profiling:
https://github.com/intel/media-
driver/tree/master/Tools/MediaDriverTools/UMDPerfProfiler
UMD Performance Profiler
(I am pretty sure that here, UMD stands for User Mode Driver.)
I will try to find a way to disable the profiling
Note: the `content chromium:va-driver-non-free` connection is completely
harmless.
We just added an extra path to get drivers from an alternate snap if so
required, in the future, for patent reasons.
This is a currently unused provision, and no free drivers are built or
used.
--
You received
Just logging this here: I tried solving this with the `GFX_FEATURE_FILE`
environment variable:
`GFX_FEATURE_FILE=$SNAP_USER_COMMON/igfx_user_feature.txt`
But unfortunately that did not prevent the media driver from using
`/etc/`
I think the file name override gets taken out by the precompiler.
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-
source/+merge/435082
--
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/124
Title:
Unsupported buffer
Public bug reported:
This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu
22.10 Wayland.
When playing a h264 video, or a youtube video, I get:
```
$ snap info chromium | grep installed
installed: 107.0.5304.121-hwacc(2224) 171MB -
$ chromium ~/sample.mp4
108.0.5359.124 from latest/candidate plays video without crashing.
109.0.5414.36-hwacc from latest/beta/hwacc has the same crash.
Adding --ozone-platform=x11 stops the crash.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu
22.10 Wayland.
When playing a h264 video, or a youtube video, I get:
```
$ snap info chromium | grep installed
installed: 107.0.5304.121-hwacc(2224) 171MB -
$
I have tried to repro this.
chromium: 107.0.5304.121-hwacc on Ubuntu 22.10
Logitech, Inc. QuickCam Vision Pro [WORKS]
IMC Networks USB2.0 HD UVC WebCam [WORKS]
Could it be that this issue happens with MIPI cameras only? My tests
were with USB based cams.
--
You received this bug notification
Public bug reported:
When building accountsservice we apply patches, among of which is
`0010-set-language.patch` which raises concerns.
It will not compile without warnings: At the very least contains
misleading indentation.
```
[92/99] Compiling C object src/accounts-daemon.p/user.c.o
@ikepanhc Thanks. What model webcam do you have?
--
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/1999487
Title:
Webcam does not work with v107.0.5304.121-hwacc
Status in
Ugh, this may need revisiting. Even though it stops the crash, it also
seems to stop hardware decode support for me. I would have sworn I
tested with intel_gpu_top, but on the current edge build, I see no HW
acceleration anymore.
--
You received this bug notification because you are a member of
I am hitting this too.
Unlike OP, I am on 22.10
Like OP, I am on nvidia 510 proprietary drivers.
Adding --ozone-platform=wayland fixes the issue for me.
$ chromium
Gtk-Message: 10:43:34.433: Not loading module "atk-bridge": The functionality
is provided by GTK natively. Please try to not load
I have made a Pull Request for upstream.
https://github.com/intel/media-driver/pull/1588
Once this is merged and released, we should pick this up in our snap build.
By setting GFX_FEATURE_FILE and GFX_FEATURE_FILE_NEXT we can then prevent
access to /etc/ dir.
** Changed in: chromium-browser
apport information
** Description changed:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
-
When I
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630394/+files/IwConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
I installed chromium snap from edge channel:
$ snap refresh --amend --channel edge chromium
chromium (edge) 109.0.5396.2 from Canonical✓ refreshed
$ chromium
Trace/breakpoint trap (core dumped)
==
STRACE
==
When I run it through strace, the last system calls are:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630398/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630396/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630395/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630401/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630400/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630402/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630399/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630397/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630404/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630405/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630403/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630406/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1996217/+attachment/5630407/+files/acpidump.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Does not crash when using AMD gpu, instead of Alderlake iGPU.
--
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/2009739
Title:
hwacc build crashes on direct scanout.
Status in
Public bug reported:
This pertains to the HWACC branches of the chromium snap.
When launched full-screen on an Intel iGPU, the hardware overlay use
will result in a core dump.
This could be related to direct-scanout and overlay planes?
To reproduce:
$ chromium --start-fullscreen
OS: Ubuntu
Unfortunately, removing the --enable-hardware-overlays flag does not
help.
Still crashes when full screen:
Chromium111.0.5563.19 (Official Build) snap (64-bit)
Revision
378a38865270d286695aeb86f190564911ef7bc2-refs/branch-heads/5563@{#251}
OS Linux
JavaScript V8
I've added logging to
third_party/minigbm/src/amdgpu.c
third_party/minigbm/src/drv.c
This yielded:
drm_version->name: amdgpu
backend_list[0] = amdgpu
drv_get_backend(13) returned 0x55bf084e4338
dri_init() failed for path /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so driver
radeonsi: No such
With the DRI_DRIVER_DIR issue out of the way, I see:
WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path.
WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render
node handle.
render node is present:
$ ls -al /dev/dri/
total 0
drwxr-xr-x 3 root root
MR for snap-from-source is here:
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437529
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is
I've sent an up-stream fix to Gerrit:
https://chromium-review.googlesource.com/c/chromiumos/platform/minigbm/+/4263398
Fix to snap-from-source will follow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I have reproduced this with a chromium that I built manually, from source, not
going via snapcraft.
So that rules out snap as the culprit, I think.
reproduced with: 112.0.5572.0
Built with:
use_system_minigbm = false
use_intel_minigbm = true
use_amdgpu_minigbm = true
This part is missing from the compiler command line
-DDRI_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri\"
I've verified that this can be fixed by adding a configuration to
minigbm's BUILD.gn I will create a patch that addresses this.
--
You received this bug notification because you are a member
Note that when logging into build VM after building the chromium-hwacc
snap:
multipass shell snapcraft-chromium
I see:
# pkg-config --variable=dridriverdir dri
/usr/lib/x86_64-linux-gnu/dri
And not the expected
/snap/gnome-3-38-2004/current/usr/lib/x86_64-linux-gnu/dri
this value is from
Hard-coding the dri directory to point to the snap's dri dir fixes this,
as I now see:
Graphics Feature Status
Canvas: Hardware accelerated
Canvas out-of-process rasterization: Disabled
Direct Rendering Display Compositor: Disabled
Compositing: Hardware accelerated
Multiple Raster Threads:
I confirmed that DRI_DRIVER_DIR never makes it to the compiler flags.
I added an error pragma to catch an empty definition and no definition
in attached patch.
The result when building w that patch (on 107 chromium):
FAILED: obj/third_party/minigbm/minigbm/amdgpu.o
Public bug reported:
Currently the hwacc branches of snap_from_source fail to build.
This is caused by the fact that the guide-0.9.1 patches are against 107
chromium, and no longer apply cleanly.
build logs here:
https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta
The previous test was on a chromium 107 build.
I re-tested it on a chromium 110 build with minigbm, and it shows the same
result on rx580 gpu:
software compositing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Bram Stolk (b-stolk)
--
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/2006641
Title:
hwacc branc
Public bug reported:
This pertains to the hwacc branches of snap_from_source chromium builds.
Following the guide-0.9.1, we switched from system gbm to minigbm.
(These switches are in args.gn)
use_system_minigbm = false
use_intel_minigbm = true
use_amdgpu_minigbm = true
This enables us to
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Bram Stolk (b-stolk)
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-b
>One-copy patch does not apply to 111.
That is regrettable. I'll do a quick test to see if a higher --fuzz
helps, by any chance. Which would be a trivial fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This could be a hint on why:
WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path.
WARNING:wayland_buffer_manager_gpu.cc(424)] Failed to initialize drm render
node handle.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks for testing. So, your first log contains this error, though:
```
/build/chromium/parts/chromium/build
ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit
code.
dri_driver_dir = exec_script(pkg_config_script,
^--
Current dir:
Public bug reported:
[NOTE] This is for the HWACC build of chromium, from snap channel
latest/candidate/hwacc
$ snap info chromium | grep installed
installed: 107.0.5304.68-hwacc(2301) 172MB -
This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin.
Assignee: Bram Stolk (b-stolk)
Status: New
** Tags: kivu
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Bram Stolk (b-stolk)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
--
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/2006966
Title:
Missing flag causing lack of
91 matches
Mail list logo
