Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ibus-m17n (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-m17n in Ubuntu.
I can reproduce this issue and if I disable hardware acceleration in
settings::system, tab will crash when webcam starting.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
spirv-headers is build-depended on by several packages; could we do
test-rebuilds of those as a part of verification, please.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1991761
Title:
Hello Timo, or anyone else affected,
Accepted spirv-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/spirv-
headers/1.6.1+1.3.216.0-1~ubuntu0.22.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
I know it doesn't have any rdepends in the archive, but this includes a
libdrm-tegra0 ABI break without bumping SONAME; what sort of consumers
of libdrm-tegra0 are likely to exist? What risk mitigations could we
implement?
--
You received this bug notification because you are a member of Desktop
Public bug reported:
I am trying to access a remote computer that does not have a publicly-
routable IPv4 address. Let's say that MyHostName.MyDomain.com has an IP
address of 2001:db8::1. If you look it up in DNS, you get no A records
and one record.
Using both Remmina and
@Aaron/arraybolt3
I filed against the package I did, as I don't experience it on other
boxes that include much slower CPUs than those listed here, but instead
use i915 or AMD gpu.
Examples where I've not experienced this include (some slower boxes)
- lenovo thinkpad sl510 (c2d-t6570, 2gb ram,
I have the same problem. Screen Blank activates after a period of
inactivity and then the monitor briefly turns off then on with
backlight. Fresh install OS does not fix the problem. Can someone help?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hello Timo, or anyone else affected,
Accepted directx-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/directx-
headers/1.606.4-1~ubuntu0.22.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
I've noticed this problem also on slower systems of mine (an Acer
Chromebook C720 for instance). This leads me to believe that system
speed (or perhaps graphics subsystem speed?) is the culprit here, as
other systems work with flurry just fine.
--
You received this bug notification because you
And this is the logs from Chromium when running the steps in the
previous comment.
** Attachment added: "chromium_hwacc_no_webcam.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635526/+files/chromium_hwacc_no_webcam.log
--
You received this bug
1. The Pipewire flag was set to "Default", but even when set to "Enabled", the
webcam does not work.
2. journalctl.log attached when accessing framatalk.org and creating a room.
** Attachment added: "journalctl.log"
** Tags added: snap
--
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 chromium-browser package in
It can't be removed from Debian until someone ports debian-installer
away from GTK2. :(
** Tags removed: lucid
** Tags added: lunar
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1999335
Public bug reported:
marisa 0.2.6-12 in -proposed does not build due to a missing dependency.
The explanation is that the ruby3.1 transition has not started yet in
Ubuntu, see bug #1999550.
No need to take separate measures for this reason; it will probably
build as soon as the ruby3.1
Hello Togo28, or anyone else affected,
Accepted evince into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/43.0-1ubuntu1
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-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-desktop/42.7-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this
Hello Jeremy, or anyone else affected,
Accepted gnome-remote-desktop into kinetic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-desktop/43.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this
On 2022-12-13 19:40, Sharcoux wrote:
> layout: fr,fr
> variant:latin9,oss
Then it's the "French (legacy, alt.)" layout you use. And yes, with that
layout you get dead_circumflex by simply pressing the key to the right
of the P key. (But I think the layout used to make use of some dead key
Public bug reported:
As requested in the upstream bug report
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby file
the downstream issue:
I am experiencing high cpu usage of gnome-shell in situations where I
would not expect it, leading to my fans running more often and wasting
The verification of the Stable Release Update for livecd-rootfs 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
This bug was fixed in the package livecd-rootfs - 2.765.13
---
livecd-rootfs (2.765.13) jammy; urgency=medium
[ Heinrich Schuchardt ]
* Backporting patches to support new RISC-V platforms (LP: #1997233)
* Add support for the LicheeRV board (SUBARCH=licheerv)
* Add support for
Marc, 102.6 was officially released today, so I've gone ahead and
updated my jammy mozjs branch for it. I added the CVEs you mentioned and
found one more I found from 102.4. I don't see any new ones for 102.6
I've also created a ubuntu/102/kinetic branch for mozjs102 for kinetic.
Since it doesn't
I'm a bit confused about your questions related with xkb-data but I hope
that this will help: here is the result of `setxkbmap -print`:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(azerty)" };
xkb_types { include "complete" };
xkb_compat{ include
liblc3 1.0.1-1ubuntu3 in lunar: universe/misc -> main
Override [y|N]? y
1 publication overridden.
** Changed in: liblc3 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liblc3 in
Are you using some layout which is not provided by xkb-data?
The one I used is named "French (alt., Latin-9 only)" and is represented
by the dconf value fr+oss_latin9. The dconf value fr+latin9 is also
available, but the name of that layout is "French (legacy, alt.)".
I'm not sure about the
Here is a layout looking almost like mine:
https://en.wikipedia.org/wiki/AZERTY#/media/File:KB_France.svg
I press the key which is to the right to `p` and to the left of `$ ` and
do not need to hold AltGr nor Shift.
If you run `gkbd-keyboard-display -l latin-9`, you should see my layout.
It
Thanks for the report.
Can you please
1. confirm that the issue is reproducible with the Pipewire flag in
about:flags turned on?
2. attach the output of journalctl around the time that happens?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
On a freshly installed Bionic system our DesignJet T120 is auto-detected
as a driverless IPP printer as soon as it is switched on, and I can
directly select it as the printer to use in print dialogs.
On Focal and later it is not auto detected anymore (also tried with
fresh
Added package.
** Description changed:
Version of Ubuntu: 22.10
- Package: ?
+ Package: X.org
Expected to happen: Toolbox on the top right corner should stay in dark mode
all the time.
What happened instead: When accessing appearance options at config menu, the
toolbox on the top right
You have been subscribed to a public bug:
Version of Ubuntu: 22.10
Package: X.org
Expected to happen: Toolbox on the top right corner should stay in dark mode
all the time.
What happened instead: When accessing appearance options at config menu, the
toolbox on the top right corner goes white,
I have the same issue with the latest gnome-shell-extension-ubuntu-dock -
74ubuntu2
It's related to display scaling, using 200% has this issue. In my case I need
to use display scaling otherwise the texts are extremely small on my screen.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1979096 ***
https://bugs.launchpad.net/bugs/1979096
I have the same issue, disabling all extensions does not help.
The bug appears when auto-hide is on, so basically makes auto-hide unusable.
--
You received this bug notification because you are a member
The 1.20 components have been uploaded to the 22.04 SRU queue now.
@oem it would be nice if you could improve the bug description to have a
more detailed testcase and regression potential section
** Description changed:
* Impact
Fibocom FM350 modems aren't working with the current
** Also affects: oem-priority/focal
Importance: Undecided
Assignee: Robert Liu (robertliu)
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1998765
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: totem (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1754477
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: intel-vaapi-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
** Description changed:
+ * Impact
+
+ Fibocom FM350 modems aren't working with the current version of
+ modemmanager in 22.04.
+
+ * Test case
+
+ Try connecting to 5G using a FM350 modem
+
+ * Regression potential
+
+ The SRU does an update to new modemmanager serie so we should do a
+
Just for info, I mean if anyone wants to port them :-), Debian SID
already has drivers patched for kernel 6.1 called nvidia-legacy-340xx-
driver.
Please check it out here:
This release was made specifically to help out older LTS distributions
which cannot migrate to newer libgweather. What needs to be done to get
it into 20.04?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
It should be removed, but this package is synced from Debian. File a
removal request there?
(BTW, 'lucid' is the wrong tag by 13 years ;)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
41 matches
Mail list logo
