@trurl42, seems you have different machine which I will need alsa-info
and dmesg for your config. Could you file another bug and attached the
detail information as comment #1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
Ok, this was introduced upstream somewhere between 2.36.0 (jammy
release) and 2.44.0 (jammy-updates). webkit2gtk now detects whether
gbm_bo_create_with_modifiers2 exists at build time; if so, it uses them.
This is not a problem for the main archive, as the libgbm that mesa
provides includes those
@ Paramvir Could you try new kernel and update the information? Thanks
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
@trurl42, does the sound used to work before (older kernel than 6.5)?
>From the kernel log, the line out has no trivial problem. I need to know is
>this a regression or something else. Thanks
[5.221075] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254:
line_outs=1
Hi Jeff, apologies for the delay in getting back to you. Based on the
crash report provided it looks like it was a bug with the tracker
package. I think this should be sorted by now though!
** Changed in: subiquity
Status: New => Invalid
--
You received this bug notification because you
duplicate filing of
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061326
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
That works! Thanks Andreas.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060335
Title:
upower/1.90.2-8build3 autopkgtest failure on arm64
Status in upower package in Ubuntu:
Fix
Yes, a no-change rebuild fixes the issue.
Please see attached debdiff for the fix.
I have provided a PPA with the build and tests:
PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower
arm64 autopkgtest log:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2060375
When reporting bugs in the future please use apport by using 'ubuntu-
m/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz
** Affects: upower (Ubuntu)
Importance: Undecided
Assignee: Chris Peterson (cpete)
Status: In Progress
** Tags: update-excuse
** Description changed:
- autopkgtests fail, only on arm64, with the f
I estimate another ncr could fix the issue. Building and testing in a
ppa.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060335
Title:
upower/1.90.2-8build3 autopkgtest failure on
So something changed to add -Werror=implicit-function-declaration at
build time (gcc didn't change so maybe dpkg?), which should have caused
the other arches to fail as well but since they ran at different times
they pulled different versions of build dependencies. This will likely
get fixed on a
(Ubuntu)
Importance: Undecided
Assignee: Chris Peterson (cpete)
Status: In Progress
** Changed in: accountsservice (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
Yes, please make sure the flaky tests are marked as such in the
autopkgtests. SRUs are not released until either the test passes or the
package version is marked as badtest in the britney hints.
(A retry has caused it to pass on armhf)
--
You received this bug notification because you are a
Public bug reported:
Intel ALC269VB Analog worked fine until today's update. Now all I get is
"dummy output" and after running ubuntu-bug, the diagnostic says that
pulseaudio has crashed. Reloading does not help.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio
Public bug reported:
Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there
is no sound. I believe the CPU sound unit is essx-8336. Many people have
reported similar problems, with the system sound being "dummy output".
My bluetooth ear buds do work. Endeavour-OS and Fedora 39
Hi,
Thanks for your report and providing some logs! Could you try the
install again and run `sudo apport-cli -u 2055418 -c /var/crash/*.crash`
in the terminal? This should collect a bit more information and dump it
here so we can investigate further.
Thank you,
Chris
** Also affects: tracker
Public bug reported:
So, this is pretty weird.
In the Shell quick settings panel (the one accessed by clicking on the
wifi/bluetooth/sound/battery part of the top bar), in the Shutdown
submenu, the "Suspend" button - and *only* the Suspend button - does not
respond to mouse clicks. I cannot use
Thank you for taking the time to report this bug and helping to make
Ubuntu (Studio) better.
@Bluesbrother (or the original posted to askubu..)
Can you please add what your installation media was, ie.
`cat /var/log/installer/media-info`
as your original post on askubu implies you
d interface & endpoints of
device terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device Aborted (core dumped)
- so I'm still stuck. thanks again anyway."
Also, running 'mtp' now invites me to use 'Fprint'...?
For the record, using Ubuntu
the affected address is hosted locally not publicly available...
i've re-attached the image
** Attachment added: "ubuntu-chromium-snap-font-bug.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022073/+attachment/5741780/+files/ubuntu-chromium-snap-font-bug.png
--
You
Is there any movement on this issue? I am having the same problem if I
don't remove Airprint capabilities from all my network printers. I
can't do that because if I do iOS devices can't print. Does anyone have
any other ideas?
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2048438
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2048441
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
When the headphone is connected before the computer is booted the sound is
played on the speakers and not on the headphone.
When I remove the headphone and insert it back, the sound then switches
correctly to the headphone.
=> This seems to be an boot / initialization
Hello Daniel, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
This occurs in the ESR builds from ppa:mozillateam/ppa.
My dmesg log is filled with lines such as:
[ 3015.575852] audit: type=1400 audit(1702042069.563:12459):
apparmor="DENIED" operation="file_lock" class="file" profile="firefox"
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
Ah, jbicha had already retriggered the autopkgtests, and they now pass.
Huzzah!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to
Retriggered the autopkgtest to use the correct apparmor version; let's
see if that fixes things.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in
Public bug reported:
Upon upgrade from Firefox 119 to 120 noticed that the Unity Global Menu
no longer works. Rolling back the package to 119 and installing FireFox
ESR global menu works as expected.
This is the package that is on the mozillateam PPA.
** Affects: firefox (Ubuntu)
OOoooh, right. This is releasable, and has a sensible changelog, it's
just that LP isn't showing the full changes file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
A support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2040077
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
I have multiple crash files:
_opt_brave.com_brave_brave.1000.crash
_usr_bin_gjs-console.1000.crash
_usr_lib_xorg_Xorg.0.crash
_opt_Signal_signal-desktop.1000.crash
_usr_libexec_goa-daemon.1000.crash
2. I have run the ubuntu-bug command against each (xorg required sudo
due to being owned by
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039711/+attachment/5710996/+files/prevjournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039711/+attachment/5710995/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to
login with Wayland, after about a minute or so of giving credentials for
login, the login prompt reappears. X11 works, but takes about 3 minutes
to actually load to desktop. Started two days ago after an
It seems that it's already been retried once in the main archive. I note
that your PPA builds *without* -proposed enabled, whereas the archive
will build *with* -proposed enabled - possibly this is why it fails in
the archive and succeeds in your PPA?
--
You received this bug notification
Gunnar asked
> But this makes me wonder if there is a need to special case other
flavors besides MATE.
I've noted a number of users report 'garbled' or 'unreadable' text on
discord (testing-cycles) & Ubuntu-MATE discourse (#1) but one of those
reports led us back here, alas I'm not aware of any
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
Hello Jeremy, or anyone else affected,
Accepted glib2.0 into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
gdm3 looks good to me, but I haven't accepted it yet as it depends on
the gnome-settings-daemon patches and I think it's best to resolve those
questions before accepting gdm3 into -proposed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
> Smartcard authentication using custom methods using via a custom
configured system nss database may not work anymore.
Do I read the gnome-settings-daemon patches correctly, and this actually
just entirely drops support for auth via NSS? So the regression
potential is that if someone has set up
The verification of the Stable Release Update for xserver-xorg-video-
amdgpu has completed successfully and the package is now being released
to -updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event
Ooof, double oops. That's the *flatpak* version they've described, not
the appstream-glib version they've tested.
Nathan Teodosio: could you (or someone else) double-check that this is
fixed specifically by appstream-glib 0.7.16-1ubuntu2 in Focal?
--
You received this bug notification because
Oops! Looks like the last commenter meant to set this into the
verification-done state, rather than -failed, as they've got correct
output.
Fixing and releasing.
** Tags removed: verification-failed-focal verification-needed
** Tags added: verification-done-focal
** Tags removed:
I attempted an install QA test of Ubuntu Desktop mantic daily (0908.2) on
- hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)
I didn't see the installer, briefly got one error message (didn't have
time to recognize/read), then screen went white with oh no, something
went wrong... and
Hello Kai-Chuan, or anyone else affected,
Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-
amdgpu/22.0.0-1ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been
rejected from the upload queue for the following reason: "This looks
good, but you've included two slightly different versions of the patch?
Please re-upload with just one :)".
--
You received this bug notification because you are
I just did:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7998
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #7998
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7998
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
This package is on the Mozillateam PPA and affects Bionic.
The update from 115 to 116 appears to have broken the Unity Menu bar
patch again. I noticed in the previous incident that this is an
unsupported build. Going forward should PPA issues still be reported
here or should
The verification of the Stable Release Update for yaru-theme has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for yaru-theme has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Changed in: archlinux
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP.
There's also an askubuntu question about this issue:
https://askubuntu.com/questions/1471028/fatalcredentials-cc127
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2017980
Relaying the information from
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it is
not publicly visible:
```
Hmmm this looks like
https://bugs.chromium.org/p/chromium/issues/detail?id=1365674#c8 again. I don't
know why using clone(CLONE_NEWUSER ...) would return EACCES (which
The verification of the Stable Release Update for ubuntu-meta has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hello Matthew, or anyone else affected,
Accepted adsys into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~20.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthew, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthew, or anyone else affected,
Accepted adsys into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Update from
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it's
not public visible:
```
@Reporter, Thanks for filing the Issue. Please find the magic signature & stack
trace for the crash id# 8e7f32382b1ddc1c
Magic signature :
[Assert] sandbox::`anonymous
I did an check and can confirm that the chromium-browser as installed by
the usual 22.04 package is *NOT* affected.
But Google chrome well as google-chrome-beta installed by the PPA
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
do show the bug.
--
You received this bug
Today apt want's to update my nvidia driver from
510.108.03-0ubuntu0.22.04.1 to 525.125.06-0ubuntu0.22.04.1
Based on the bad experience of the unwanted kernel update I'm not sure
whether I should take the risk.
Hopefully one of the maintainers reacts to this bug soon and gives more
advice about
When booting just select an older kernel - and hope that the maintainers
are quickly cleaning the mess
--
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/2017980
Title:
Chrome
Coming back to this report here: as expected but now confirmed: when I
boot the old kernel everything is working normally.
So the cause is *confirmed* to be the different/upgraded kernel that was
installed without my request (as described in
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
I just checked the chromium bug tracker: the link is valid, but it is
flagged as "Only users with EditIssue permission or issue reporter may
view.".
I guess it's caused by being created from an uploaded crash report. Probably
due to privacy considerations as the crash dump might contain private
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
Chrome bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821
--
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/2017980
Title:
Chrome crashes with
Related (but not duplicate) is bug
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
nvidia-5.19/+bug/2025538
--
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/2017980
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Confirmed
** Changed in:
** Tags added: lunar
--
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/2025520
Title:
User fonts are not detected (only system wide fonts)
Status in libreoffice package in Ubuntu:
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Now an ubuntu-release thread: https://lists.ubuntu.com/archives/ubuntu-
release/2023-June/005650.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2020682
Title:
Release adsys 0.12.0
I doubt I'll be able to do anything here.. (beyond keep testing)
This box had multiple installs, one (sda5) was reused without issue, the
other (having ~same done to it) seemed to attract bugs, I see mention of
SDA6 above, with later issues on that problematic install reported here
-
Ubuntu 23.04, X11
Codec H.265 / HEVC
Container ISO MP4/M4A
running totem from command line gives below errors.
** Message: 23:18:54.268: Missing plugin:
gstreamer|1.0|totem|meta/x-gst-fourcc-fdsc
decoder|decoder-meta/x-gst-fourcc-fdsc (meta/x-gst-fourcc-fdsc decoder)
** Message: 23:18:54.268:
I'm going to mark this incomplete
I suspect the issue is a consequence of a bad install -
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000
Regardless, if it's a real issue, it'll be re-filed...
** Changed in: evolution-data-server (Ubuntu)
Status: New => Incomplete
--
I'm going to mark this incomplete
I suspect the issue is a consequence of a bad install -
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000
Regardless, if it's a real issue, it'll be re-filed...
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received
I see that we've done this sort of wholesale backport once before, but
this doesn't seem like it falls under the "other safe cases" part of the
SRU criteria:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
It seems like this should have a more formal process? I don't see any
special
*** This bug is a security vulnerability ***
Public security bug reported:
I have no useful details to provide sorry.
This is a QA test install only.. with packages & VERY MINOR change(s)
having taken place on it ...
(on subsequent boot; these messages are now appearing & requesting me to
*** This bug is a security vulnerability ***
Public security bug reported:
I have no details to provide sorry.
This is a QA test install only.. with packages & VERY MINOR change(s)
having taken place on it ...
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: evolution-data-server (not
I was finally able to get the browser approach to work (advice: there is
a little slider at the very top of the gnome-extensions-app GUI that you
have to click to get the extensions to activate, or else you begin to
lose your mind thinking that you have to install it manually from source
because
*** This bug is a duplicate of bug 2022879 ***
https://bugs.launchpad.net/bugs/2022879
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
wishes to you, Chris
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1965215
Title:
[81FD, Realtek ALC236, Black Mic, Right] The external microphone is
not detected
Status
Public bug reported:
I've been building some single purpose kiosks using Ubuntu server on
RaspberyPis (models 3 and 4). It's a minimal build that uses matchbox-
window-manager and chromium in kiosk mode.
Prior to 22.04 we had no issues (see 'correct font' link). Building new
Pi images from a
*** This bug is a security vulnerability ***
Public security bug reported:
Ubuntu Desktop (mantic) install on hp dc7700 as QA-test.
Install was a re-use of SDA6 which was Ubuntu-MATE 23.04 with music
added to /home/Music, plus audacious, figlet, fortune, aptitude & other
apps added earlier
Well, on one of my machines I installed Mesa from the kisak more stable
ppa ("turtle"), which is more up to date than mesa from the jammy
repository. I was able to re-enable hardware acceleration with no
problems. So there is something in the whole collection of mesa packages
that broke
://gpu url is that unless you disable the
gpu, it's not possible to even read the url. A real chicken and egg
problem.
Chris Hall
On 5/26/23 4:13 AM, Nathan Teodosio wrote:
> Passing --disable-gpu would likely help here.
>
> Hardware acceleration stuff can be seen in about://gpu.
>
>
Public bug reported:
The update installed this morning (May 25, 2023) disabled both Brave and
Chrome. Firefox is OK. I have installed a newer Brave-beta and it works
fine. The problem first appeared in Xorg, where no page could be
rendered, including settings. I then rebooted into Wayland and
Hello Angel, or anyone else affected,
Accepted gnome-shell into lunar-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/44.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Jeremy, or anyone else affected,
Accepted gnome-shell into lunar-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/44.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
While the discussion about the test plan is ongoing
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/58 I'm happy to
accept this with the currently documented test plan and the test plans
on all the associated bugs.
--
You received this bug notification because you are a member of Desktop
Hello Nathan, or anyone else affected,
Accepted mutter into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted mutter into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted mutter into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/44.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
1 - 100 of 8510 matches
Mail list logo
