[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launch
** Attachment added:
"201606-22344-network-manager-nplusone-190312.var-log.tar.gz"
https://bugs.launchpad.net/ubuntu/+bug/1819572/+attachment/5245585/+files/201606-22344-network-manager-nplusone-190312.var-log.tar.gz
** Also affects: network-manager (Ubuntu)
Importance: Undecided
St
Public bug reported:
using a (2010?) 2.1 surround Creative speaker but the sound seems to
fall back to a generic stereo output with only left and right channels
(using the green plug).
The subwoofer receives little sound and the left and right speakers
receive the bulk of the sound. If I increase
Also, does this bug apply to the laptop's internal speakers? Or are you
using headphones?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1818802
Title:
[ZenBook UX433FN
Next, please wait until the audio has stopped working AND has later come
back, then run:
dmesg > dmesgafter.txt
journalctl -b0 > journalafter.txt
and send us the files 'dmesgafter.txt' and 'journalafter.txt'.
** Summary changed:
- [ZenBook UX433FN_UX433FN] Audio only works when the laptop i
I'm removing this from the 19.0 blocking tracker. Generally we don't add
bugs to block a release if they were present in the previous release,
additionally there doesn't seem to be any consensus on a solution, at
this moment. If there is a fix implemented I'd be happy to pull that
into a later 19.0
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
This bug was fixed in the package pygobject - 3.32.0-1
---
pygobject (3.32.0-1) experimental; urgency=medium
* New upstream release
-- Jeremy Bicha Sun, 10 Mar 2019 12:59:34 -0400
pygobject (3.31.4-1) experimental; urgency=medium
* New upstream release
* Bump minimum glib
Dimitri didn't post results from a power8 system, but here's what I see
in a Power8 VM, with up-to-date 19.04:
$ lscpu
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
** Package changed: network-manager (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1819549
Title:
Cannot Update Ubuntu MATE 16.04.2 RP1
Status
This was fixed in -121.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1110147
Title:
Error in manual
Public bug reported:
When attempting to use the Update utility on Ubuntu MATE 16.04.2 on
Raspberry Pi 3 for the latest security updates the user is informed that
approximately 50MB of space is required and there is not enough space on
/boot.
The user is advised to use "sudo apt-get clean" to free
PS: the issue is not present any more. It had been for some two/three
weeks, now it's gone... (no, I have not been using hibernation or
suspend)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.l
Acceptance of openssl currently blocked on coverage of the (distro
patch) OPENSSL_TLS_SECURITY_LEVEL change as part of the SRU template.
** Changed in: openssl (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Same here on OpenSUSE Tumbleweed u,u
El lun., 11 de mar. de 2019, 13:45, magdiychuk <1553...@bugs.launchpad.net>
escribió:
> I really hope that the problem will be solved. I use Arch Linux and the
> same problem. The subwoofer does not work ... :-( It is a pity. I would
> like to solve the proble
Hello, it seems like now audio is not working even when on full battery
or plugged in. It's so weird.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1818802
Title:
[Zen
** Description changed:
This is actually a regression in Disco from Artful, Bionic and Cosmic,
where this was fixed in https://bugs.launchpad.net/bugs/1717951
- Since the update to Disco the unprofessional and childish ImageMagick
- icon is back. It was removed in Artful, Bionic and Cosmic
Filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-
settings/+bug/1819503
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1717951
Title:
UIFe: Drop imagemagick-
This bug was fixed in the package systemd - 237-3ubuntu10.15
---
systemd (237-3ubuntu10.15) bionic; urgency=medium
[ Victor Tapia ]
* d/p/stop-mount-error-propagation.patch:
keep mount errors local to the failing mount point instead of blocking
the processing of all mounts
Seems a dupe to me.
For the bionic case, with keepalived < 2.0, is there some keepalived
script that can be run to restore the vip, after networkd removed it? We
could run it as a network-dispatcher hook then. Has this been
considered?
--
You received this bug notification because you are a memb
This bug was fixed in the package systemd - 229-4ubuntu21.17
---
systemd (229-4ubuntu21.17) xenial; urgency=medium
[ Victor Tapia ]
* d/p/stop-mount-error-propagation.patch:
keep mount errors local to the failing mount point instead of blocking
the processing of all mounts
This bug was fixed in the package systemd - 239-7ubuntu10.10
---
systemd (239-7ubuntu10.10) cosmic; urgency=medium
[ Victor Tapia ]
* d/p/stop-mount-error-propagation.patch:
keep mount errors local to the failing mount point instead of
blocking the processing of all mounts
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been 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
This bug was fixed in the package systemd - 229-4ubuntu21.17
---
systemd (229-4ubuntu21.17) xenial; urgency=medium
[ Victor Tapia ]
* d/p/stop-mount-error-propagation.patch:
keep mount errors local to the failing mount point instead of blocking
the processing of all mounts
** Summary changed:
- Drop imagemagick-display from the default install [regression]
+ Drop imagemagick-display from the default install [disco regression]
** Description changed:
- This is actually a regression from
- https://bugs.launchpad.net/bugs/1717951
+ This is actually a regression in
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been 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
I really hope that the problem will be solved. I use Arch Linux and the
same problem. The subwoofer does not work ... :-( It is a pity. I would
like to solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-dr
The verification of the Stable Release Update for libseccomp has
completed successfully and the package has now been 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 encounte
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu4.1
---
libseccomp (2.3.1-2.1ubuntu4.1) bionic; urgency=medium
* d/p/lp-1755250-add-the-statx-syscall.patch: add statx support (LP: #1755250)
* d/p/lp-1815415-*: Add syscalls up to kernel 4.15 (LP: #1815415)
-- Christ
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu4.1
---
libseccomp (2.3.1-2.1ubuntu4.1) bionic; urgency=medium
* d/p/lp-1755250-add-the-statx-syscall.patch: add statx support (LP: #1755250)
* d/p/lp-1815415-*: Add syscalls up to kernel 4.15 (LP: #1815415)
-- Christ
The verification of the Stable Release Update for libseccomp has
completed successfully and the package has now been 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 encounte
Public bug reported:
This is actually a regression in Disco from Artful, Bionic and Cosmic,
where this was fixed in https://bugs.launchpad.net/bugs/1717951
Since the update to Disco the unprofessional and childish ImageMagick
icon is back. It was removed in Artful, Bionic and Cosmic for the
follo
This bug was fixed in the package libxcb - 1.13-2~ubuntu18.04
---
libxcb (1.13-2~ubuntu18.04) bionic-proposed; urgency=medium
[ Timo Aaltonen ]
* Package libxcb-xinput0/libxcb-xinput-dev. (Closes: #733227) (LP: #1777994)
[ Andreas Boll ]
* control: Fix VCS urls.
-- Jonathan
The verification of the Stable Release Update for libxcb has completed
successfully and the package has now been 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 r
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.1
---
resolvconf (1.79ubuntu10.18.04.1) bionic; urgency=medium
* Pull systemd-resolved conf from non-stub file; the stub file should
not be used unless all dns traffic goes to the local stub resolver.
Specific
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-themes (Ubuntu)
Status: New => Confirmed
--
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
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/178772
@seb128 please see "In 16.04 the NetworkManager package used to carry
this patch..." in the bug description above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754
I am looking for if the patch was included before the release of mesa
"19.0.0-rc7"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1815236
Title:
totem assert failure: totem:
They could pass to [1]mesa_19.0.0~rc7
[1]
https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog
https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.
** Bug watch added: freedesktop.org Bugzilla #109535
https://bugs.freedeskt
Thank you for your bug report, that might be best reported upstream on
https://lists.gnu.org/mailman/listinfo/bug-tar
** Changed in: tar (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touc
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1669751.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
Fixed in gobject-introspection (1.60.0-1).
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1816415
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.1
---
resolvconf (1.79ubuntu10.18.10.1) cosmic; urgency=medium
* Pull systemd-resolved conf from non-stub file; the stub file should
not be used unless all dns traffic goes to the local stub resolver.
Specific
The verification of the Stable Release Update for resolvconf has
completed successfully and the package has now been 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 encounte
Please see if this kernel helps:
https://people.canonical.com/~khfeng/lp1809856/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1809856
Title:
[XPS 13 9370, Realtek AL
/etc/mke2fs.conf:
[defaults]
blocksize = 4096
[fs_types]
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
We default to 4k, unless one is formatting small filesystems which from manpage:
If the filesystem size
This is a well-known upstream issue/bug.
This is not s390x, Ubuntu 18.10, any other Ubuntu release specific.
There is no dataloss -> one can execute pvmove operation in reverse (or i guess
onto any 512 sector size PV) to mount the filesystems again.
Thus this is not critical at all.
Also, I am f
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.n
** Changed in: perl (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
** Changed in: ubuntu-power-systems
Status: Incomplete => Confirmed
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Per former discussion, better safe than sorry - added a FFe request to
the description and subscribed the release-team.
** Description changed:
+ [FFe]
+ * (re-)introduce a feature to ensure the initial (boot time) kernel
+messages are preserved
+ * This existed up to Trusty (upstart) but
Ok, reproduced this on x86_64 with raw files which are in multiples of
4k.
This is not an architecture specific issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
T
note this is listed in pending-sru as being at 5 days aging, however it
was actually uploaded 9 days ago, then re-uploaded mid-last-week with
the patches for bug 1812760 removed; so the patches for this bug have
been in the systemd in -proposed for 9 days.
--
You received this bug notification be
--- Comment From ifran...@de.ibm.com 2019-03-11 08:22 EDT---
The message "Device size is not aligned to the requested sector size." is
because the size of your loopback device is not a multiple of 4096 bytes. With
--sector-size 4096, it's size must be a multiple of 4096 bytes, otherwise y
bah, mbrtowc claims to fail, tested that with C too, that works too.
And I cannot understand how perl XS stuff works. But it is fairly recent that
mbrtowc was started to be used.
See: 6de6aebdf89cb5abd8296cf686184e4b9461d11b
--
You received this bug notification because you are a member of Ubun
Sample C usage of mblen() appears to be fine, so libc is probably fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dump
On an amd64 machine, I do get a core dump:
xnox@ottawa:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s)
I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development
release).
I am failing to produce a mixed blocksize cryptsetup device:
$ sudo cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
is faili
Kay-Heng, what's the status of the linux image landing on bionic?
Can you help in verify this once we've all there?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1745032
Ti
It would be the readdition of a feature that we lost as a feature
regression nine releases ago. I don't see why the release team would
object, but I can't speak for the release team. It feels like a feature
to me. In the general case, ignoring feature freeze for features being
readded that were dro
what testing has happened / what are the risks?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516
Title:
FFe: Mesa 19.0.x for disco
Status in mesa package in Ubuntu:
ubuntu@baltar:~$ lscpu
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 160
On-line CPU(s) list: 0-159
Thread(s) per core: 4
Core(s) per socket: 20
Socket(s): 2
NUMA node(s):2
Model: 2.2 (pvr 004e 1202)
Model name: POWE
Yep, sure. (Ideally as a sync.)
It'd be nicer for me in future if you could paste the NEWS entries and
other things, so that I can read it all and reply directly from my email
client. :-)
** Changed in: pygobject (Ubuntu)
Status: New => Confirmed
** Changed in: pygobject (Ubuntu)
Impor
@xnox - thanks for your ping, I agree if we would have worked on this in Vivid
or at least Xenial.
But being so late I'd think to ask for an ack by the Release team is not wrong.
I thought here "better safe than sorry" somewhat applies.
OTOH fortunately the change itself isn't very invasive to an
There you go
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5245381/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubu
I have the same bug. I used to work around this by installing an
alternative sound device selector shell extension but this one broke
down when Gnome shell upgraded to 3.31.91. So now there is no way for me
to switch to HDMI output any more.
The select box shows the correct devices but selecting a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://
I'm not sure why you think an FFe is needed for this. It is a simple
regression since move from upstart->systemd in the rsyslog package, and
we must SRU this back to all the releases back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
If I also set "AuthType Default" for "/" then the cups 2.2.7-1ubuntu2.4 works.
I did not have this set in 14.04 or 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
cups 2.2.7-1ubuntu2.4 from proposed has exactly the same symptoms for me
- prompts for password when printing. So the original issue seems to be
different from Esko's.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ub
Esko, thanks for the feedback. I have marked the fix as verified now so
it will get an official update for Bionic soon.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
h
@dwmw2, 'This was a regression there caused by an earlier update.' would
give some details ont that? you should probably open another report
specifically about that if there was a regression in a xenial update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
cups 2.2.7-1ubuntu2.4 from proposed works and fixes this issue for us.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
Title:
[SRU] AuthInfoRequired negotiate in cups
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
Perl core dumping core on UBUNTU 19.04
Also verified mpv works, but mpv isn't using VAAPI at all. It's using
software decoding because "VO does not support requested hardware
decoder".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
Verified on bionic (fresh install and fully updated) that the bug is still
present, and that the workaround in comment #16 works. It just took me a while
to remember you need to:
1. Install ubuntu-restricted-addons; and
2. Use Xorg (because if you're in a Wayland session you hit bug 1720820
78 matches
Mail list logo
