Just to give a data point, mesa/23.3.3-1ubuntu1 fixes many issues with
snaps and LibGL on my laptop, namely:
- white blank screen when opening firmware-updater snap
- no OpenGL hardware acceleration but software rendering only in chromium snap,
and missing background effect in Google Meet
fwiw, this worked for me with 22.04 LTS ISO.
#cloud-config
autoinstall:
version: 1
identity:
hostname: ubuntu-server
username: ubuntu
# password=ubuntu
password:
"$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
** Description changed:
- When running a laptop with a mesh WiFi network, frequent disconnections
- happen like 10 to 20 times per hour. And the issue has disappeared by
+ When running a laptop with a mesh WiFi network, frequent errors/notices
+ are recorded on an access point. And the issue has
** Patch added:
"rrm-include-passive-channels-in-active-beacon-report-scan.patch"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1987252/+attachment/5610935/+files/rrm-include-passive-channels-in-active-beacon-report-scan.patch
--
You received this bug notification because you are a
** Description changed:
When running a laptop with a mesh WiFi network, frequent disconnections
happen like 10 to 20 times per hour. And the issue has disappeared by
applying the following patch.
https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6
> RRM:
The output above was with Intel Wi-Fi 6 AX201. And another colleague in
EU had Intel 8200 series and the output was all *with* NO_IR.
> Mode[A] Channels:
> 36 = 5180 MHz (NO_IR)
> 40 = 5200 MHz (NO_IR)
> 44 = 5220 MHz (NO_IR)
> 48 = 5240 MHz (NO_IR)
> 52 = 5260 MHz (NO_IR) (DFS)
> 56 = 5280
I forgot to mention; 2.10-9ubuntu1 in kinetic didn't make a difference
so I went down the path of finding a commit in upstream.
My colleague in EU kindly shared an output of `sudo wpa_cli get_capability
freq` and it had 5GHz channels *without* NO_IR. So the key to reproduce the
issue would be
I've been using the custom build with the patch for one and a half days
and it's far stable now.
https://launchpad.net/~nobuto/+archive/ubuntu/experimental-
packages/+build/24301259/+files/wpasupplicant_2.10-6ubuntu2.1~ppa1_amd64.deb
--
You received this bug notification because you are a
Public bug reported:
When running a laptop with a mesh WiFi network, frequent disconnections
happen like 10 to 20 times per hour. And the issue has disappeared by
applying the following patch.
https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6
> RRM: Include passive
> TL;DR: pipewire-pulse and PulseAudio should *not* be installed at the
same time as they serve the same function and applications don't know
the difference.
This is not the case at least for the default Ubuntu flavor (w/ GNOME).
$ curl -s
I can confirm that after stopping pipewire temporarily by:
$ systemctl --user stop pipewire.socket pipewire.service
The volume level is properly recovered across plugging in and out a headset for
example, which is good.
Both pulseaudio and pipewire are installed out of the box and running if
I'm
>From a duplicate of this bug, as tldr:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
> > > Does that mean that enabling it, would only add some dependencies but
> > > not actually do anything?
> >
> > Yes, a (soft)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
> > Does that mean that enabling it, would only add some dependencies but
> > not actually do anything?
>
> Yes, a (soft) dependency should probably be added against
> gstreamer1.0-plugins-bad, but as I said, the needed version (>= 1.19)
** Bug watch added: Debian Bug tracker #991597
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
** Also affects: pulseaudio (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
The changelog mentions AptX, but it's not actually enabled in the build
if I'm not mistaken. Aptx support seems to require gstreamer in the
build dependency at least.
[changelog]
pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium
* New upstream version
FWIW, I was able to use WPS push botton with 19.10 as of today. There was a
message as "Alternatively you can connect by pushing the “WPS” button on your
router" and it just worked for me. The UI patch seems merged in upstream 7
months ago.
Public bug reported:
When logging into lightdm guest session, mozc gives an error saying
"Failed to start Kana/Kanji conversion program. You need to reboot".
Thus Japanese text cannot be input.
[possibly related messages]
10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400
output of `journalctl -k`.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509829/+attachment/4504791/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
** Package changed: unity-settings-daemon (Ubuntu) => ubuntu-settings
(Ubuntu)
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Nobuto Murata (nobuto)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Summary changed:
- after upgrading, one finger tap no longer works
+ after upgrading, tap-to-click no longer works by default
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
2015-07-07 0:38 GMT+09:00 Gunnar Hjalmarsson 1468...@bugs.launchpad.net:
On 07/06/2015 05:14 PM, Nobuto Murata wrote: On 06/23/2015 07:42 PM,
tomoe_musashi wrote:
and of course, i still hope that ubuntu could drop those
69-language-selector fontconfig files, just like what F13 did.
Can you
Hello tomoe_musashi,
I believe Noto Sans CJK is one of the best fonts available in free/libre
licenses for Japanese. However I'm not convinced to set the Noto Sans
CJK as default yet and I would like to know your motivations here.
But for Chinese and Japanese community, i think that the answer
So if @nobuto can tell that using fcitx as default is desired for Japanese
users, let's talk with other people on desktop team next week (preferably
on IRC).
Well, fcitx-anthy(LP: #1356222) and fcitx-mozc are still in universe. No
Japanese engine for fcitx to seed is available yet.
@ikuya, can
Maybe theoretical, but: If LC_CTYPE is set explicitly, its value is
not surrounded by quotes in the locale output.
I actually hit this issue and opened an separate bug as LP: #1431862. If
you guys intend to fix it in a series of this bug, please mark it as a
duplicate.
--
You received this bug
It's better to be backported to utopic as well, but I'm not sure if
ubuntu-meta can be SRUed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1377370
Title:
It looks like it's no longer reproducible on vivid. I'm not sure where
exatly it's fixed.
eog:
Installed: 3.14.3-1ubuntu2
light-themes:
Installed: 14.04+15.04.20150212-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) = Nobuto Murata (nobuto)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1377370
Title:
ubuntu-desktop
From utopic, ibus-gtk no longer be pulled automatically. I have proposed
a merge especially for ibus-gtk in bug #1377370.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
related: bug #1164252
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1377370
Title:
ubuntu-desktop should depend on ibus-gtk
Status in One Hundred Papercuts:
*** This bug is a duplicate of bug 1419554 ***
https://bugs.launchpad.net/bugs/1419554
** This bug has been marked a duplicate of bug 1419554
Can't upgrade procps in LXC 1.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Upstart cookbook refers to limit nofile unlimited unlimited.
http://upstart.ubuntu.com/cookbook/#limit
However it fails to start jobs, for example:
$ sudo stop cron
$ echo limit nofile unlimited unlimited | sudo tee /etc/init/cron.override
$ sudo start cron
start: Job
[/var/log/upstart/procps.log]
sysctl: setting key kernel.printk: Read-only file system
sysctl: setting key net.ipv6.conf.all.use_tempaddr: Read-only file system
sysctl: setting key net.ipv6.conf.default.use_tempaddr: Read-only file system
sysctl: setting key kernel.kptr_restrict: Read-only file
Public bug reported:
Inside a trusty container on vivid host.
$ running-in-container
lxc
$ sudo dpkg --configure -a
Setting up procps (1:3.3.9-1ubuntu2.1) ...
start: Job failed to start
invoke-rc.d: initscript procps, action start failed.
dpkg: error processing package procps (--configure):
** Package changed: light-themes (Ubuntu) = ubuntu-themes (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1296487
Title:
Initial zoom level is slightly
overlayfs, sound good. I will try it to see if it works for me without
patching.
** Patch removed: lxc_sru_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff
** Patch removed: lxc_utopic.debdiff
Public bug reported:
I'm following this guide:
https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/
[quote]
Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing
as you have on the host. Note that if you want the container to only be able to
read the
** Patch added: lxc_utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229943/+files/lxc_utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Patch added: lxc_sru_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
You can also easily work around this by adding
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
to your /etc/lxc/default.conf or ~/.local/share/lxc/default.conf.
hmm, /etc/lxc/default.conf already had lxc.network.hwaddr =
00:16:3e:xx:xx:xx in my env. Besides, I have changed the line in
Public bug reported:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
After installing old packages, it seems a regression between
https://launchpad.net/ubuntu/+source/lxc/1.0.4-0ubuntu2/+build/6098430
and
https://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha1-0ubuntu1/+build/6162946
--
You received this bug notification because you are a member of Ubuntu
Touch
41 matches
Mail list logo
